Data Mining Docs Topic Reviewed
This commit is contained in:
Luis Fernando Molina committed
1 parent
0f0ede81b2
commit
173f752dc1
14 files changed
+142
-75
No files matched your search
+15
-10
@@ -3,14 +3,14 @@
|
||||
"pageNumber": "1",
|
||||
"type": "Data Mining - Introduction",
|
||||
"definition": {
|
||||
"text": "Data Mining in Superalgos means extracting data from external sources, procesing that data in order to have it ready for consumption by trading strategies.",
|
||||
"updated": 1621694013759
|
||||
"text": "Data Mining in Superalgos means extracting data from external sources and procesing that data in order to have it ready for consumption by trading strategies.",
|
||||
"updated": 1621899758597
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Superalgos offers a set of Data Mining tools. With those, users can fetch data from external sources, process them into more elaborate datasets, plot them at the charts and ultimately consume the data within their trading strategies.",
|
||||
"updated": 1621694036120
|
||||
"text": "Superalgos offers a set of Data Mining tools. With those, users can fetch data from external sources, process them into more elaborate datasets, plot them at the charts, feed ML Bot's models and ultimately consume the data within their trading strategies.",
|
||||
"updated": 1621899827534
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
@@ -18,8 +18,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "All of the data inside the Superalgos system has an origin somewhere at the Internet, outisde of the system. There are currently to ways to bring data into the system:",
|
||||
"updated": 1621705240818
|
||||
"text": "All of the data inside the Superalgos system has an origin somewhere outside the system, usually somewhere at the Internet. There are currently 3 ways to bring data into the system:",
|
||||
"updated": 1621899913780
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
@@ -28,13 +28,18 @@
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Without coding an Algorithm: (available since Beta 10) via the API Data Fetcher Bot, this method involves designing an API Map which is later feeded to an API Data Fetcher Bot at run time so that it can fetch data from APIs without needing the user to write a single line of code at all.",
|
||||
"updated": 1621705316432
|
||||
"text": "Without coding an Algorithm: (available since Beta 10) via the API Data Fetcher Bot, this method involves designing an API Map which is later feeded to an API Data Fetcher Bot at runtime so that it can fetch data from APIs without needing the user to write a single line of code at all.",
|
||||
"updated": 1621900116590
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "External processing: it is also possible to gather the data and process it outside the system, and put it in the right folder, with the right format, and in this way feed the system with data. This use case is not the most popular, but it is a valid possibility.",
|
||||
"updated": 1621900136004
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Once the data is in the system, it is then processed for different reasons by Indicator Bot s. Some of the processed data might be plotted, and some might be consumed from a Trading Strategy.",
|
||||
"updated": 1621691628626
|
||||
"text": "Once the data is in the system, it is then processed for different reasons by Indicator Bot s. Some of the processed data might be plotted, some might feed machile learning bots, and some might be consumed from a Trading Strategy.",
|
||||
"updated": 1621900199919
|
||||
}
|
||||
]
|
||||
}
|
||||
+10
-10
@@ -36,8 +36,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "Both of these 2 workflows start by producing Raw Data that has to be digested by Indicator Bots.",
|
||||
"updated": 1621698358246
|
||||
"text": "The data just arrived from an external source is considered Raw Data. Both of these 2 workflows produce Raw Data that has to be digested by Indicator Bots.",
|
||||
"updated": 1621900437233
|
||||
},
|
||||
{
|
||||
"style": "Subtitle",
|
||||
@@ -50,8 +50,8 @@
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Standarize Datasets: They are used for standarization of raw data extracted from the internet by Sensor Bot s or API Data Fetcher Bot s. Once data is standarized, it can be run through other Indicator Bot s that will extract the juice out of them. Once standarized data can also be plotted and consumed from trading strategies. By standarizing we are specifically referring to transforming the data into a Dataset type that can be used for Plotting, to feed Learning Bots and Trading Bots. These Dataset types are Multi-Period-Daily and Milti-Period-Market. ",
|
||||
"updated": 1621705567513
|
||||
"text": "Standarize Datasets: They are used for standarization of raw data extracted from the internet by a Sensor Bot or an API Data Fetcher Bot. Once data is standarized, it can be run through other Indicator Bot s that will extract the juice out of them. Once standarized, data can also be plotted and consumed from trading strategies. By standarizing we are specifically referring to transforming the data into a Dataset type that can be used for Plotting, to feed Learning Bots and Trading Bots. These Dataset types are Multi-Period-Daily and Milti-Period-Market.",
|
||||
"updated": 1621900536868
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
@@ -60,13 +60,13 @@
|
||||
},
|
||||
{
|
||||
"style": "Subtitle",
|
||||
"text": "Indicators -> Plotters (for users)",
|
||||
"updated": 1621698262190
|
||||
"text": "Indicators -> Plotters",
|
||||
"updated": 1621900608845
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Plotters are intended for users, not for bots. Plotters will render at the charts information of a Dataset based on the plotter's definition. Plotters can only read data from certain Dataset types, you will learn which ones later at this Topic.",
|
||||
"updated": 1621697151527
|
||||
"text": "Plotters are tools for users, not for bots. Plotters will render at the charts information of a Dataset based on the plotter's definition. Plotters can only read data from certain Dataset types, you will learn which ones later at this Topic.",
|
||||
"updated": 1621900619194
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -88,8 +88,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Trading bots are the final consumer of data, which they use to take trading decisions based on their definitions. The ultimate purpose of the whole Data Mining operation is to digest data so that is is easily accesible for trading strategies.",
|
||||
"updated": 1621696940017
|
||||
"text": "Trading bots are the ultimate consumer of data, which they use to take trading decisions based on their definitions. The ultimate purpose of the whole Data Mining operation is to digest data so that is is easily accesible for trading strategies.",
|
||||
"updated": 1621900703336
|
||||
}
|
||||
]
|
||||
}
|
||||
+12
-8
@@ -14,23 +14,27 @@
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Single File: As the name suggest, this Dataset contains only one file with all the data in there. It is not frequently used. So far is the Dataset type where data comming from Webhooks is stored at. It is stored in this way because it assumed that not a lot of data will come through this pipe, only signals produced by external systems. Webhooks feature is expected to evolve in the future maniging the incoming data in another type of Dataset. This Dataset type can be plotted and it's data consumed from withing trading strategies.",
|
||||
"updated": 1621696354757
|
||||
"text": "Single-File: As the name suggest, this Dataset contains only one file with all the data in there. It is not frequently used. So far is the Dataset type where data comming from Webhooks is stored at. It is stored in this way because it is assumed that not a lot of data will come through this pipe, only signals produced by external systems. Webhooks feature is expected to evolve in the future maniging the incoming data in another type of Dataset. This Dataset type can be plotted and it's data consumed from withing trading strategies. The API Data Fetcher Bot also can save Raw Data in this type of dataset, if needed.",
|
||||
"updated": 1621901077561
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "One-Min Daily: This Dataset type organizes data in one file per day, and as the name suggest, expects the data itself to belong to time periods of one minute. This type of Dataset can not be plotted or it's data consumed from trading strategies.",
|
||||
"updated": 1621696328584
|
||||
"text": "One-Min-Daily: This Dataset type organizes data in one file per day, and as the name suggest, expects the data itself to belong to time frames of one minute. This type of Dataset can not be plotted or it's data consumed from trading strategies.",
|
||||
"updated": 1621901069906
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Multi Period Daily: This Dataset type organizes data in one file per day for each Time Frame ranging from 1 minute to 45 minuntes. The data of this type of Dataset can be plotted and can be consumed by trading strategies.",
|
||||
"updated": 1621696475925
|
||||
"text": "Multi-Period-Daily: This Dataset type organizes data in one file per day for each Time Frame ranging from 1 minute to 45 minuntes. The data of this type of Dataset can be plotted and can be consumed by trading strategies.",
|
||||
"updated": 1621901061453
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Multi Period Market: This Dataset type organizes data in only one file each Time Frame ranging from 1 hour to 24 hours. That means that the whole market history will be stored in one single file for each time frame. For example candles of 1 hour for a certain market, will be stored in a single file. The data of this type of Dataset can be plotted and can be consumed by trading strategies.",
|
||||
"updated": 1621696582451
|
||||
"text": "Multi-Period-Market: This Dataset type organizes data in only one file for each Time Frame ranging from 1 hour to 24 hours. That means that the whole market history will be stored in one single file for each time frame. For example candles of 1 hour for a certain market, will be stored in a single file. The data of this type of Dataset can be plotted and can be consumed by trading strategies.",
|
||||
"updated": 1621901050963
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "By far, the most popular Dataset Types are Multi-Period-Daily and Multi-Period-Market. "
|
||||
}
|
||||
]
|
||||
}
|
||||
+9
-4
@@ -62,8 +62,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The Asset Metrics Indicator Bot, defined at the Messari Data Mine uses a Standard Converter from One-Min-Daily Dataset type to Multi-Period-Daily and Multi-Period-Market Dataset types. To use the conferter, the bot's Process Definition nodes need to have at their config the framework of this converter.",
|
||||
"updated": 1621711379111
|
||||
"text": "The Asset Metrics Indicator Bot, defined at the Messari Data Mine uses a Standard Converter from One-Min-Daily Dataset type to Multi-Period-Daily and Multi-Period-Market Dataset types. To use the converter, the bot's Process Definition nodes need to have at their config the framework of this converter.",
|
||||
"updated": 1621901387602
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -82,8 +82,13 @@
|
||||
},
|
||||
{
|
||||
"style": "Json",
|
||||
"text": "{\n \"codeName\": \"From-One-Min-To-Multi-Period-Market\",\n \"normalWaitTime\": 0,\n \"retryWaitTime\": 10000,\n \"framework\": {\n \"name\": \"From-One-Min-To-Multi-Period-Market\"\n }\n}",
|
||||
"updated": 1621701757557
|
||||
"text": " {\n \"codeName\": \"From-One-Min-To-Multi-Period-Market\",\n \"normalWaitTime\": 0,\n \"retryWaitTime\": 10000,\n \"framework\": {\n \"name\": \"From-One-Min-To-Multi-Period-Market\"\n }\n}",
|
||||
"updated": 1621901499029
|
||||
},
|
||||
{
|
||||
"style": "Success",
|
||||
"text": "You will need the standar converter everytime you use the API Data Fetcher Bot to extract data from some Inernet API. The bot will usually save the data in a One-Min-Daily Dataset Type, and you will need to setup and Indicator Bot with two processes, in order to convert the One-Min-Daily Dataset Type into a Multi-PeriodDaily and a Multi-Period-Market Dataset Type. ",
|
||||
"updated": 1621901677409
|
||||
}
|
||||
]
|
||||
}
|
||||
+18
-15
@@ -9,8 +9,8 @@
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "When running custom code, users have full control of the process and there is no limit on what it can be done in terms of data manipulations. The trade off is that the user must be a developer.",
|
||||
"updated": 1621702329009
|
||||
"text": "When running custom code, users have full control of the process and there is no limit on what it can be done in terms of data manipulation. The trade off is that the user must be a developer.",
|
||||
"updated": 1621902338195
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -31,11 +31,13 @@
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Custom Code: This means the Indicator will use custom made code to handle all data transformations. "
|
||||
"text": "Custom Code: This means the Indicator Bot will use custom made code to handle all data transformations.",
|
||||
"updated": 1621902418790
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "UI-Defined: This means that the indictor will base it's behaviour on the definitioins defined at the UI including the code snippets provided by the user."
|
||||
"text": "UI-Defined: This means that the Indictor Bot will base it's behaviour on the definitioins at the UI including the code snippets provided by the user.",
|
||||
"updated": 1621902442579
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
@@ -65,8 +67,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The way to implement a Custom Code Indicator is to set up at the config of the Process Definition that there is custom code for this process. Specifically, you need to add the botModule property to the config. This is how it looks like.",
|
||||
"updated": 1621703510791
|
||||
"text": "The way to implement a Custom Code Indicator tell the Bot at the config of the Process Definition that there is custom code for this process. Specifically, you need to add the botModule property to the config. This is how it looks like.",
|
||||
"updated": 1621902538119
|
||||
},
|
||||
{
|
||||
"style": "Json",
|
||||
@@ -75,8 +77,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Then you will need to locate the Project Schema file for the project your bot belongs to. Inside of that file you will need to add some definitions in order for the system to be able to laod your new module at runtime and later execute it once users run your bot implemented in this way.",
|
||||
"updated": 1621703616902
|
||||
"text": "Then you will need to locate the Project Schema File for the project your bot belongs to. Inside of that file you will need to add some definitions in order for the system to be able to laod your new module at runtime and later execute it once users run your bot implemented in this way.",
|
||||
"updated": 1621902552523
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -84,7 +86,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The definition to be added there should be something like this:"
|
||||
"text": "The definition to be added there should look something like this:",
|
||||
"updated": 1621902599128
|
||||
},
|
||||
{
|
||||
"style": "Json",
|
||||
@@ -93,8 +96,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "After that you will need to add a new Javascript module with your code. ",
|
||||
"updated": 1621704019288
|
||||
"text": "After that you will need to add to the codebase a new Javascript module with your code.",
|
||||
"updated": 1621902622372
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
@@ -127,13 +130,13 @@
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Multi-Period-Daily: It is used to process data currently available at a Dataset of type Multi-Period-Daily and produce an output of a Dataset of the same type. How the data is going to be transformed is up to the user, since at the UI users can provide code snippets to handle the data transformation at the Data Building Procedure node.",
|
||||
"updated": 1621703225204
|
||||
"text": "Multi-Period-Daily: It is used to process data currently available at a Dataset of type Multi-Period-Daily and produce as output a Dataset of the same type. How the data is going to be transformed is up to the user, since at the UI users can provide code snippets to handle the data transformation at the Data Building Procedure node.",
|
||||
"updated": 1621902697553
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Multi-Period-Market: It is used to process data currently available at a Dataset of type Multi-Period-Market and produce an output of a Dataset of the same type. How the data is going to be transformed is up to the user, since at the UI users can provide code snippets to handle the data transformation at the Data Building Procedure node.",
|
||||
"updated": 1621703273921
|
||||
"text": "Multi-Period-Market: It is used to process data currently available at a Dataset of type Multi-Period-Market and produce as output a Dataset of the same type. How the data is going to be transformed is up to the user, since at the UI users can provide code snippets to handle the data transformation at the Data Building Procedure node.",
|
||||
"updated": 1621902733616
|
||||
},
|
||||
{
|
||||
"style": "Subtitle",
|
||||
|
||||
@@ -51,7 +51,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Data Mines might depend of other Data Mines if any of their bots depend on bots belonging to other Data Mines. You will learn further down this Topic how a bot can depend on other bots in detail. In a nutshell, they can depend in two ways:"
|
||||
"text": "Data Mines might depend of other Data Mines if any of their bots depend on bots belonging to other Data Mines. You will learn further down this Topic how a bot can depend on other bots in detail. In a nutshell, they can depend in 3 ways. They can have a:",
|
||||
"updated": 1621903084681
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
@@ -68,8 +69,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "When a Data Mine depends on another Data Mine, both need to be present at the Workspace where the Task involving the execution of the Bot is.",
|
||||
"updated": 1621709928655
|
||||
"text": "When a Data Mine depends on another Data Mine, both need to be present at the Workspace where the Task defining the execution of the Bot is located.",
|
||||
"updated": 1621903174117
|
||||
}
|
||||
]
|
||||
}
|
||||
+9
-4
@@ -3,8 +3,8 @@
|
||||
"pageNumber": "7",
|
||||
"type": "Data Mining - Managing Execution",
|
||||
"definition": {
|
||||
"text": "Bots can execute at their own pace or they could wait for other bots to finish executing in order to start. ",
|
||||
"updated": 1621710031525
|
||||
"text": "Bots can execute at their own pace or they can wait for other bots to finish executing in order for them to start.",
|
||||
"updated": 1621903220369
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
@@ -38,8 +38,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "This is how to configure the Process Definition of a Bot that it's execution depends on other Bot. Here the normalWaitTime has a value of zero, which will force the boot to inmediatelly run the next loop, but since there is an Execution Started Event defined, that will make it wait until the referenced Bot finishes.",
|
||||
"updated": 1621710760133
|
||||
"text": "This is how to configure the Process Definition of a Bot that it's execution depends on other Bot. Here the normalWaitTime has a value of zero, which will force the Bot to inmediatelly run the next loop, but since there is an Execution Started Event defined, that will make it wait until the referenced Bot finishes.",
|
||||
"updated": 1621903624630
|
||||
},
|
||||
{
|
||||
"style": "Json",
|
||||
@@ -50,6 +50,11 @@
|
||||
"style": "Success",
|
||||
"text": "In this case users must also define which bot to wait for. To do this they stablish a reference from the Execution Started Event node of the Bot that needs to wait, to the Execution Finished Event of the Bot they are waiting for to finish.",
|
||||
"updated": 1621710539966
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "From the deployment point of view, the dependant bots can be physically located at the same machine, or at multiple different machines. Superalgos handles the syncronization across multiples machines.",
|
||||
"updated": 1621903914878
|
||||
}
|
||||
]
|
||||
}
|
||||
+2
-1
@@ -26,7 +26,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "When a Bot has a Data Dependency of a dataset produced by a Bot defined in a different Data Mine, then both Data Mines must be present at the Workspace where the Bot is going to be lauched at."
|
||||
"text": "When a Bot has a Data Dependency of a dataset produced by a Bot defined at a different Data Mine, then both Data Mines must be present at the Workspace where the Bot is going to be lauched at.",
|
||||
"updated": 1621903950116
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
+8
-6
@@ -3,18 +3,19 @@
|
||||
"pageNumber": "9",
|
||||
"type": "Data Mining - Status Reports",
|
||||
"definition": {
|
||||
"text": "Status Reports are files produced by each Bot's processes with some key information that the Bot needs to save in order to remember the next time is run.",
|
||||
"updated": 1621716668465
|
||||
"text": "Status Reports are files produced by each Bot's processes with some key information that the Bot needs to save in order to remember it the next time is run.",
|
||||
"updated": 1621904046327
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Most Bots in superalgos are run by the Task Server and they implement a Main Loop. At each loop execution, bots do their job and at the end they go to sleep. How much time they sleep and other details are configured at the Bot's process. ",
|
||||
"updated": 1621717056723
|
||||
"text": "Most Bots in Superalgos are run by the Task Server and they implement a Main Loop. At each loop execution, bots do their job and at the end they go to sleep. How much time they sleep and other details are configured at the Bot's Process Definition.",
|
||||
"updated": 1621904131214
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Before going to sleep all the memory is flushed from all information related to the bot, so that machine resources are freed for other bots in the same machine to use. There is some info Bot's need to remember between every execution of the Main Loop, and between executions of the Task itself. That info is stored in a JSON / text file called the Status Report."
|
||||
"text": "Before going to sleep, all the memory is flushed from all information related to the Bot, so that hardware resources are freed for other bots in the same machine to use. There is some info Bots need to remember between every execution of the Main Loop, and between executions of the Task itself. That info is stored in a JSON / text file called the Status Report.",
|
||||
"updated": 1621904194069
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -27,7 +28,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "Status Report files also might include a data structure called Inter Execution Memory. Status information is kind of standard for all types of bots. Inter Execution Memory on the other hand depends on each Bot type and what is actually processing."
|
||||
"text": "Status Report files also might include a data structure called Inter Execution Memory. Status information is kind of standard for all types of bots. Inter Execution Memory on the other hand, depends on each Bot type and what is actually processing.",
|
||||
"updated": 1621904260686
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
+4
-3
@@ -19,8 +19,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Bots that produce Raw Data usually do not depend on any other Bot's status and they are usually the root of a dependency tree or graph. Any Bot might have zero to many status dependencies. For each Status Dependency, the Bot's process at runtime will load the Status Report file of the dependent Bot and let extract from there the information it needs.",
|
||||
"updated": 1621718085593
|
||||
"text": "Bots that produce Raw Data usually do not depend on any other Bot's status and they are usually the root of a dependency tree or graph. Any Bot can have from zero to many status dependencies. For each Status Dependency, the Bot's process at runtime will load the Status Report file of the dependent Bot and will extract from there the information it needs.",
|
||||
"updated": 1621904417277
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
@@ -29,7 +29,8 @@
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Status Dependency can be classified by their utility. This make it easier for processes to handle them in code. There are currently three different utilities:"
|
||||
"text": "A Status Dependency can be classified by it's utility. This make it easier for processes to handle them in code. There are currently three different utilities:",
|
||||
"updated": 1621904453267
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
|
||||
+28
-4
@@ -13,13 +13,37 @@
|
||||
"updated": 1621719049976
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "On one hand, the definitions at the Data Mine already contain the 3 types of relationships between Bots. Execution, Data Dependency and Status Dependency. On the other hand, the network hierarchy contains all the information needed to guess where the dependent bots are running (looking at the Tasks it can know at which machine in the network) and where the Datasets are in the network (looking at the Data Storage section).",
|
||||
"updated": 1621719258047
|
||||
"style": "Title",
|
||||
"text": "How does Superalgos know how to coordinate Bots?",
|
||||
"updated": 1621904714762
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Everytime a Task is executed, the whole Network hierarchy, together with the bot's definitions at Data Mines are sent to the Task Server which will help the bot to load the datasets defined as Data Depencies, the Status Reports defined as Status Dependencies and wait for the Bot's defined at the Execution Dependencies, no matter where all those resources are within the physical network. "
|
||||
"text": "Everything that needs to be known is already defined at the Workspace.",
|
||||
"updated": 1621904768357
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "In Data Mines: The definitions at the Data Mine contain the 3 types of relationships between Bots. Execution, Data Dependency and Status Dependency. "
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "At the Network: The Network hierarchy contains all the information needed to know where the dependent bots are running (looking at the Tasks we can know at which machine in the network) and where the Datasets are in the network (looking at the Data Storage section)."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How does a Bot know where are it's dependencies running?",
|
||||
"updated": 1621904824161
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Everytime a Task is executed, the whole Network hierarchy, together with the bot's definitions at Data Mines are sent to the Task Server. This includes not only the Bot to be ran definitions, but also all the definitions of the dependent bots. ",
|
||||
"updated": 1621904939603
|
||||
},
|
||||
{
|
||||
"style": "Success",
|
||||
"text": "At runtime, Superalgos will provide the Bot with the Datasets defined at Data Depencies, the Status Reports defined as Status Dependencies and if necesary, it iwll help the Bot wait for the Bot defined as an Execution Dependency, no matter where all those resources are within the physical network.",
|
||||
"updated": 1621905102590
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -3,14 +3,14 @@
|
||||
"pageNumber": "12",
|
||||
"type": "Data Mining - Products",
|
||||
"definition": {
|
||||
"text": "All Datasets of any type of bot within the Superalgos system are considered products of the Bot that produced them. Why products? Because these dataset once the Superalgos Network is implemente wil be able to be sold to other users in the form of subscriptions.",
|
||||
"updated": 1621721546261
|
||||
"text": "All Datasets of any type of bot within the Superalgos system are considered products of the Bot that produced them. Why products? Because users will be able to sell hese datasets in the form of subscriptions once the Superalgos Network is implemented.",
|
||||
"updated": 1621905194343
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "In the future, users will be able to offer products to the rest of the users of the Superalgos Network / Marketplace. A single bot might produce many as many products as the bot designer wishes. Each product might contain one or more datasets. ",
|
||||
"updated": 1621721677750
|
||||
"text": "In the future, users will be able to offer products to the rest of the users of the Superalgos Network / Superalgos Marketplace. A single bot might produce as many products as the bot designer wishes. Each product might contain one or more datasets.",
|
||||
"updated": 1621905284676
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -3,13 +3,14 @@
|
||||
"pageNumber": "13",
|
||||
"type": "Data Mining - Plotting",
|
||||
"definition": {
|
||||
"text": "Each product might have one Plotter Module associated with it. This Plotter Module has all the definitions to inteerpret the Product's datasets and render the information at the charts.",
|
||||
"updated": 1621721823675
|
||||
"text": "Each product might have one Plotter Module associated with it. This Plotter Module has all the definitions needed to interpret the Product's datasets and render the information at the charts.",
|
||||
"updated": 1621905321330
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Right click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode. Then you can use docs.save to save your changes and app.contribute to send it to the main repository."
|
||||
"text": "Superalgos has the capability to allow it's users to create plotters without writing any code at all. The ploter is defined at the Designer Space, and by the means of defining vertices and polygons, users can create custom charts for any Dataset.",
|
||||
"updated": 1621905478694
|
||||
}
|
||||
]
|
||||
}
|
||||
+15
@@ -0,0 +1,15 @@
|
||||
{
|
||||
"topic": "Data Mining",
|
||||
"pageNumber": "13.1",
|
||||
"type": "Data Mining - Fetching Data From APIs",
|
||||
"definition": {
|
||||
"text": "Superalgos allow it's user to fetch data from any API on the Internet without needing to write code to do it. Instead, users design an API Map, which is a set of definitions of how a Bot can access a certain API and how to interpret the API Server responses. With this API Maps, a API Data Fetcher Bot can be configured to extract data from any API Server and stored inside the system as Raw Data that later can processed and consumed by other Bots.",
|
||||
"updated": 1621905787119
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Right click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode. Then you can use docs.save to save your changes and app.contribute to send it to the main repository."
|
||||
}
|
||||
]
|
||||
}
|
||||
Reference in new issue
Block a user