--------------------------------------------------------------------------------
/npm/src/old/Layers/2-Mid/midLevel.md:
--------------------------------------------------------------------------------
1 | ### Mid Level (Detailed Categories)
2 | Once "Wildlife" **(category)** is chosen, functions in the Mid level handle displaying "Biology" or differentiating between marine animals and land animals.
3 | Business logic handle user interactions specific to this subcategory.
4 |
5 | - **Purpose**: Delves deeper into specifics, but not the most detailed level. Could represent subcategories or more detailed themes.
6 |
7 | - **Contains:**
8 | - **Sub-controllers**: Manage the flow within this level, calling on granular functions or operations as needed.
9 | - **Business Logic**: Code handling specific processes related to the subcategories.
10 | - **Views (if applicable)**: For visual representations specific to this middle level.
11 |
12 | ### Example:
13 |
14 | Given list of categories (Wildlife, Geography, etc.):
15 |
16 | **Docs:** [this.me](https://www.neurons.me/this-me)
17 | **Docs:** [mlearning.me](https://www.mlearning.me)
18 | **Docs:** [neurons.me](https://www.neurons.me/)
19 |
20 | 
--------------------------------------------------------------------------------
/docs/config.md:
--------------------------------------------------------------------------------
1 | #### Name: i.mlearning src/docs/config.md
2 |
3 | **Docs:** [mlearning](https://www.mlearning.studio) **Docs:** [neurons.me](https://www.neurons.me/)
4 |
5 | # i.mlearning/
6 |
7 | ```text
8 | i.mlearning/
9 | │
10 | ├── index.js # Entry Point
11 | ├── docs/
12 | ├── tests/
13 | ├── src/
14 | │ ├── gematria/
15 | │ │ ├── index.js
16 | │ │ ├── values.js
17 | │ │
18 | │ ├── Token/
19 | │ │
20 | │ │── Layer/ # Base directory for all layers
21 | │ │ ├── High/ # Components or functionalities for high-level abstraction
22 | │ │ │ ├── index.js # Entry point for high-level functionalities
23 | │ │ │ ├── ... # Other relevant files or directories for high-level operations
24 | │ │ ├── Mid/ # Components or functionalities for mid-level abstraction
25 | │ │ │ ├── index.js # Entry point for mid-level functionalities
26 | │ │ │ ├── ... # Other relevant files or directories for mid-level operations
27 | │ │ └── GranularLevel/ # Components or functionalities for granular-level abstraction
28 | │ │ ├── index.js # Entry point for granular-level functionalities
29 | │ │ ├── ... # Other relevant files or directories for granular operations
30 | │ │
31 | │ ├── utils/ # Directory for utilities or helper functions that may be shared across layers
32 | │ ├── tokenization.js
33 | │ ├── ... # Other utility functions
34 | │
35 | │
36 | └── README.md # Documentation for your module
37 | └── package.json
38 | ```
39 |
40 | This structure ensures:
41 |
42 | 1. **Separation of Concerns**: Each layer has its own dedicated directory, ensuring functionalities are neatly organized.
43 | 2. **Scalability**: Easily add more functionalities within each layer or even add more layers without disturbing the existing structure.
44 | 3. **Shared Utilities**: Common utility functions or helpers that are used across layers are kept in a central `Utils` directory for ease of access and maintenance.
45 |
46 | Remember `i.mlearning`.
47 |
--------------------------------------------------------------------------------
/npm/src/old/gematria/values.json:
--------------------------------------------------------------------------------
1 | {
2 | "gematria_values": [
3 | {
4 | "number": 10,
5 | "hebrew": "י - Yud",
6 | "description": "Represents the singular point of creation, divinity, and the infinite in the finite."
7 | },
8 | {
9 | "number": 18,
10 | "hebrew": "חי - Chai",
11 | "description": "Means 'life'. Commonly used in the custom of giving monetary gifts in multiples of 18."
12 | },
13 | {
14 | "number": 26,
15 | "hebrew": "יהוה - YHWH",
16 | "description": "The numerical value of the Tetragrammaton, the ineffable name of God."
17 | },
18 | {
19 | "number": 32,
20 | "hebrew": "לב - Lev",
21 | "description": "Means 'heart'. Significant in Kabbalistic literature, associated with the 32 Paths of Wisdom."
22 | },
23 | {
24 | "number": 40,
25 | "hebrew": "מ - Mem",
26 | "description": "Represents transition or change, such as the duration of the Great Flood or Moses' time leading the Israelites."
27 | },
28 | {
29 | "number": 72,
30 | "description": "Associated with the 72 names of God in Kabbalah, derived from three verses in Exodus 14."
31 | },
32 | {
33 | "number": 137,
34 | "description": "Significant in Jewish contexts and also known as the Fine Structure Constant in physics."
35 | },
36 | {
37 | "number": 613,
38 | "description": "Represents the total number of mitzvot (commandments) in the Torah."
39 | },
40 | {
41 | "number": 666,
42 | "description": "While most associated with Christian eschatology, it appears in the Hebrew Bible in contexts like 1 Kings 10:14."
43 | },
44 | {
45 | "number": 888,
46 | "hebrew": "Mashiach (Mem, Shin, Yud, Chet)",
47 | "description": "The gematria value of the word 'Mashiach' (Messiah) when spelled in a particular way."
48 | }
49 | ]
50 | }
51 |
--------------------------------------------------------------------------------
/docs/styles/prettify-jsdoc.css:
--------------------------------------------------------------------------------
1 | /* JSDoc prettify.js theme */
2 |
3 | /* plain text */
4 | .pln {
5 | color: #000000;
6 | font-weight: normal;
7 | font-style: normal;
8 | }
9 |
10 | /* string content */
11 | .str {
12 | color: #006400;
13 | font-weight: normal;
14 | font-style: normal;
15 | }
16 |
17 | /* a keyword */
18 | .kwd {
19 | color: #000000;
20 | font-weight: bold;
21 | font-style: normal;
22 | }
23 |
24 | /* a comment */
25 | .com {
26 | font-weight: normal;
27 | font-style: italic;
28 | }
29 |
30 | /* a type name */
31 | .typ {
32 | color: #000000;
33 | font-weight: normal;
34 | font-style: normal;
35 | }
36 |
37 | /* a literal value */
38 | .lit {
39 | color: #006400;
40 | font-weight: normal;
41 | font-style: normal;
42 | }
43 |
44 | /* punctuation */
45 | .pun {
46 | color: #000000;
47 | font-weight: bold;
48 | font-style: normal;
49 | }
50 |
51 | /* lisp open bracket */
52 | .opn {
53 | color: #000000;
54 | font-weight: bold;
55 | font-style: normal;
56 | }
57 |
58 | /* lisp close bracket */
59 | .clo {
60 | color: #000000;
61 | font-weight: bold;
62 | font-style: normal;
63 | }
64 |
65 | /* a markup tag name */
66 | .tag {
67 | color: #006400;
68 | font-weight: normal;
69 | font-style: normal;
70 | }
71 |
72 | /* a markup attribute name */
73 | .atn {
74 | color: #006400;
75 | font-weight: normal;
76 | font-style: normal;
77 | }
78 |
79 | /* a markup attribute value */
80 | .atv {
81 | color: #006400;
82 | font-weight: normal;
83 | font-style: normal;
84 | }
85 |
86 | /* a declaration */
87 | .dec {
88 | color: #000000;
89 | font-weight: bold;
90 | font-style: normal;
91 | }
92 |
93 | /* a variable name */
94 | .var {
95 | color: #000000;
96 | font-weight: normal;
97 | font-style: normal;
98 | }
99 |
100 | /* a function name */
101 | .fun {
102 | color: #000000;
103 | font-weight: bold;
104 | font-style: normal;
105 | }
106 |
107 | /* Specify class=linenums on a pre to get line numbering */
108 | ol.linenums {
109 | margin-top: 0;
110 | margin-bottom: 0;
111 | }
112 |
--------------------------------------------------------------------------------
/docs/Tokens.md:
--------------------------------------------------------------------------------
1 | Using Hebrew for token creation based on the gematria system.
2 |
3 | Hebrew Alphabet and Numeric Mapping:
4 |
5 | Traditional Hebrew Gematria mapping:
6 |
7 | Copy code
8 | א - 1 י - 10 ק - 100
9 | ב - 2 כ - 20 ר - 200
10 | ג - 3 ל - 30 ש - 300
11 | ד - 4 מ - 40 ת - 400
12 | ה - 5 נ - 50
13 | ו - 6 ס - 60
14 | ז - 7 ע - 70
15 | ח - 8 פ - 80
16 | ט - 9 צ - 90
17 |
18 | Compute Gematria Values.
19 |
20 | Package Initialization:
21 |
22 |
23 | 10 (י - Yud): Represents the singular point of creation, divinity, and the infinite in the finite.
24 |
25 | 18 (חי - Chai): As mentioned, this means "life". The custom of giving monetary gifts in multiples of 18 is common in Jewish tradition because of this association.
26 |
27 | 26 (יהוה - YHWH): This is the numerical value of the Tetragrammaton, the ineffable name of God. The individual letters are Yud (10), Hei (5), Vav (6), and Hei (5), which add up to 26.
28 |
29 | 32 (לב - Lev): This number, which means "heart" in Hebrew, is significant in Kabbalistic literature, especially in the context of the 32 Paths of Wisdom associated with the Tree of Life.
30 |
31 | 40 (מ - Mem): Represents transition or change. For instance, the Great Flood during Noah's time lasted 40 days and 40 nights, and Moses spent 40 years leading the Israelites through the desert.
32 |
33 | 72: In Kabbalah, there's the concept of the 72 names of God, derived from three verses in Exodus 14, each containing 72 letters.
34 |
35 | 137: This number has intrigued both religious scholars and scientists. It's seen in various Jewish contexts, but it's also known as the Fine Structure Constant in physics, a dimensionless value that describes the strength of the electromagnetic interaction between elementary charged particles.
36 |
37 | 613: Represents the total number of mitzvot (commandments) in the Torah.
38 |
39 | 666: While most associated with Christian eschatology, 666 appears in the Hebrew Bible too. For example, in 1 Kings 10:14, it's the weight of the gold that came to King Solomon in a single year.
40 |
41 | 888: This is the gematria value of the word "Mashiach" (Messiah) when spelled Mem, Shin, Yud, Chet.
--------------------------------------------------------------------------------
/npm/Knowledge_Files/Components of a Supervised Learning Dataset.md:
--------------------------------------------------------------------------------
1 | In supervised learning, for classification tasks (classifying images as 'cat' or 'non-cat'), the dataset typically consists of the following components:
2 |
3 | ### Components of a Supervised Learning Dataset
4 |
5 | 1. **Training Data:**
6 | - **Training Data Collection (Features):** This is a set of data used to train the model. For image classification, these are usually arrays of pixel values.
7 | - **Training Labels (Targets):** These are the correct answers or labels for each instance in the training data. In your case, these labels indicate whether each image is of a cat (1) or not (0).
8 |
9 | 2. **Test Data:**
10 | - **Test Data Collection (Features):** This set of data is used only for evaluating the performance of the model after it has been trained. It should not be used in the training phase.
11 | - **Test Labels (Targets):** These are the correct labels for the test data. They allow you to assess how well your model predicts new data. It is crucial that this data is not used during training to ensure that you are evaluating your model’s performance on completely unseen data.
12 |
13 | ### Importance in Supervised Learning
14 |
15 | - **Training Phase:** The model learns by finding patterns between the features and the corresponding labels from the training data. The goal is for the model to learn a function that maps the input features to the target output (labels).
16 |
17 | - **Testing Phase:** The trained model is then used to predict the labels for the test data. The accuracy of these predictions is evaluated by comparing them to the actual labels of the test data. This step is critical as it provides an unbiased evaluation of a model's predictive performance on new data.
18 |
19 | ### Summary
20 |
21 | The entire purpose of separating data into training and test sets in supervised learning is to ensure that the model can not only memorize the details of the training data but also generalize well to new, unseen situations, which is measured by how it performs on the test set. This structure helps in preventing overfitting and in verifying the model's ability to work in real-world scenarios where true labels are not known beforehand.
--------------------------------------------------------------------------------
/docs/styles/prettify-tomorrow.css:
--------------------------------------------------------------------------------
1 | /* Tomorrow Theme */
2 | /* Original theme - https://github.com/chriskempson/tomorrow-theme */
3 | /* Pretty printing styles. Used with prettify.js. */
4 | /* SPAN elements with the classes below are added by prettyprint. */
5 | /* plain text */
6 | .pln {
7 | color: #4d4d4c; }
8 |
9 | @media screen {
10 | /* string content */
11 | .str {
12 | color: #718c00; }
13 |
14 | /* a keyword */
15 | .kwd {
16 | color: #8959a8; }
17 |
18 | /* a comment */
19 | .com {
20 | color: #8e908c; }
21 |
22 | /* a type name */
23 | .typ {
24 | color: #4271ae; }
25 |
26 | /* a literal value */
27 | .lit {
28 | color: #f5871f; }
29 |
30 | /* punctuation */
31 | .pun {
32 | color: #4d4d4c; }
33 |
34 | /* lisp open bracket */
35 | .opn {
36 | color: #4d4d4c; }
37 |
38 | /* lisp close bracket */
39 | .clo {
40 | color: #4d4d4c; }
41 |
42 | /* a markup tag name */
43 | .tag {
44 | color: #c82829; }
45 |
46 | /* a markup attribute name */
47 | .atn {
48 | color: #f5871f; }
49 |
50 | /* a markup attribute value */
51 | .atv {
52 | color: #3e999f; }
53 |
54 | /* a declaration */
55 | .dec {
56 | color: #f5871f; }
57 |
58 | /* a variable name */
59 | .var {
60 | color: #c82829; }
61 |
62 | /* a function name */
63 | .fun {
64 | color: #4271ae; } }
65 | /* Use higher contrast and text-weight for printable form. */
66 | @media print, projection {
67 | .str {
68 | color: #060; }
69 |
70 | .kwd {
71 | color: #006;
72 | font-weight: bold; }
73 |
74 | .com {
75 | color: #600;
76 | font-style: italic; }
77 |
78 | .typ {
79 | color: #404;
80 | font-weight: bold; }
81 |
82 | .lit {
83 | color: #044; }
84 |
85 | .pun, .opn, .clo {
86 | color: #440; }
87 |
88 | .tag {
89 | color: #006;
90 | font-weight: bold; }
91 |
92 | .atn {
93 | color: #404; }
94 |
95 | .atv {
96 | color: #060; } }
97 | /* Style */
98 | /*
99 | pre.prettyprint {
100 | background: white;
101 | font-family: Consolas, Monaco, 'Andale Mono', monospace;
102 | font-size: 12px;
103 | line-height: 1.5;
104 | border: 1px solid #ccc;
105 | padding: 10px; }
106 | */
107 |
108 | /* Specify class=linenums on a pre to get line numbering */
109 | ol.linenums {
110 | margin-top: 0;
111 | margin-bottom: 0; }
112 |
113 | /* IE indents via margin-left */
114 | li.L0,
115 | li.L1,
116 | li.L2,
117 | li.L3,
118 | li.L4,
119 | li.L5,
120 | li.L6,
121 | li.L7,
122 | li.L8,
123 | li.L9 {
124 | /* */ }
125 |
126 | /* Alternate shading for lines */
127 | li.L1,
128 | li.L3,
129 | li.L5,
130 | li.L7,
131 | li.L9 {
132 | /* */ }
133 |
--------------------------------------------------------------------------------
/docs/LUI.md:
--------------------------------------------------------------------------------
1 | Creating a Logical, Linguistic User Interface (LUI) essentially means creating a user interface that interacts with users through language and logic processing, typically via text inputs and outputs. This kind of interface can be encountered in chatbots, virtual assistants, CLI (Command Line Interface) applications, and other applications where user interaction is primarily through text and logic instead of graphical elements.
2 |
3 | Components of Logical User Interface:
4 | 1. Parser
5 | Role: Interpret user inputs, deciphering the intent behind the user's text.
6 | Components: Tokenizer, Interpreter, etc.
7 | Operation: Divides inputs into manageable pieces and makes logical interpretations.
8 | 2. Processor
9 | Role: Manage the logical flow of the interaction, handle requests, and prepare responses.
10 | Components: Request Handler, Logic Unit, etc.
11 | Operation: Processes parsed input, applies business logic, and determines the appropriate response.
12 | 3. Responder
13 | Role: Create and manage responses to user inputs.
14 | Components: Response Generator, Formatter, etc.
15 | Operation: Formulates responses based on processed data and ensures they are communicated understandably.
16 | 4. User Input/Output Management
17 | Role: Handle user interactions.
18 | Components: Input Receiver, Output Sender, etc.
19 | Operation: Manages the retrieval of user input and the delivery of responses.
20 | Implementation Guidelines:
21 | 1. Define Language and Logic Rules
22 | Determine Syntax: Define the syntax and grammar acceptable by your LUI.
23 | Create Logic Models: Establish logical models that drive interactions and responses.
24 | 2. Construct Component Models
25 | Develop Components: Build and/or integrate existing NLP (Natural Language Processing) components.
26 | Implement Logic Processing: Ensure that your processor is able to handle various logical flows and conditions.
27 | 3. Build Response Mechanism
28 | Craft Responses: Ensure responses are linguistically sound and contextually relevant.
29 | Enable Variance: Embed variation in responses to make interactions more human-like.
30 | 4. Ensure Robustness
31 | Handle Varied Inputs: Ensure your LUI can manage a range of input styles and linguistics.
32 | Implement Fallbacks: Make sure your LUI handles unrecognized inputs gracefully.
33 | 5. User Experience
34 | Enable Clear Interaction: Ensure the user can easily understand how to interact.
35 | Provide Assistance: Embed help and guidance within the interface.
36 | 6. Scalability and Extensibility
37 | Ensure Scalability: Build your LUI to handle increasing user interactions.
38 | Enable Extensibility: Make it easy to add more features, logic, or language capabilities.
39 | Use-Case Example:
40 | Imagine a DevOps scenario where a developer interacts with a CLI application to manage cloud resources. The LUI will interpret commands and requests made in a natural language, such as:
41 |
42 | sql
43 | Copy code
44 | User: Create a new EC2 instance with 2 vCPUs and 8GB RAM.
45 | LUI: Sure, creating a new EC2 instance with the specified configuration...
46 | In this scenario, the LUI will parse the request, interpret the intent (create EC2 instance), extract parameters (2 vCPUs and 8GB RAM), process the request logically, and provide an appropriate response, all through linguistic interaction.
47 |
48 | Conclusion:
49 | Building a logical, linguistical user interface is a complex yet fascinating task that blends linguistics and logic processing. Careful planning, a deep understanding of linguistic structures, and efficient logical processing are crucial for crafting an LUI that offers a seamless and intuitive user experience.
--------------------------------------------------------------------------------
/npm/src/old/nouns/README.md:
--------------------------------------------------------------------------------
1 | Everyday examples of nouns and pronouns
2 |
3 | Oxford International English
4 | https://www.oxfordinternationalenglish.com › ...
5 |
6 | # Nouns
7 | A noun is what we call the word that names something or someone. A noun may be a person, a thing or a place. Nouns can play many roles within a sentence.
8 |
9 |
10 |
11 | ## What is a noun?
12 | Nouns make up a lot of the English language. There are also many different types.
13 |
14 | ##### These are all nouns:
15 | My father
16 | Your aunty
17 | The Queen
18 | Elvis Presley
19 |
20 | ##### The following places are also nouns:
21 | My house
22 | Mount Everest
23 | The bathroom
24 |
25 | **Nouns** can also **be things.** That includes imaginary items, concepts, activities, and other objects.
26 |
27 | Tab
28 | Football
29 | Table
30 | Freedom
31 |
32 | ## Common Nouns
33 | Generic (common) nouns can be put into three categories. These are collective nouns, abstract nouns and concrete nouns.
34 |
35 | A collective noun is a collection or a group.
36 |
37 | Examples of a collective noun:
38 |
39 | A murder of crows.
40 | A wild pack of dogs.
41 |
42 | A concrete noun is something physical, or real.
43 | Examples of concrete nouns:
44 | I have a cup of coffee.
45 | I heard some music.
46 |
47 | An abstracts noun is something we cannot perceive.
48 | The bravery he had shown.
49 | They had a lot of compassion.
50 |
51 | ## Nouns as subjects
52 |
53 | All sentences have a subject. The subject is always a noun—a person, thing, or a place that is being or doing the verb.
54 |
55 | ##### Examples of nouns as subjects:
56 |
57 | Edward felt excited.
58 | Louise was happy.
59 |
60 | Edward and Louise are the subjects in each of their sentences.
61 |
62 | ## Plural nouns
63 |
64 | A plural noun differs from a collection or group. A plural noun will require a -s or a -es to be added to the singular form. There are some exceptions.
65 |
66 | Examples of plural nouns:
67 | Singular: A dog
68 | Plural: The dogs
69 | Singular: A car
70 | Plural: The cars.
71 | Singular: A tax.
72 | Plural: The taxes.
73 |
74 | ## Possessive nouns
75 |
76 | A possessive noun is a noun that possesses something. You will see a possessive noun as it has an apostrophe.
77 |
78 | It was Joshua’s ball.
79 | I went to Ella’s house for dinner.
80 |
81 |
82 | When there is a plural noun that ends in s, the apostrophe is moved.
83 | My nephews’ first suit was expensive.
84 |
85 | ## Nouns as objects
86 |
87 | A noun can be an object in a sentence.
88 | Examples of a noun asana object:
89 | Give the shoes to them.
90 | Pass the books to her.
91 |
92 | # What is a pronoun?
93 |
94 | A pronoun’s distinguishing feature is that within a sentence, you can replace it. A pronoun is a word that replaces a noun to avoid repetition.
95 |
96 | Robert decided to sleep. Robert has always enjoyed taking long naps.
97 | Robert decided to sleep. He has always enjoyed taking long naps.
98 | Robert decided to sleep. My brother has always enjoyed taking long naps.
99 |
100 | In this case, the second Robert is replaced with ‘he’ and ‘my brother’. The change of pronoun stops the sentence from getting boring.
101 |
102 | ##### Personal Pronouns
103 |
104 | Personal pronouns are:
105 | They, Them, We, You, Me, I, Her, She, He, and Him
106 |
107 | ##### Relative Pronouns
108 |
109 | A relative pronoun connects relative clauses to independent clauses. They include:
110 | What, who, which, whom, that
111 |
112 | Example of using a relative pronoun:
113 | The person who posted these cards forgot to leave a number.
114 | My plant is very large, that new pot will fit perfectly.
115 |
116 | ## Antecedents
117 |
118 | A pronoun can be almost anything. It is a very versatile part of the English language. An antecedent is a noun or a noun phrase that is replaced later in a sentence.
119 |
120 | Example of an antecedent:
121 | My friends are the best; I love to be around them.
122 | In this example, the antecedent is family and replaced later by them.
123 | Henry is my dog; he is loud and loves to run.
124 | In this example, the antecedent is Henry, and the pronoun replacement is he.
125 |
126 | ### Indefinite pronouns
127 |
128 | For some occasions, you will not need to name a person or an object. In this case, you can refer to them with an indefinite pronoun.
129 |
130 | Examples of indefinite pronouns:
131 |
132 | Other, anybody, no one, none, some, everybody, one
133 | Example use of indefinite pronouns:
134 | The traffic jam meant that everyone was late.
135 |
136 | In this case, the indefinite pronoun used is everybody.
137 | No one else knows I have mismatched socks on.
138 | In this case, the indefinite pronoun used is no one.
139 |
140 | ### Interrogative pronouns
141 |
142 | An interrogative pronoun will be used in a question.
143 |
144 | Examples of interrogative pronouns:
145 | What, which, whose, and who
146 |
147 | An example use of an interrogative pronoun:
148 | What is your last name?
149 |
150 | In this example, the interrogative pronoun is what.
151 |
152 | Which colour is your favourite?
153 | In this example, the interrogative pronoun is which.
154 |
155 | Those are some of the examples, and example uses of nouns and pronouns that you will often see.
--------------------------------------------------------------------------------
/npm/README.md:
--------------------------------------------------------------------------------
1 | 
2 |
3 | # i.mLearning
4 |
5 | -----------
6 |
7 | ### [Project Status : Experimental and Under Development, Subject to Major Changes]
8 |
9 | `i.mlearning` is an experimental module under development within the `all.this` family, specifically designed to streamline the process of setting up structured datasets for supervised learning. The module aims to **provide a standardized framework for organizing and labeling data**, making it optimally structured for training machine learning models, particularly in conjunction with the [neurons.me](https://neurons.me) platform.
10 |
11 | [mlearning.studio](https://mlearning.studio)
12 |
13 | The module is in active development, and as such, it is subject to significant changes as we refine our approach and methodologies to best support supervised learning processes.
14 |
15 | ----------
16 |
17 | ## Core Vision and Purpose
18 | The primary goal of `i.mlearning` is to facilitate the creation of well-organized, labeled datasets that can be directly utilized for training machine learning models. This involves:
19 |
20 | - **Structured Data Directory**: Providing a template or blueprint for organizing data files, such as images or audio clips, into labeled directories (e.g., `cats/` for cat images) to support straightforward supervised learning.
21 | - **Data Labeling Consistency**: Ensuring that all data within the structure is appropriately labeled and categorized to aid in the accurate training of machine learning models, enhancing the overall effectiveness and reliability of the learning process.
22 | - **Integration with neurons.me**: Making the structured and labeled data easily accessible and compatible with neurons.me, allowing for seamless data processing, model training, and analysis within the platform.
23 |
24 | ## Getting Started
25 | To begin experimenting with `i.mlearning`, you can clone or download the module and explore the provided directory structures and guidelines. As this module is still under development, we encourage experimentation and feedback:
26 |
27 | ```bash
28 | npm i i.mlearning
29 | ```
30 |
31 | **Note:** As `i.mlearning` is in experimental mode, please be prepared for ongoing changes and updates. Your feedback and contributions can significantly shape its evolution.
32 |
33 | ## Contributing to `i.mlearning`
34 | We welcome contributions, suggestions, and feedback from the community to enhance and refine `i.mlearning`. Whether you have ideas for new features, improvements to existing structures, or feedback on the module's usability, your input is invaluable.
35 |
36 | ## Licensing and Usage
37 | `i.mlearning` is released under an open-source license, allowing you to use and modify the module freely within your projects. As the module evolves, please refer to the LICENSE file for the most current licensing information.
38 |
39 | ## Join Us in Shaping i.mlearning
40 | Your involvement can help shape `i.mlearning` into a robust tool for data structuring in machine learning. Join us in this exciting journey to simplify and enhance the preparation of data for machine learning, contributing to the broader goals of accessibility and efficiency in AI and data science.
41 |
42 | For more details, visit our [project page](https://www.neurons.me) or check out the [neurons.me platform](https://www.neurons.me/all-this).
43 |
44 | If you have suggestions or issues, please open an issue. We encourage contributions from the community.
45 |
46 |
47 | ----------
48 |
49 | # About All.This
50 |
51 | ## Modular Data Structures:
52 |
53 | **[this.me](https://suign.github.io/this.me) - [this.audio](https://suign.github.io/this.audio) - [this.text](https://suign.github.io/this.text) - [this.wallet](https://suign.github.io/this.wallet) - [this.img](https://suign.github.io/this.img) - [this.pixel](https://suign.github.io/Pixels) - [be.this](https://suign.github.io/be.this) - [this.DOM](https://suign.github.io/this.DOM) - [this.env](https://suign.github.io/this.env/) - [this.GUI](https://suign.github.io/this.GUI) - [this.be](https://suign.github.io/this.be) - [this.video](https://suign.github.io/this.video) - [this.atom](https://suign.github.io/this.atom) - [this.dictionaries](https://suign.github.io/this.dictionaries/)**
54 |
55 | **Each module** in **[all.this](https://neurons.me/all-this)** represents a specific **datastructure**. These classes encapsulate the functionalities and **data specific to their domain.**
56 |
57 | ## **Utils**
58 |
59 | **[all.this](https://neurons.me/all-this)** not only aggregates these modules but also provides utilities to facilitate the integration, management, and enhancement of these data structures. **For example:**
60 |
61 | *The integration with [cleaker](https://suign.github.io/cleaker/) ensures each module instance has a **unique cryptographic identity**, enhancing security and data integrity.*
62 |
63 | ### Neurons.me Ecosystem Glossary:
64 |
65 | visit: [Neurons.me Glossary](https://suign.github.io/neurons.me/Glossary)
66 |
67 | ## License & Policies
68 |
69 | - **License**: MIT License (see LICENSE for details).
70 |
71 | - **Privacy Policy**: Respects user privacy; no collection/storage of personal data.
72 |
73 | - **Terms of Usage**: Use responsibly. No guarantees/warranties provided. [Terms](https://www.neurons.me/terms-of-use) | [Privacy](https://www.neurons.me/privacy-policy)
74 |
75 | **Learn more** at https://neurons.me
76 |
77 | **Author:** SuiGn
78 |
79 | [By neurons.me](https://neurons.me)
80 |
81 | 
82 |
--------------------------------------------------------------------------------
/docs/README.md:
--------------------------------------------------------------------------------
1 | /* In i.mlearning/index.js
134 | ⓝⓔⓤⓡⓞⓝⓢ.ⓜⓔ
135 | 🆂🆄🅸🅶🅽 */
136 |
137 | /**
138 | * @module imlearning
139 | * @description Exports the main functionalities of the i.mlearning library.
140 | */
141 |
142 | import imLearning from './src/imLearning.js';
143 |
144 | /**
145 | * The main export object of i.mlearning package.
146 | * @type {Object}
147 | */
148 | const imlearning = {
149 | imLearning
150 | };
151 |
152 | export default imlearning;
153 | console.log("i.mLearning loaded;");
154 |
122 |
123 |
126 |
127 |
128 |
129 |
130 |
131 |
132 |
133 |
156 |
157 |
158 |
159 |
160 |
161 |
162 |
163 |
186 |
187 | Source
124 |