Scales Improvements
This commit is contained in:
1 parent
1a8a0c27ad
commit
31ff6e38e8
213 files changed
+5371
-2884
No files matched your search
+11
-8
@@ -1,16 +1,16 @@
|
||||
designer: "The designer is the portion of the system the controls all the information available and that enables to user to exert control over the whole system."
|
||||
design_space: "The design space is the visual environment that features all the information available and that enables users to exert control over the whole system. You may think of the design space as your desktop."
|
||||
|
||||
workspace: "The workspace refers to the visual environment that contains all information managed by the system. You may think of the workspace as your desktop."
|
||||
workspace: "The workspace refers to the body of information managed by the system. Every data structure in the form of strategies, the configuration of different parts of the system, operational settings, and the relationships among them live within the workspace."
|
||||
|
||||
node: "A node is a small data structure containing information which may be related to markets information, trading intelligence, the operation of the system or other concepts. They are visually represented by icons on the workspace."
|
||||
node: "A node is a small data structure containing information which may be related to market information, trading intelligence, the operation of the system or other concepts. They are visually represented by icons on the workspace."
|
||||
|
||||
structure_of_nodes: "Nodes may be linked together forming structures of nodes. In every structure of nodes, there is a parent node with offprings. That is, a structure of nodes is a data structure composed of any node and its offspring."
|
||||
structure_of_nodes: "Nodes may be chained together forming structures of nodes. In every structure of nodes, there is a parent node with offsprings. That is, a structure of nodes is a data structure composed of any node and its offspring."
|
||||
|
||||
parent-offspring_relationships: "Nodes in structures of nodes are chained to each other by so-called parent-offspring relationships, which are visually represented by orange dotted lines, which may turn yellow or blue depending on certain visualization properties that the user may control. When nodes are chained together they form structures of nodes."
|
||||
parent-offspring_relationships: "Nodes in structures of nodes are chained to each other by so-called parent-offspring relationships. These relationships are visually represented by orange dotted lines, which may turn yellow or blue depending on certain visualization properties that the user may control. When nodes are chained together they form structures of nodes."
|
||||
|
||||
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 Space, 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: the crypto ecosystem, the charting space, trading systems, the 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."
|
||||
|
||||
@@ -22,6 +22,9 @@ indicator_bot: "An indicator bot processes data to produce more elaborate datase
|
||||
|
||||
trading_bot: "Based on datasets exposed as products by other bots (counting sensors, indicators and even other trading bots), a trading bot applies the trading logic defined on a trading system to, on one side, generate a complete trading simulation (outputting datasets that include trades, the action of strategies, validation of conditions, etc.), and on the other side, manage the execution of orders when on a forward testing or live trading session."
|
||||
|
||||
superalgos_protocol: "In conceptual terms, the Superalgos Protocol determines the structure in which the information decribing a trading system is stored and provides guidance on how traders shall create and automate strategies. In practical terms, the protocol results in a file with a specific format capable of holding all the information concerning any number and variety of strategies. In its current early version, the protocol is the description of a JSON object which defines the desired automation."
|
||||
superalgos_protocol: "In conceptual terms, the Superalgos Protocol determines the structure in which the information describing a trading system is stored and guides how traders shall create and automate strategies. In practical terms, the protocol results in a file with a specific format capable of holding all the information concerning any number and variety of strategies. In its current early version, the protocol is the description of a JSON object which defines the desired automation."
|
||||
|
||||
hierarchies_directory: "The hierarchies directory is the part of the documentation that features a description of the complete catalog of nodes of each hierachy"
|
||||
|
||||
pending: "balanceAssetA, balanceAssetB, overfitting, supported assets, supported exchanges, supported markets"
|
||||
|
||||
pending: "balanceAssetA, balanceAssetB, overfitting, supported assets, supported exchanges, supported markets"
|
||||
+12
-7
@@ -1,16 +1,16 @@
|
||||
designer: "The designer is the portion of the system the controls all the information available and that enables to user to exert control over the whole system."
|
||||
design_space: "The design space is the visual environment that features all the information available and that enables users to exert control over the whole system. You may think of the design space as your desktop."
|
||||
|
||||
workspace: "The workspace refers to the visual environment that contains all information managed by the system. You may think of the workspace as your desktop."
|
||||
workspace: "The workspace refers to the body of information managed by the system. Every data structure in the form of strategies, the configuration of different parts of the system, operational settings, and the relationships among them live within the workspace."
|
||||
|
||||
node: "A node is a small data structure containing information which may be related to markets information, trading intelligence, the operation of the system or other concepts. They are visually represented by icons on the workspace."
|
||||
node: "A node is a small data structure containing information which may be related to market information, trading intelligence, the operation of the system or other concepts. They are visually represented by icons on the workspace."
|
||||
|
||||
structure_of_nodes: "Nodes may be linked together forming structures of nodes. In every structure of nodes, there is a parent node with offprings. That is, a structure of nodes is a data structure composed of any node and its offspring."
|
||||
structure_of_nodes: "Nodes may be chained together forming structures of nodes. In every structure of nodes, there is a parent node with offsprings. That is, a structure of nodes is a data structure composed of any node and its offspring."
|
||||
|
||||
parent-offspring_relationships: "Nodes in structures of nodes are chained to each other by so-called parent-offspring relationships, which are visually represented by orange dotted lines, which may turn yellow or blue depending on certain visualization properties that the user may control. When nodes are chained together they form structures of nodes."
|
||||
parent-offspring_relationships: "Nodes in structures of nodes are chained to each other by so-called parent-offspring relationships. These relationships are visually represented by orange dotted lines, which may turn yellow or blue depending on certain visualization properties that the user may control. When nodes are chained together they form structures of nodes."
|
||||
|
||||
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 Space, 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: the crypto ecosystem, the charting space, trading systems, the 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."
|
||||
|
||||
@@ -22,4 +22,9 @@ indicator_bot: "An indicator bot processes data to produce more elaborate datase
|
||||
|
||||
trading_bot: "Based on datasets exposed as products by other bots (counting sensors, indicators and even other trading bots), a trading bot applies the trading logic defined on a trading system to, on one side, generate a complete trading simulation (outputting datasets that include trades, the action of strategies, validation of conditions, etc.), and on the other side, manage the execution of orders when on a forward testing or live trading session."
|
||||
|
||||
pending: "balanceAssetA, balanceAssetB, overfitting, supported assets, supported exchanges, supported markets"
|
||||
superalgos_protocol: "In conceptual terms, the Superalgos Protocol determines the structure in which the information describing a trading system is stored and guides how traders shall create and automate strategies. In practical terms, the protocol results in a file with a specific format capable of holding all the information concerning any number and variety of strategies. In its current early version, the protocol is the description of a JSON object which defines the desired automation."
|
||||
|
||||
hierarchies_directory: "The hierarchies directory is the part of the documentation that features a description of the complete catalog of nodes of each hierachy"
|
||||
|
||||
pending: "balanceAssetA, balanceAssetB, overfitting, supported assets, supported exchanges, supported markets"
|
||||
|
||||
@@ -8,5 +8,5 @@ football: "No doubt the most fun sport to watch, football also manages to accrue
|
||||
|
||||
soccer: "If there's one sport that dominates the world landscape, it's soccer. However, US soccer fans are few and far between. Apart from the popularity of soccer during the World Cup, most people don't even know the name of the professional soccer organization in their area."
|
||||
|
||||
workspace: "The workspace is a concept that refers to the visual environment that contains all hierarchies with all of their nodes, nodes that may be floating around detached from hierarchies, and the information regarding the physical position and status of all nodes within the Designer, even those detached from the hierarchies. You may think of the workspace as your desktop. It is not part of any of the hierarchies; instead, it contains them."
|
||||
workspace: "The workspace is a concept that refers to the visual environment that contains all hierarchies with all of their nodes, nodes that may be floating around detached from hierarchies, and the information regarding the physical position and status of all nodes within the design space, even those detached from the hierarchies. You may think of the workspace as your desktop. It is not part of any of the hierarchies; instead, it contains them."
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
entries:
|
||||
- title: sidebar
|
||||
product: Superalgos Suite
|
||||
product: Superalgos
|
||||
version: 0.0.6
|
||||
folders:
|
||||
|
||||
@@ -85,43 +85,43 @@ entries:
|
||||
# url: /suite-layers-panel.html
|
||||
# output: web
|
||||
|
||||
# - title: Designer
|
||||
# output: web
|
||||
# folderitems:
|
||||
|
||||
# - 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: 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: References
|
||||
# url: /suite-references.html
|
||||
# output: web
|
||||
|
||||
- title: Trading Concepts
|
||||
- title: Design space
|
||||
output: web
|
||||
folderitems:
|
||||
|
||||
- title: Defining a Trading System
|
||||
url: /suite-defining-a-trading-system.html
|
||||
- title: Design space, workspace, and nodes
|
||||
url: /suite-design-space-workspace-and-data-structures.html
|
||||
output: web
|
||||
|
||||
- title: Defining a Strategy
|
||||
url: /suite-defining-a-trading-strategy.html
|
||||
- title: Hierarchies
|
||||
url: /suite-hierarchies.html
|
||||
output: web
|
||||
|
||||
- title: Trading Sessions
|
||||
- title: References
|
||||
url: /suite-references.html
|
||||
output: web
|
||||
|
||||
- title: Interface
|
||||
url: /suite-design-space-interface.html
|
||||
output: web
|
||||
|
||||
- title: Trading concepts
|
||||
output: web
|
||||
folderitems:
|
||||
|
||||
- title: Trading systems
|
||||
url: /suite-trading-systems.html
|
||||
output: web
|
||||
|
||||
- title: Strategies
|
||||
url: /suite-strategies.html
|
||||
output: web
|
||||
|
||||
- title: Situations, conditions and formulas
|
||||
url: /suite-situations-conditions-formulas.html
|
||||
output: web
|
||||
|
||||
- title: Trading sessions
|
||||
url: /suite-trading-sessions.html
|
||||
output: web
|
||||
|
||||
@@ -129,25 +129,25 @@ entries:
|
||||
url: /suite-parameters.html
|
||||
output: web
|
||||
|
||||
# - title: Conditions & Formulas
|
||||
# output: web
|
||||
# folderitems:
|
||||
- title: Writing 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: Masters indicators
|
||||
url: /suite-masters-indicators.html
|
||||
output: web
|
||||
|
||||
# - title: Indicators not included in the release
|
||||
# url: /suite-indicators-not-included-in-the-data-release.html
|
||||
# output: web
|
||||
- title: Sparta indicators
|
||||
url: /suite-sparta-indicators.html
|
||||
output: web
|
||||
|
||||
# - title: Using non-included indicators
|
||||
# url: /suite-using-non-included-indicators.html
|
||||
@@ -273,7 +273,7 @@ entries:
|
||||
# url: /suite-telegram-announcements.html
|
||||
# output: web
|
||||
|
||||
- title: Hierarchies Directory
|
||||
- title: Hierarchies directory
|
||||
output: web
|
||||
folderitems:
|
||||
|
||||
|
||||
@@ -61,3 +61,5 @@ close_stage: "Close stage is not developed yet. In the future, it will deal with
|
||||
close_execution: "Close execution is the node that will eventually hold the information regarding the execution of the closing orders."
|
||||
|
||||
event: "An event is an action triggered by predefined market situations."
|
||||
|
||||
javascript_code: "The JavaScript code node may hold any snippet of valid JavaScript."
|
||||
@@ -61,3 +61,5 @@ close_stage: "Close stage is not developed yet. In the future, it will deal with
|
||||
close_execution: "Close execution is the node that will eventually hold the information regarding the execution of the closing orders."
|
||||
|
||||
event: "An event is an action triggered by predefined market situations."
|
||||
|
||||
javascript_code: "The JavaScript code node may hold any snippet of valid JavaScript."
|
||||
Reference in new issue
Block a user