Live Trading working tested at Binance
This commit is contained in:
Luis Fernando Molina committed
1 parent
1ba29a7bad
commit
15b8a9044d
63 files changed
+1675
-1970
No files matched your search
@@ -0,0 +1,17 @@
|
||||
charting_space: "The Charting Space is the hierarchy that governs the configuration of the charts."
|
||||
|
||||
viewport: "A viewport represents the bidimensional space on which the charts are drawn."
|
||||
|
||||
time_machine: "A time machine synchronizes multiple timeline charts over the same timeline. Timeline charts within a time machine may have different rate scales or time frame scales, but their time scale will always match."
|
||||
|
||||
time_scale: "The time scale controls the scale of the horizontal axis, that is, the timeline of the corresponding time machine, and of all of the timeline charts within it."
|
||||
|
||||
rate_scale: "The rate scale controls the scale of the vertical axis, that is, the scale of the quoted asset, either of the time machine or of the timeline chart, depending on where the node is located."
|
||||
|
||||
time_frame_scale: "The time frame scale controls the time frame setting, that is, the period represented by each candle, either of the time machine or of the timeline chart, depending on where the node is located."
|
||||
|
||||
timeline_chart: "The timeline chart represents a chart within a time machine, which may have independent rate and time frame scales, as well as particular layers."
|
||||
|
||||
layers_manager: "The layer manager determines which layers will be visible on the corresponding timeline chart."
|
||||
|
||||
layer: "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."
|
||||
@@ -0,0 +1,17 @@
|
||||
charting_space: "The Charting Space is the hierarchy that governs the configuration of the charts."
|
||||
|
||||
viewport: "A viewport represents the bidimensional space on which the charts are drawn."
|
||||
|
||||
time_machine: "A time machine synchronizes multiple timeline charts over the same timeline. Timeline charts within a time machine may have different rate scales or time frame scales, but their time scale will always match."
|
||||
|
||||
time_scale: "The time scale controls the scale of the horizontal axis, that is, the timeline of the corresponding time machine, and of all of the timeline charts within it."
|
||||
|
||||
rate_scale: "The rate scale controls the scale of the vertical axis, that is, the scale of the quoted asset, either of the time machine or of the timeline chart, depending on where the node is located."
|
||||
|
||||
time_frame_scale: "The time frame scale controls the time frame setting, that is, the period represented by each candle, either of the time machine or of the timeline chart, depending on where the node is located."
|
||||
|
||||
timeline_chart: "The timeline chart represents a chart within a time machine, which may have independent rate and time frame scales, as well as particular layers."
|
||||
|
||||
layers_manager: "The layer manager determines which layers will be visible on the corresponding timeline chart."
|
||||
|
||||
layer: "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."
|
||||
@@ -10,7 +10,7 @@ parent-offspring_relationships: "Nodes in structures of nodes are chained to eac
|
||||
|
||||
chain: "Nodes in the workspace may be unchained or detached from its parent, carrying all offspring with it. When a node is left unchained, it is no longer taken into account in the logic of the hierarchy, as it no longer belongs to it. When a node is chained back or reattached to the hierarchy, it goes back to being functional."
|
||||
|
||||
hierarchy: "A hierarchy is the representation of an overarching, top-level concept resulting in a long chain of nodes, usually with many ramifications. Currently, the system manages five different types of hierarchies: Charting System, Crypto Ecosystem, Trading Systems, Network, and Data Mines."
|
||||
hierarchy: "A hierarchy is the representation of an overarching, top-level concept resulting in a long chain of nodes, usually with many ramifications. Currently, the system manages five different types of hierarchies: Charting Space, Crypto Ecosystem, Trading Systems, Network, and Data Mines."
|
||||
|
||||
reference: "A reference is a mechanism by which information in a node is related to, or accessed by, other nodes. The ability of a node to establish a reference with another node enables the first to access the information or features entailed in the second one."
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ parent-offspring_relationships: "Nodes in structures of nodes are chained to eac
|
||||
|
||||
chain: "Nodes in the workspace may be unchained or detached from its parent, carrying all offspring with it. When a node is left unchained, it is no longer taken into account in the logic of the hierarchy, as it no longer belongs to it. When a node is chained back or reattached to the hierarchy, it goes back to being functional."
|
||||
|
||||
hierarchy: "A hierarchy is the representation of an overarching, top-level concept resulting in a long chain of nodes, usually with many ramifications. Currently, the system manages five different types of hierarchies: Charting System, Crypto Ecosystem, Trading Systems, Network, and Data Mines."
|
||||
hierarchy: "A hierarchy is the representation of an overarching, top-level concept resulting in a long chain of nodes, usually with many ramifications. Currently, the system manages five different types of hierarchies: Charting Space, Crypto Ecosystem, Trading Systems, Network, and Data Mines."
|
||||
|
||||
reference: "A reference is a mechanism by which information in a node is related to, or accessed by, other nodes. The ability of a node to establish a reference with another node enables the first to access the information or features entailed in the second one."
|
||||
|
||||
|
||||
+15
-15
@@ -1,8 +1,8 @@
|
||||
data_mine: "A data mine is a hierarchy that contains definitions regarding bots, including the trading bot, sensors, indicators, and even plotters. These definitions make up the actual programs of such bots—the source code."
|
||||
|
||||
indicator_bot: "An indicator bot is an algorithm that processes information that other bots have generated, and produces elaborate datasets for others to consume. "
|
||||
indicator_bot: "An indicator bot is an algorithm that processes information that other bots have generated, and produces elaborate datasets for others to consume."
|
||||
|
||||
process_definition: "The process definition node groups all definitions required for a process to function. The Multi Period Market Process deals with time frames of one hour and above. The Multi Period Daily Process deals with time frames of 45 minutes and below."
|
||||
process_definition: "The process definition node groups all definitions required for a process to function. The Multi-Period-Market Process deals with time frames of one hour and above. The Multi-Period-Daily Process deals with time frames of 45 minutes and below."
|
||||
|
||||
process_output: "The process output groups the definitions of which datasets are impacted by the process, that is, which datasets the process builds or takes a part in building."
|
||||
|
||||
@@ -22,7 +22,7 @@ execution_finished_event: "The execution finished event is the event that proces
|
||||
|
||||
product_definition: "The product definition node holds all definitions that make up a product, including how the product is calculated and the datasets the product is comprised of."
|
||||
|
||||
dataset_definition: "A dataset definition contains a configuration file that defines all aspects of the dataset. There are two types of dataset definitions: multi period market and multi period daily."
|
||||
dataset_definition: "A dataset definition contains a configuration file that defines all aspects of the dataset. There are two types of dataset definitions: Multi-Period-Market and Multi-Period-Daily."
|
||||
|
||||
record_definition: "The record definition is where indicators define how many fields, what fields and in which order those fields will be stored in each record."
|
||||
|
||||
@@ -32,7 +32,7 @@ formula: "In the context of a record definition, formulas are used to assign a v
|
||||
|
||||
calculations_procedure: "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."
|
||||
|
||||
procedure_loop: "The procedure loop holds the JavaScript code that cycles through an input processing information to generate an output."
|
||||
procedure_loop: "The procedure loop holds the JavaScript code that reads an input, processes the information, and generates an output recursively."
|
||||
|
||||
javascript_code: "The JavaScript code node may hold any snippet of valid JavaScript."
|
||||
|
||||
@@ -40,34 +40,34 @@ procedure_initialization: "The procedure initialization is used to initialize va
|
||||
|
||||
data_building_procedure: "The data building procedure processes information to be fed to properties that are stored in the output dataset."
|
||||
|
||||
plotter: "A plotter is a device used to produce a graphic representation of the data generated by indicators."
|
||||
plotter: "A plotter is a device used to produce a graphic representation of datasets generated by bots."
|
||||
|
||||
plotter_module: "A plotter module is a device within a plotter that contains the definitions to create the visualization, often times, for a particular product definition."
|
||||
plotter_module: "A plotter module is a device within a plotter that contains the definitions to create the visualization for a product definition."
|
||||
|
||||
plotter_panel: "A plotter panel usually shows numerical representations of data over the charts on a small window or panel. The plotter panel node features definitions to make that possible."
|
||||
|
||||
panel_data: "A panel data node represents a data field to be plotted on the plotter panel."
|
||||
|
||||
data_formula: "A data formula is the device used to assign a value to the panel data, usually in the form of the name of the corresponding record property."
|
||||
data_formula: "A data formula is a device used to assign a value to the panel data, usually in the form of the name of the corresponding record property."
|
||||
|
||||
shapes: "The shapes node contains definitions that define polygons and styles to be rendered on a per period basis over the charts."
|
||||
shapes: "The shapes node contains definitions of polygons and styles to be rendered on a per-period basis over the charts."
|
||||
|
||||
chart_points: "The chart points node groups definitions of points."
|
||||
chart_points: "A chart points groups definitions of coordinate points used to define polygons."
|
||||
|
||||
point: "A point is a definition of an [x,y] coordinate where x is usually a datetime and y is usually a value that refers to a price, as output by the indicator."
|
||||
point: "A point is a definition of an [x,y] coordinate. The value [x] usually represents a datetime. The value [y] may refer to a price or some other concept."
|
||||
|
||||
point_formula: "A point formula is the node used to input the coordinates of a point."
|
||||
point_formula: "A point formula is a node used to input the [x,y] coordinates of a point."
|
||||
|
||||
polygon: "A polygon features definitions that make up shapes and their styles."
|
||||
polygon: "A polygon features definitions that makeup shapes and their styles."
|
||||
|
||||
polygon_vertex: "A polygon vertex is a reference to a point defined in the chart points, constituting a specific coordinate to be used as vertex of a shape."
|
||||
polygon_vertex: "A polygon vertex is a reference to a point defined in the chart points, constituting a specific coordinate to be used as a vertex of a shape."
|
||||
|
||||
polygon_border: "A polygon border is a shape defined by at least two vertices used to draw lines or to apply a style to the stroke of a closed shape."
|
||||
|
||||
style: "A style is a definition of color and opacity in case of a polygon body, and of color, opacity and line thickness in case of polygon borders."
|
||||
style: "A style is a definition of color and opacity in case of a polygon body, and color, opacity and line thickness in case of polygon borders."
|
||||
|
||||
style_condition: "A style condition is a rule that allows applying an alternative style in cases where the rule validates true."
|
||||
|
||||
polygon_body: "A polygon body is is the fill of a shape made out of at least 3 vertices."
|
||||
polygon_body: "A polygon body is the fill of a shape made out of at least three vertices."
|
||||
|
||||
pending: "daily files, market files and so on, Multi-Period-Daily, Multi-Period-Market"
|
||||
+15
-15
@@ -1,8 +1,8 @@
|
||||
data_mine: "A data mine is a hierarchy that contains definitions regarding bots, including the trading bot, sensors, indicators, and even plotters. These definitions make up the actual programs of such bots—the source code."
|
||||
|
||||
indicator_bot: "An indicator bot is an algorithm that processes information that other bots have generated, and produces elaborate datasets for others to consume. "
|
||||
indicator_bot: "An indicator bot is an algorithm that processes information that other bots have generated, and produces elaborate datasets for others to consume."
|
||||
|
||||
process_definition: "The process definition node groups all definitions required for a process to function. The Multi Period Market Process deals with time frames of one hour and above. The Multi Period Daily Process deals with time frames of 45 minutes and below."
|
||||
process_definition: "The process definition node groups all definitions required for a process to function. The Multi-Period-Market Process deals with time frames of one hour and above. The Multi-Period-Daily Process deals with time frames of 45 minutes and below."
|
||||
|
||||
process_output: "The process output groups the definitions of which datasets are impacted by the process, that is, which datasets the process builds or takes a part in building."
|
||||
|
||||
@@ -22,7 +22,7 @@ execution_finished_event: "The execution finished event is the event that proces
|
||||
|
||||
product_definition: "The product definition node holds all definitions that make up a product, including how the product is calculated and the datasets the product is comprised of."
|
||||
|
||||
dataset_definition: "A dataset definition contains a configuration file that defines all aspects of the dataset. There are two types of dataset definitions: multi period market and multi period daily."
|
||||
dataset_definition: "A dataset definition contains a configuration file that defines all aspects of the dataset. There are two types of dataset definitions: Multi-Period-Market and Multi-Period-Daily."
|
||||
|
||||
record_definition: "The record definition is where indicators define how many fields, what fields and in which order those fields will be stored in each record."
|
||||
|
||||
@@ -32,7 +32,7 @@ formula: "In the context of a record definition, formulas are used to assign a v
|
||||
|
||||
calculations_procedure: "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."
|
||||
|
||||
procedure_loop: "The procedure loop holds the JavaScript code that cycles through an input processing information to generate an output."
|
||||
procedure_loop: "The procedure loop holds the JavaScript code that reads an input, processes the information, and generates an output recursively."
|
||||
|
||||
javascript_code: "The JavaScript code node may hold any snippet of valid JavaScript."
|
||||
|
||||
@@ -40,34 +40,34 @@ procedure_initialization: "The procedure initialization is used to initialize va
|
||||
|
||||
data_building_procedure: "The data building procedure processes information to be fed to properties that are stored in the output dataset."
|
||||
|
||||
plotter: "A plotter is a device used to produce a graphic representation of the data generated by indicators."
|
||||
plotter: "A plotter is a device used to produce a graphic representation of datasets generated by bots."
|
||||
|
||||
plotter_module: "A plotter module is a device within a plotter that contains the definitions to create the visualization, often times, for a particular product definition."
|
||||
plotter_module: "A plotter module is a device within a plotter that contains the definitions to create the visualization for a product definition."
|
||||
|
||||
plotter_panel: "A plotter panel usually shows numerical representations of data over the charts on a small window or panel. The plotter panel node features definitions to make that possible."
|
||||
|
||||
panel_data: "A panel data node represents a data field to be plotted on the plotter panel."
|
||||
|
||||
data_formula: "A data formula is the device used to assign a value to the panel data, usually in the form of the name of the corresponding record property."
|
||||
data_formula: "A data formula is a device used to assign a value to the panel data, usually in the form of the name of the corresponding record property."
|
||||
|
||||
shapes: "The shapes node contains definitions that define polygons and styles to be rendered on a per period basis over the charts."
|
||||
shapes: "The shapes node contains definitions of polygons and styles to be rendered on a per-period basis over the charts."
|
||||
|
||||
chart_points: "The chart points node groups definitions of points."
|
||||
chart_points: "A chart points groups definitions of coordinate points used to define polygons."
|
||||
|
||||
point: "A point is a definition of an [x,y] coordinate where x is usually a datetime and y is usually a value that refers to a price, as output by the indicator."
|
||||
point: "A point is a definition of an [x,y] coordinate. The value [x] usually represents a datetime. The value [y] may refer to a price or some other concept."
|
||||
|
||||
point_formula: "A point formula is the node used to input the coordinates of a point."
|
||||
point_formula: "A point formula is a node used to input the [x,y] coordinates of a point."
|
||||
|
||||
polygon: "A polygon features definitions that make up shapes and their styles."
|
||||
polygon: "A polygon features definitions that makeup shapes and their styles."
|
||||
|
||||
polygon_vertex: "A polygon vertex is a reference to a point defined in the chart points, constituting a specific coordinate to be used as vertex of a shape."
|
||||
polygon_vertex: "A polygon vertex is a reference to a point defined in the chart points, constituting a specific coordinate to be used as a vertex of a shape."
|
||||
|
||||
polygon_border: "A polygon border is a shape defined by at least two vertices used to draw lines or to apply a style to the stroke of a closed shape."
|
||||
|
||||
style: "A style is a definition of color and opacity in case of a polygon body, and of color, opacity and line thickness in case of polygon borders."
|
||||
style: "A style is a definition of color and opacity in case of a polygon body, and color, opacity and line thickness in case of polygon borders."
|
||||
|
||||
style_condition: "A style condition is a rule that allows applying an alternative style in cases where the rule validates true."
|
||||
|
||||
polygon_body: "A polygon body is is the fill of a shape made out of at least 3 vertices."
|
||||
polygon_body: "A polygon body is the fill of a shape made out of at least three vertices."
|
||||
|
||||
pending: "daily files, market files and so on, Multi-Period-Daily, Multi-Period-Market"
|
||||
@@ -1,4 +1,4 @@
|
||||
network: "The network hierarchy contains definitions regarding the physical location in which certain nodes live or function. For instance, a certain process my run and store data in your local machine, or in some other machine in the network."
|
||||
network: "The network hierarchy contains definitions regarding the physical location in which certain nodes live or function. For instance, a certain process my run and store data in your local machine or some other machine in the network."
|
||||
|
||||
network_node: "A network node represents a machine in the network on which processes run or data is stored."
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
network: "The network hierarchy contains definitions regarding the physical location in which certain nodes live or function. For instance, a certain process my run and store data in your local machine, or in some other machine in the network."
|
||||
network: "The network hierarchy contains definitions regarding the physical location in which certain nodes live or function. For instance, a certain process my run and store data in your local machine or some other machine in the network."
|
||||
|
||||
network_node: "A network node represents a machine in the network on which processes run or data is stored."
|
||||
|
||||
|
||||
@@ -6,108 +6,108 @@ entries:
|
||||
version: 0.0.6
|
||||
folders:
|
||||
|
||||
- title:
|
||||
output: pdf
|
||||
type: frontmatter
|
||||
folderitems:
|
||||
- title:
|
||||
url: /titlepage.html
|
||||
output: pdf
|
||||
type: frontmatter
|
||||
- title:
|
||||
url: /tocpage.html
|
||||
output: pdf
|
||||
type: frontmatter
|
||||
# - title:
|
||||
# output: pdf
|
||||
# type: frontmatter
|
||||
# folderitems:
|
||||
# - title:
|
||||
# url: /titlepage.html
|
||||
# output: pdf
|
||||
# type: frontmatter
|
||||
# - title:
|
||||
# url: /tocpage.html
|
||||
# output: pdf
|
||||
# type: frontmatter
|
||||
|
||||
- title: Before you Begin
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Before you Begin
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Welcome!
|
||||
url: /index.html
|
||||
output: web
|
||||
type: homepage
|
||||
# - title: Welcome!
|
||||
# url: /index.html
|
||||
# output: web
|
||||
# type: homepage
|
||||
|
||||
- title: What to expect
|
||||
url: /suite-what-to-expect.html
|
||||
output: web
|
||||
# - title: What to expect
|
||||
# url: /suite-what-to-expect.html
|
||||
# output: web
|
||||
|
||||
- title: System requirements
|
||||
url: /suite-system-requirements.html
|
||||
output: web
|
||||
# - title: System requirements
|
||||
# url: /suite-system-requirements.html
|
||||
# output: web
|
||||
|
||||
- title: Getting Started
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Getting Started
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Download and set up
|
||||
url: /suite-download-and-set-up.html
|
||||
output: web
|
||||
# - title: Download and set up
|
||||
# url: /suite-download-and-set-up.html
|
||||
# output: web
|
||||
|
||||
- title: Run the suite
|
||||
url: /suite-run-the-suite.html
|
||||
output: web
|
||||
# - title: Run the suite
|
||||
# url: /suite-run-the-suite.html
|
||||
# output: web
|
||||
|
||||
- title: Quick overview
|
||||
url: /suite-quick-overview.html
|
||||
output: web
|
||||
# - title: Quick overview
|
||||
# url: /suite-quick-overview.html
|
||||
# output: web
|
||||
|
||||
- title: Run your first backtest
|
||||
url: /suite-run-your-first-backtest.html
|
||||
output: web
|
||||
# - title: Run your first backtest
|
||||
# url: /suite-run-your-first-backtest.html
|
||||
# output: web
|
||||
|
||||
- title: Update datasets
|
||||
url: /suite-update-datasets.html
|
||||
output: web
|
||||
# - title: Update datasets
|
||||
# url: /suite-update-datasets.html
|
||||
# output: web
|
||||
|
||||
- title: Trade with an open-source strategy
|
||||
url: /suite-trade-live-with-an-open-source-strategy.html
|
||||
output: web
|
||||
# - title: Trade with an open-source strategy
|
||||
# url: /suite-trade-live-with-an-open-source-strategy.html
|
||||
# output: web
|
||||
|
||||
- title: What's next?
|
||||
url: /suite-what-is-next.html
|
||||
output: web
|
||||
# - title: What's next?
|
||||
# url: /suite-what-is-next.html
|
||||
# output: web
|
||||
|
||||
|
||||
- title: Charts
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Charts
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Overview
|
||||
url: /suite-charts-overview.html
|
||||
output: web
|
||||
# - title: Overview
|
||||
# url: /suite-charts-overview.html
|
||||
# output: web
|
||||
|
||||
- title: Interface
|
||||
url: /suite-charts-interface.html
|
||||
output: web
|
||||
# - title: Interface
|
||||
# url: /suite-charts-interface.html
|
||||
# output: web
|
||||
|
||||
- title: Layers panel
|
||||
url: /suite-layers-panel.html
|
||||
output: web
|
||||
# - title: Layers panel
|
||||
# url: /suite-layers-panel.html
|
||||
# output: web
|
||||
|
||||
- title: Designer
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Designer
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Intro, workspace and data structures
|
||||
url: /suite-designer-workspace-and-data-structures.html
|
||||
output: web
|
||||
# - title: Intro, workspace and data structures
|
||||
# url: /suite-designer-workspace-and-data-structures.html
|
||||
# output: web
|
||||
|
||||
- title: Hierarchies
|
||||
url: /suite-hierarchies.html
|
||||
output: web
|
||||
# - title: Hierarchies
|
||||
# url: /suite-hierarchies.html
|
||||
# output: web
|
||||
|
||||
- title: Interface
|
||||
url: /suite-designer-interface.html
|
||||
output: web
|
||||
# - title: Interface
|
||||
# url: /suite-designer-interface.html
|
||||
# output: web
|
||||
|
||||
- title: Atachment and detachment of nodes
|
||||
url: /suite-detachment-and-attachment-of-nodes.html
|
||||
output: web
|
||||
# - title: Atachment and detachment of nodes
|
||||
# url: /suite-detachment-and-attachment-of-nodes.html
|
||||
# output: web
|
||||
|
||||
- title: References
|
||||
url: /suite-references.html
|
||||
output: web
|
||||
# - title: References
|
||||
# url: /suite-references.html
|
||||
# output: web
|
||||
|
||||
- title: Trading Concepts
|
||||
output: web
|
||||
@@ -129,149 +129,149 @@ entries:
|
||||
url: /suite-parameters.html
|
||||
output: web
|
||||
|
||||
- title: Conditions & Formulas
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Conditions & Formulas
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Syntax Overview
|
||||
url: /suite-sysntax-overview.html
|
||||
output: web
|
||||
# - title: Syntax Overview
|
||||
# url: /suite-sysntax-overview.html
|
||||
# output: web
|
||||
|
||||
- title: Internal variables
|
||||
url: /suite-internal-variables.html
|
||||
output: web
|
||||
# - title: Internal variables
|
||||
# url: /suite-internal-variables.html
|
||||
# output: web
|
||||
|
||||
- title: Indicators included in the data release
|
||||
url: /suite-indicators-included-in-the-data-release.html
|
||||
output: web
|
||||
# - title: Indicators included in the data release
|
||||
# url: /suite-indicators-included-in-the-data-release.html
|
||||
# output: web
|
||||
|
||||
- title: Indicators not included in the release
|
||||
url: /suite-indicators-not-included-in-the-data-release.html
|
||||
output: web
|
||||
# - title: Indicators not included in the release
|
||||
# url: /suite-indicators-not-included-in-the-data-release.html
|
||||
# output: web
|
||||
|
||||
- title: Using non-included indicators
|
||||
url: /suite-using-non-included-indicators.html
|
||||
output: web
|
||||
# - title: Using non-included indicators
|
||||
# url: /suite-using-non-included-indicators.html
|
||||
# output: web
|
||||
|
||||
- title: Network
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Network
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Overview
|
||||
url: /suite-network-overview.html
|
||||
output: web
|
||||
# - title: Overview
|
||||
# url: /suite-network-overview.html
|
||||
# output: web
|
||||
|
||||
- title: Managing processes
|
||||
url: /suite-managing-processes.html
|
||||
output: web
|
||||
# - title: Managing processes
|
||||
# url: /suite-managing-processes.html
|
||||
# output: web
|
||||
|
||||
- title: Backtests & Paper Trading
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Backtests & Paper Trading
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Overview
|
||||
url: /suite-testing-overview.html
|
||||
output: web
|
||||
# - title: Overview
|
||||
# url: /suite-testing-overview.html
|
||||
# output: web
|
||||
|
||||
- title: Session parameters
|
||||
url: /suite-session-parameters.html
|
||||
output: web
|
||||
# - title: Session parameters
|
||||
# url: /suite-session-parameters.html
|
||||
# output: web
|
||||
|
||||
- title: Simulation layers
|
||||
url: /suite-simulation-layers.html
|
||||
output: web
|
||||
# - title: Simulation layers
|
||||
# url: /suite-simulation-layers.html
|
||||
# output: web
|
||||
|
||||
- title: Advanced backtesting
|
||||
url: /suite-advanced-backtesting.html
|
||||
output: web
|
||||
# - title: Advanced backtesting
|
||||
# url: /suite-advanced-backtesting.html
|
||||
# output: web
|
||||
|
||||
- title: Forward Tests & Live Trading
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Forward Tests & Live Trading
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Overview
|
||||
url: /suite-live-trading-overview.html
|
||||
output: web
|
||||
# - title: Overview
|
||||
# url: /suite-live-trading-overview.html
|
||||
# output: web
|
||||
|
||||
- title: Getting ready to trade live
|
||||
url: /suite-getting-ready-to-trade-live.html
|
||||
output: web
|
||||
# - title: Getting ready to trade live
|
||||
# url: /suite-getting-ready-to-trade-live.html
|
||||
# output: web
|
||||
|
||||
- title: Live trading history layer
|
||||
url: /suite-live-trading-history-layer.html
|
||||
output: web
|
||||
# - title: Live trading history layer
|
||||
# url: /suite-live-trading-history-layer.html
|
||||
# output: web
|
||||
|
||||
- title: Execution limitations
|
||||
url: /suite-execution-limitations.html
|
||||
output: web
|
||||
# - title: Execution limitations
|
||||
# url: /suite-execution-limitations.html
|
||||
# output: web
|
||||
|
||||
- title: Multiple sessions
|
||||
url: /suite-multiple-forward-testing-and-live-trading-sessions.html
|
||||
output: web
|
||||
# - title: Multiple sessions
|
||||
# url: /suite-multiple-forward-testing-and-live-trading-sessions.html
|
||||
# output: web
|
||||
|
||||
- title: Data Mining & Research
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Data Mining & Research
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Data Mining Overview
|
||||
url: /suite-data-mining-overview.html
|
||||
output: web
|
||||
# - title: Data Mining Overview
|
||||
# url: /suite-data-mining-overview.html
|
||||
# output: web
|
||||
|
||||
- title: Bots
|
||||
url: /suite-bots.html
|
||||
output: web
|
||||
# - title: Bots
|
||||
# url: /suite-bots.html
|
||||
# output: web
|
||||
|
||||
- title: Anatomy of an indicator
|
||||
url: /suite-anatomy-of-an-indicator.html
|
||||
output: web
|
||||
# - title: Anatomy of an indicator
|
||||
# url: /suite-anatomy-of-an-indicator.html
|
||||
# output: web
|
||||
|
||||
- title: ":: Process definition"
|
||||
url: /suite-process-definition.html
|
||||
output: web
|
||||
# - title: ":: Process definition"
|
||||
# url: /suite-process-definition.html
|
||||
# output: web
|
||||
|
||||
- title: ":: Product definition"
|
||||
url: /suite-product-definition.html
|
||||
output: web
|
||||
# - title: ":: Product definition"
|
||||
# url: /suite-product-definition.html
|
||||
# output: web
|
||||
|
||||
- title: Input-to-output cycle
|
||||
url: /suite-input-to-output-cycle.html
|
||||
output: web
|
||||
# - title: Input-to-output cycle
|
||||
# url: /suite-input-to-output-cycle.html
|
||||
# output: web
|
||||
|
||||
- title: Datasets
|
||||
url: /suite-datasets.html
|
||||
output: web
|
||||
# - title: Datasets
|
||||
# url: /suite-datasets.html
|
||||
# output: web
|
||||
|
||||
- title: Dependencies
|
||||
url: /suite-dependencies.html
|
||||
output: web
|
||||
# - title: Dependencies
|
||||
# url: /suite-dependencies.html
|
||||
# output: web
|
||||
|
||||
- title: Build an indicator
|
||||
url: /suite-build-an-indicator.html
|
||||
output: web
|
||||
# - title: Build an indicator
|
||||
# url: /suite-build-an-indicator.html
|
||||
# output: web
|
||||
|
||||
- title: Build a plotter
|
||||
url: /suite-build-a-plotter.html
|
||||
output: web
|
||||
# - title: Build a plotter
|
||||
# url: /suite-build-a-plotter.html
|
||||
# output: web
|
||||
|
||||
- title: Productivity Tools
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Productivity Tools
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Backups
|
||||
url: /suite-backups.html
|
||||
output: web
|
||||
# - title: Backups
|
||||
# url: /suite-backups.html
|
||||
# output: web
|
||||
|
||||
- title: Clones
|
||||
url: /suite-clones.html
|
||||
output: web
|
||||
# - title: Clones
|
||||
# url: /suite-clones.html
|
||||
# output: web
|
||||
|
||||
- title: Shares
|
||||
url: /suite-shares.html
|
||||
output: web
|
||||
# - title: Shares
|
||||
# url: /suite-shares.html
|
||||
# output: web
|
||||
|
||||
- title: Telegram Announcements
|
||||
url: /suite-telegram-announcements.html
|
||||
output: web
|
||||
# - title: Telegram Announcements
|
||||
# url: /suite-telegram-announcements.html
|
||||
# output: web
|
||||
|
||||
- title: Hierarchies Directory
|
||||
output: web
|
||||
@@ -281,8 +281,8 @@ entries:
|
||||
url: /suite-crypto-ecosystem-hierarchy.html
|
||||
output: web
|
||||
|
||||
- title: Charting system
|
||||
url: /suite-charting-system-hierarchy.html
|
||||
- title: Charting Space
|
||||
url: /suite-charting-space-hierarchy.html
|
||||
output: web
|
||||
|
||||
- title: Trading system
|
||||
@@ -297,33 +297,33 @@ entries:
|
||||
url: /suite-data-mine-hierarchy.html
|
||||
output: web
|
||||
|
||||
- title: Troubleshooting
|
||||
output: web
|
||||
folderitems:
|
||||
# - title: Troubleshooting
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
- title: Upgrading your existing installation
|
||||
url: /suite-upgrading-your-existing-instalation.html
|
||||
output: web
|
||||
# - title: Upgrading your existing installation
|
||||
# url: /suite-upgrading-your-existing-instalation.html
|
||||
# output: web
|
||||
|
||||
- title: My system gets slow
|
||||
url: /suite-my-system-gets-slow.html
|
||||
output: web
|
||||
# - title: My system gets slow
|
||||
# url: /suite-my-system-gets-slow.html
|
||||
# output: web
|
||||
|
||||
- title: On-screen errors and warnings
|
||||
url: /suite-on-screen-errors-and-warnings.html
|
||||
output: web
|
||||
# - title: On-screen errors and warnings
|
||||
# url: /suite-on-screen-errors-and-warnings.html
|
||||
# output: web
|
||||
|
||||
- title: Market data seems to be outdated
|
||||
url: /suite-market-data-indicators-seem-to-be-outdated.html
|
||||
output: web
|
||||
# - title: Market data seems to be outdated
|
||||
# url: /suite-market-data-indicators-seem-to-be-outdated.html
|
||||
# output: web
|
||||
|
||||
- title: Reporting bugs
|
||||
url: /suite-reporting-bugs.html
|
||||
output: web
|
||||
# - title: Reporting bugs
|
||||
# url: /suite-reporting-bugs.html
|
||||
# output: web
|
||||
|
||||
- title: Consulting logs
|
||||
url: /suite-consulting-logs.html
|
||||
output: web
|
||||
# - title: Consulting logs
|
||||
# url: /suite-consulting-logs.html
|
||||
# output: web
|
||||
|
||||
|
||||
|
||||
|
||||
+21
-21
@@ -11,24 +11,24 @@ topnav:
|
||||
url: index.html
|
||||
|
||||
#Topnav dropdowns
|
||||
topnav_dropdowns:
|
||||
- title: Topnav dropdowns
|
||||
folders:
|
||||
- title: Product Docs
|
||||
folderitems:
|
||||
- title: Systematic Trading
|
||||
url: /systematic-trading-system-overview.html
|
||||
- title: Algorithmic Trading
|
||||
url: /algorithmic-trading-system-overview.html
|
||||
- title: Discretionary Trading
|
||||
url: /discretionary-introduction.html
|
||||
- title: Smart Holding
|
||||
url: /smart-introduction.html
|
||||
- title: Trading Coach
|
||||
url: /coach-introduction_page.html
|
||||
- title: Signals Broadcast
|
||||
url: /signal-introduction.html
|
||||
- title: Markets Research
|
||||
url: /market-introduction_page.html
|
||||
- title: Data Mining
|
||||
url: /mine-introduction.html
|
||||
#topnav_dropdowns:
|
||||
#- title: Topnav dropdowns
|
||||
# folders:
|
||||
# - title: Product Docs
|
||||
# folderitems:
|
||||
# - title: Systematic Trading
|
||||
# url: /systematic-trading-system-overview.html
|
||||
# - title: Algorithmic Trading
|
||||
# url: /algorithmic-trading-system-overview.html
|
||||
# - title: Discretionary Trading
|
||||
# url: /discretionary-introduction.html
|
||||
# - title: Smart Holding
|
||||
# url: /smart-introduction.html
|
||||
# - title: Trading Coach
|
||||
# url: /coach-introduction_page.html
|
||||
# - title: Signals Broadcast
|
||||
# url: /signal-introduction.html
|
||||
# - title: Markets Research
|
||||
# url: /market-introduction_page.html
|
||||
# - title: Data Mining
|
||||
# url: /mine-introduction.html
|
||||
Reference in new issue
Block a user