Definition in function
This commit is contained in:
1 parent
51f3d50af7
commit
47041b4676
223 files changed
+513
-497
No files matched your search
@@ -3,8 +3,8 @@
|
||||
"definition": "Actual rate is the number reported by the exchange as the rate at which an order was filled.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Actual Rate Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Algorithm name is the name of the execution algorithm that opened the order, as specified in the trading system.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Algorithm Name Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Annualized rate of return is the equivalent ROI scaled to one year.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Annualized Rate Of Return Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,12 +3,12 @@
|
||||
"definition": "A backtesting session is a trading mode by which the trading bot instance reads historic market data in a user-defined datetime range, applies the rules defined in the associated trading system, and generates a trading simulation.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Backtesting Session Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "A backtesting session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it. Fordward Testing bla bla bla"
|
||||
"text": "A backtesting session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Balance is the running balance, that is, the amount of the asset that exists at any point in time.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Balance Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Begin balance is the balance at the datetime of the begin property of the parent node or concept.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Begin Balance Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Begin rate is the close rate of the candle corresponding to the datetime of the begin property.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Begin Rate Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Begin is the datetime at the moment the object represented by the parent node began to exist.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Begin Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A bot data dependencies node is an organizational device used to arrange data dependencies corresponding to a specific bot.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Bot Data Dependencies Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -24,7 +24,7 @@
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "See the data dependency schema document and the Adding a Data Dependecy Node section for all the details."
|
||||
"text": "See the data dependency node definition and the Adding a Data Dependecy Node section for all the details."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A bot products node is an organizational device used to arrange data products corresponding to a specific bot.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Bot Products Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -28,7 +28,7 @@
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "See the data product schema document and the Adding a Data Product Node section for all the details."
|
||||
"text": "See the data product node definition and the Adding a Data Product Node section for all the details."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The calculations procedure processes information to be fed to calculated properties. Calculated properties are not stored in the data set; instead, they are calculated in real-time as the data is consumed by others.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Calculations Procedure Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The cancel order event makes cancelling limit orders possible.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Cancel Order Event Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A chart points groups definitions of coordinate points used to define polygons.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Chart Points Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The charting space is the hierarchy that governs the configuration of the charts, and the bidimensional space on which charts are drawn.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Charting Space Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The close execution node groups all execution algorithms involved in the process of closing a position.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Close Execution Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The close stage event defines the set of rules that need to be met for the corresponding stage to be closed.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Close Stage Event Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The close stage deals with the definitions that make up the logic to close a position, including the target rate and size, and order execution.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Close Stage Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Conditions are rules within a situation. When all conditions under a situation validate true, then the situation gets validated as well, and the associated event is triggered.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Condition Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The create order event controls the placement of orders.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Create Order Event Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The crypto ecosystem is a hierarchy that contains definitions about third-parties, including exchanges and their markets, as well as accounts of users with those third parties.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Crypto Ecosystem Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The current object refers to the context in which instances of several other objects exist—like episode, strategy, position, strategy stages, and so on—in particular, the instances that are open at the time of evaluation, hence the adjective current.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Current Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The trading bot performs its duties in regards to exchange orders and accounts in two consecutive cycles for each candle.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Cycle Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A dashboard is a collection of time machines, each containing any number of charts.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Dashboard Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The data building procedure processes information to be fed to properties that are stored in the output dataset.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Building Procedure Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A data dependency folder node is an organizational device used to map the arrangement of product definition folders of a given bot.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Dependency Folder Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Data dependencies are references established with dataset definitions of other bots, determining which datasets the process establishing the reference uses as input.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Dependency Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Data mine data dependencies are references established with entire data mines to facilitate establishing data dependencies with multiple datasets in the given data mine.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Mine Data Dependencies Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -24,7 +24,7 @@
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "See the data dependency schema document and the Adding a Data Dependecy Node section for all the details."
|
||||
"text": "See the data dependency node definition and the Adding a Data Dependecy Node section for all the details."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Data mine products are references established with data mines to facilitate establishing data product references with multiple products in the given data mine.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Mine Products Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -28,7 +28,7 @@
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "See the data product schema document and the Adding a Data Product Node section for all the details."
|
||||
"text": "See the data product node definition and the Adding a Data Product Node section for all the details."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The data mine tasks node is an organizational device that groups tasks corresponding to the referenced data mine.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Mine Tasks Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
@@ -24,7 +24,7 @@
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "See the task schema document and the Adding a Task Node section for all the details."
|
||||
"text": "See the task node definition and the Adding a Task Node section for all the details."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A data mine is a hierarchy that contains definitions of sensor and indicators bots, and their plotters. These definitions make up the actual programs of such bots—the source code.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Mine Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Session independent data refers to data generated by sensors and indicators, not related to trading sessions.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Mines Data Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A data product folder node is an organizational device used to map the arrangement of product definition folders as may exist in the bot definition of the corresponding data or trading mine.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Product Folder Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A data product represents the collection of datasets generated by the instance of a bot as defined in the corresponding data mine or trading mine.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Product Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The data storage node holds the definitions as to what data is stored in the corresponding network node.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Data Storage Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
{
|
||||
"type": "Dataset Definition",
|
||||
"definition": "A data set is a collection of files stored in the designated location, as per the definitions on the referenced data product in the corresponding data mine.",
|
||||
"definition": "A dataset definition contains a configuration file that defines many aspects of the dataset. There are two types of dataset definitions: Multi-Period-Market and Multi-Period-Daily.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Dataset Definition Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Days counts the number of days through which the trading bot has cycled since the object represented by the parent node was open.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Days Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The design space is the visual environment that hosts all system and user definitions. In practical terms, it is the black space below the slider that splits the screen horizontally, separating the design space in the bottom from the charting space on top. As a hierarchy, it features nodes that enable user-control over certain aspects of the look, feel, and behavior of the space.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Design Space Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Distance to event features counters indicating how many periods (candles) have passed since the last occurrence of certain events, in the context of the episode.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Distance To Event Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "End balance is the balance at the datetime of the end property of the parent node or concept.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the End Balance Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "End rate is the close rate of the candle corresponding to the datetime of the end property.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the End Rate Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "End is the datetime on which the object represented by the parent node ceased to exist. In case the object has not been closed yet, it is the datetime at the moment of evaluation.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the End Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Entry target rate is the target rate set on the initial targets definition, in the open stage of the strategy.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Entry Target Rate Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Entry target size is the target size set on the initial targets definition, in the open stage of the strategy.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Entry Target Size Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The episode base asset node keeps track of the evolution of variables and metrics denominated in the base asset, throughout the episode.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Episode Base Asset Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The episode quoted asset node keeps track of the evolution of variables and metrics denominated in the quoted asset, throughout the episode.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Episode Quoted Asset Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Episode is the object that handles the information corresponding to the whole run of the trading bot—beginning to end—between the specified initial datetime and final datetime, in the time range parameter of the trading session.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Episode Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The exchange account asset represents a single asset the user has at the exchange.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exchange Account Asset Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The exchange data products node organizes data mines data by exchange. That is, each exchange installed in the system has an exchange data products node grouping all market data products nodes corresponding to the said exchange.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exchange Data Products Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The exchange data tasks node organizes data mining tasks by exchange. That is, each exchange installed in the system has an exchange data tasks node grouping all market data tasks corresponding to the said exchange.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exchange Data Tasks Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Exchange ID is a unique identifier the exchange assigns to the order, so that it may be unequivocally identified.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exchange Id Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Exchange orders is the section of the data structure that keeps track of orders of all types.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exchange Orders Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The exchange trading products node organizes trading mines data by exchange. That is, each exchange installed in the system has an exchange trading products node grouping all session references corresponding to the said exchange.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exchange Trading Products Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The exchange trading tasks node organizes trading tasks by exchange. That is, each exchange installed in the system has an exchange trading tasks node grouping all market trading tasks corresponding to the said exchange.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exchange Trading Tasks Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "An execution algorithm is a set of instructions used to place and manage orders at the exchange.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Execution Algorithm Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The execution finished event is the event that processes trigger once they have finished an execution cycle. The event is broadcasted to whoever wants to listen, so that other bots may know when the process has finished its execution cycle.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Execution Finished Event Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The execution started event is the event that triggers the execution of a process. It usually references the execution finished event of another process on which the process depends on.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Execution Started Event Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Exit target rate is the target rate set on the initial targets definition, in the close stage of the strategy.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exit Target Rate Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Exit target size is the target size set on the initial targets definition, in the close stage of the strategy.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exit Target Size Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Exit type refers to the reason why the object is closed.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Exit Type Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Fails counts the number of positions that closed with a negative profit loss, in the context of the parent node.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Fails Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The fee structure is a parameter fundamental to the calculation of fees, both in testing and live trading sessions.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Fee Structure Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Fees paid is the amount paid in fees.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Fees Paid Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A formula is a mathematical expression intended to determine a numerical value to be applied dynamically to a certain property.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Formula Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A forward testing session is a trading mode by which the trading bot instance performs live trading with a user-defined fraction of the available capital.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Forward Testing Session Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "During a trading session, the backend communicates with the frontend via heartbeats to inform the frontend about the status of the session. The parameter controls what information is made available to the user through the frontend.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Heartbeats Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Hit fail states whether a transaction is successful or not, hit meaning it is successful and fail meaning it is not.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Hit Fail Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Hit ratio is the percentage of positions that closed with a positive profit loss, in the context of the parent node.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Hit Ratio Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Hits counts the number of positions that closed with a positive profit loss, in the context of the parent node.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Hits Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Identifier is a unique alphanumeric string by which the object represented by the parent node may be unequivocally identified.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Identifier Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "An image condition is a rule that allows establishing when an image shall be rendered and when not.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Image Condition Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The image position node is a reference to a point defined in the chart points, and serves to determine the position in which the image shall be placed.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Image Position Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The image node allows overlaying an image over the charts, controlling its position, size, and when it shall be rendered.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Image Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Index is the position of the parent object in the corresponding data collection, as determined by the context.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Index Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "An indicator bot instance is a reference to an indicator bot as defined in a data mine. The instance of the bot runs the defined processes and generates the defined data products.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Indicator Bot Instance Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "An indicator bot is an algorithm that processes information that other bots have generated, and produces elaborate datasets for others to consume.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Indicator Bot Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "An indicator process instance is a reference to the process definition of an indicator bot, as defined in a data mine.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Indicator Process Instance Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The JavaScript code node may hold any snippet of valid JavaScript.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Javascript Code Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The key reference is a reference to an exchange account key as defined in a specific user account, in a specific exchange, on the Crypto Ecosystem hierarchy.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Key Reference Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The last object stores instances of position and strategy objects, in particular the instances that were last open at the time of evaluation, hence the adjective last.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Last Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The layer manager determines which layers will be visible on the corresponding timeline chart.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Layer Manager Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A layer represents a reference to a data product in the data storage node of the network hierarchy. Conceptually, it means that a certain data product, which exists in a certain location on the network, holds the data to be rendered on the charts.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Layer Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A limit buy order is an instruction sent to the exchange to buy the base asset, for execution at a specific rate or better.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Limit Buy Order Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Limit order is the section of the data structure that keeps track of the properties of a specific limit order, as defined in the trading system.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Limit Order Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A limit sell order is an instruction sent to the exchange to sell the base asset, for execution at a specific rate or better.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Limit Sell Order Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A live trading session is a trading mode by which the trading bot instance reads a live market data feed, applies the rules as defined in the associated trading system, places the corresponding orders at the associated exchange, and stores the defined data products.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Live Trading Session Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Lock is an internal mechanism that blocks the data structure of the order at the trading engine when the definition of the order at the trading system disallows spawning multiple orders.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Lock Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The manage stage deals with the setting and management of stop loss and take profit targets, both to protect your capital and to increase the efficiency of your trading system.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Manage Stage Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The managed stop loss node features the definition of the phases that make up the management of the stop loss target as the position develops.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Managed Stop Loss Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The managed take profit node features the definition of the phases that make up the management of the take profit target as the position develops.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Managed Take Profit Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The market base asset is the asset in the pair used to provide a quote—a price—for the quoted asset, as listed at the exchange.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Base Asset Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A market buy order is an instruction sent to the exchange to buy the base asset, for immediate execution at current market prices.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Buy Order Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A market data products node represents the group of data products generated in a specific market.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Data Products Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A market data tasks node groups data mining tasks operating in a specific market.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Data Tasks Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "Market order is the section of the data structure that keeps track of the properties of a specific market order, as defined in the trading system.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Order Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "The market quoted asset is the asset in the pair for which a quote is given, denominated in the base asset, as listed at the exchange.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Quoted Asset Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A market sell order is an instruction sent to the exchange to sell the base asset, for immediate execution at current market prices.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Sell Order Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A market trading products node features the group of data products generated by the referenced session in a specific market.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Trading Products Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A market trading tasks node groups trading tasks operating in a specific market.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Trading Tasks Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A market is the definition of a pair of assets (i.e.: BTC-USDT) listed as a market in the corresponding exchange.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Market Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Important",
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
"definition": "A master script contains the definitions of any number of template scripts along with the master JavaScript code providing the logic to implement them.",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How the Master Script Works"
|
||||
"style": "Block",
|
||||
"text": "Content"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
|
||||
Loaded 100 of 223 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user