Testing content aggregation
This commit is contained in:
1 parent
6693701271
commit
c839383d46
27 files changed
+965
-356
No files matched your search
@@ -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 four different types of hierarchies: Trading Systems, Data Mines, Network, and Crypto Ecosystem."
|
||||
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."
|
||||
|
||||
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,4 @@ 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"
|
||||
pending: "balanceAssetA, balanceAssetB, overfitting, supported assets, supported exchanges, supported markets"
|
||||
@@ -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 four different types of hierarchies: Trading Systems, Data Mines, Network, and Crypto Ecosystem."
|
||||
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."
|
||||
|
||||
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,4 @@ 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"
|
||||
pending: "balanceAssetA, balanceAssetB, overfitting, supported assets, supported exchanges, supported markets"
|
||||
@@ -117,8 +117,16 @@ entries:
|
||||
url: /suite-trading-system-overview.html
|
||||
output: web
|
||||
|
||||
- title: Working with strategies
|
||||
url: /suite-working-with-strategies.html
|
||||
- title: Strategies
|
||||
url: /suite-strategies.html
|
||||
output: web
|
||||
|
||||
- title: Trading Sessions
|
||||
url: /suite-trading-sessions.html
|
||||
output: web
|
||||
|
||||
- title: Parameters
|
||||
url: /suite-parameters.html
|
||||
output: web
|
||||
|
||||
- title: Conditions & Formulas
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
trading_system: "A trading system is a hierarchy that contains definitions regarding any number of trading strategies, all sharing the same market, the same base asset, and the same initial capital."
|
||||
trading_system: "A trading system is a framework handling the low-level logic that serves to structure the processes and methods used to implement and deploy trading strategies."
|
||||
|
||||
parameters: "Parameters are user definitions over several concepts. Parameters defined at the level of a session take precedence over parameters defined at the level of the trading system, which act as a fallback instance. The behavior of parameters may vary depending on the type of session."
|
||||
|
||||
@@ -44,7 +44,7 @@ initial_take_profit: "The initial take profit defines the initial target to take
|
||||
|
||||
position_size: "The size of the position is the amount of capital that will go in the trade, denominated in the quoted asset. The position size node allows setting a size for the position using a formula."
|
||||
|
||||
position_rate: "The position rate is the rate at which the position is taken, denominated in the quoted asset. The position rate node allows setting the desired position rate with a formula. However, the formula is overridden by the system as execution is currently limited to market orders until a more robust execution system is deployed. Therefore, the position rate is currently taken from the close value of the last candle."
|
||||
position_rate: "The position rate is the rate at which the position is taken, denominated in the quoted asset. The position rate node allows setting the desired position rate with a formula."
|
||||
|
||||
open_execution: "Open execution is the node that will eventually hold the information regarding the execution of the trade opening orders."
|
||||
|
||||
@@ -58,4 +58,6 @@ take_profit: "Take profit node in the manage stage groups all phases managing ta
|
||||
|
||||
close_stage: "Close stage is not developed yet. In the future, it will deal with the execution of the closing orders, trading log, and related matters."
|
||||
|
||||
close_execution: "Close execution is the node that will eventually hold the information regarding the execution of the closing orders."
|
||||
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."
|
||||
@@ -1,4 +1,4 @@
|
||||
trading_system: "A trading system is a hierarchy that contains definitions regarding any number of trading strategies, all sharing the same market, the same base asset, and the same initial capital."
|
||||
trading_system: "A trading system is a framework handling the low-level logic that serves to structure the processes and methods used to implement and deploy trading strategies."
|
||||
|
||||
parameters: "Parameters are user definitions over several concepts. Parameters defined at the level of a session take precedence over parameters defined at the level of the trading system, which act as a fallback instance. The behavior of parameters may vary depending on the type of session."
|
||||
|
||||
@@ -44,7 +44,7 @@ initial_take_profit: "The initial take profit defines the initial target to take
|
||||
|
||||
position_size: "The size of the position is the amount of capital that will go in the trade, denominated in the quoted asset. The position size node allows setting a size for the position using a formula."
|
||||
|
||||
position_rate: "The position rate is the rate at which the position is taken, denominated in the quoted asset. The position rate node allows setting the desired position rate with a formula. However, the formula is overridden by the system as execution is currently limited to market orders until a more robust execution system is deployed. Therefore, the position rate is currently taken from the close value of the last candle."
|
||||
position_rate: "The position rate is the rate at which the position is taken, denominated in the quoted asset. The position rate node allows setting the desired position rate with a formula."
|
||||
|
||||
open_execution: "Open execution is the node that will eventually hold the information regarding the execution of the trade opening orders."
|
||||
|
||||
@@ -58,4 +58,6 @@ take_profit: "Take profit node in the manage stage groups all phases managing ta
|
||||
|
||||
close_stage: "Close stage is not developed yet. In the future, it will deal with the execution of the closing orders, trading log, and related matters."
|
||||
|
||||
close_execution: "Close execution is the node that will eventually hold the information regarding the execution of the closing orders."
|
||||
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."
|
||||
Reference in new issue
Block a user