diff --git a/docs/_data/trading_system.md b/docs/_data/trading_system.md index b03064d0e..68a68d175 100644 --- a/docs/_data/trading_system.md +++ b/docs/_data/trading_system.md @@ -1,14 +1,14 @@ 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." -parameters: "Parameters are user definitions over several concepts. When defined at the level of a session, parameters take precedence over those 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." +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." base_asset: "In the context of a trading system or a session, the base asset is the asset in the pair on which capital stands when out of a trade." -quoted_asset: "In the context of a trading system or a session, the quoted asset is the asset in the pair for wich capital is traded." +quoted_asset: "In the context of a trading system or a session, the quoted asset is the asset in the pair for which capital is traded." time_frame: "The time frame is the frequency on which the session runs, meaning that the associated process instance runs once per unit of the time frame." -time_range: "The time range is the specific period of time between a starting and an ending date on which the session runs." +time_range: "The time range is the specific period between a starting and an ending date on which the session runs." slippage: "The slippage is an assumption on the difference between the simulated rate and the actual fill rate of an order, most relevant in the context of backtesting and paper-trading sessions. The parameter is a tool to make simulations more realistic." @@ -16,9 +16,9 @@ fee_structure: "The fee structure is a parameter enabling users to enter assumpt strategy: "A strategy is a set of actions occurring in stages, designed to achieve a specific goal within a broader plan, via executing trades." -trigger_stage: "The trigger stage deals with monitoring the market in search for trading oportunities with the corresponding strategy." +trigger_stage: "The trigger stage deals with monitoring the market in search of trading opportunities with the corresponding strategy." -trigger-on_event: "The trigger-on event defines the set of rules that need to be met in order for the corresponding strategy to be triggered on. A strategy that is triggered on may use all the capital available to the trading system, preventing other strategies in the system from triggering." +trigger-on_event: "The trigger-on event defines the set of rules that need to be met for the corresponding strategy to be triggered on. A strategy that is triggered may use all the capital available to the trading system, preventing other strategies in the system from triggering." situation: "A situation refers to a specific state of the market in which a certain event should take place, as defined by any number of conditions." @@ -26,13 +26,13 @@ condition: "Conditions are rules within a situation. When all conditions under a trigger-off_event: "The trigger-off event defines the situation in which the corresponding strategy shall be triggered-off. A strategy that is triggered-off releases the capital in reserve and makes it available to other strategies in the trading system." -take_position_event: "The take position event defines the situation that needs to be met in order to enter a trade." +take_position_event: "The take position event defines the situation that needs to be met to enter a trade." open_stage: "The open stage deals with all the parameters that define a trade, including position rate and size as well as initial stop and take profit targets." initial_definition: "The initial definition node groups the parameters that define the trade at the moment the position is taken." -initial_stop: "The initial stop defines the initial target to stop a loss, before the trade gets to be managed." +initial_stop: "The initial stop defines the initial target to stop a loss before the trade gets to be managed." phase_0: "Phase 0 represents the starting point for a stop or take profit target, which may be managed in subsequent phases, on the manage stage." @@ -40,22 +40,22 @@ formula: "A formula is a mathematical expression intended to determine a numeric next_phase_event: "The next-phase event describes a market situation upon which the management of the trade should shift from one phase to the next." -initial_take_profit: "The initial take profit defines the initial target to take profit, before the trade gets to be managed." +initial_take_profit: "The initial take profit defines the initial target to take profit before the trade gets to be managed." 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 overriden 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. 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." open_execution: "Open execution is the node that will eventually hold the information regarding the execution of the trade opening orders." -manage_stage: "The manage stage is the third stage in the definition of a strategy and deals with the management of stop and take profit targets." +manage_stage: "The manage stage is the third stage in the definition of a strategy and deals with the management of stop and take-profit targets." -stop: "Stop sets a new stop loss target associated with the corresponding phase." +stop: "The stop node in the manage stage groups all phases managing stop loss targets as the trade develops." -phase_1: "Phase 1 is the first phase in the management of a stop or take profit target. The management of targets may have as many phases as required." +phase_1: "Phase 1 is the first phase in the management of a stop or take-profit target. The management of targets may have as many phases as required." -take_profit: "Take profit sets a new take profit target associated with the corresponding phase." +take_profit: "Take profit node in the manage stage groups all phases managing take profit targets as the trade develops." 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 trade closing orders." \ No newline at end of file +close_execution: "Close execution is the node that will eventually hold the information regarding the execution of the closing orders." \ No newline at end of file diff --git a/docs/_data/trading_system.yml b/docs/_data/trading_system.yml index b03064d0e..68a68d175 100644 --- a/docs/_data/trading_system.yml +++ b/docs/_data/trading_system.yml @@ -1,14 +1,14 @@ 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." -parameters: "Parameters are user definitions over several concepts. When defined at the level of a session, parameters take precedence over those 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." +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." base_asset: "In the context of a trading system or a session, the base asset is the asset in the pair on which capital stands when out of a trade." -quoted_asset: "In the context of a trading system or a session, the quoted asset is the asset in the pair for wich capital is traded." +quoted_asset: "In the context of a trading system or a session, the quoted asset is the asset in the pair for which capital is traded." time_frame: "The time frame is the frequency on which the session runs, meaning that the associated process instance runs once per unit of the time frame." -time_range: "The time range is the specific period of time between a starting and an ending date on which the session runs." +time_range: "The time range is the specific period between a starting and an ending date on which the session runs." slippage: "The slippage is an assumption on the difference between the simulated rate and the actual fill rate of an order, most relevant in the context of backtesting and paper-trading sessions. The parameter is a tool to make simulations more realistic." @@ -16,9 +16,9 @@ fee_structure: "The fee structure is a parameter enabling users to enter assumpt strategy: "A strategy is a set of actions occurring in stages, designed to achieve a specific goal within a broader plan, via executing trades." -trigger_stage: "The trigger stage deals with monitoring the market in search for trading oportunities with the corresponding strategy." +trigger_stage: "The trigger stage deals with monitoring the market in search of trading opportunities with the corresponding strategy." -trigger-on_event: "The trigger-on event defines the set of rules that need to be met in order for the corresponding strategy to be triggered on. A strategy that is triggered on may use all the capital available to the trading system, preventing other strategies in the system from triggering." +trigger-on_event: "The trigger-on event defines the set of rules that need to be met for the corresponding strategy to be triggered on. A strategy that is triggered may use all the capital available to the trading system, preventing other strategies in the system from triggering." situation: "A situation refers to a specific state of the market in which a certain event should take place, as defined by any number of conditions." @@ -26,13 +26,13 @@ condition: "Conditions are rules within a situation. When all conditions under a trigger-off_event: "The trigger-off event defines the situation in which the corresponding strategy shall be triggered-off. A strategy that is triggered-off releases the capital in reserve and makes it available to other strategies in the trading system." -take_position_event: "The take position event defines the situation that needs to be met in order to enter a trade." +take_position_event: "The take position event defines the situation that needs to be met to enter a trade." open_stage: "The open stage deals with all the parameters that define a trade, including position rate and size as well as initial stop and take profit targets." initial_definition: "The initial definition node groups the parameters that define the trade at the moment the position is taken." -initial_stop: "The initial stop defines the initial target to stop a loss, before the trade gets to be managed." +initial_stop: "The initial stop defines the initial target to stop a loss before the trade gets to be managed." phase_0: "Phase 0 represents the starting point for a stop or take profit target, which may be managed in subsequent phases, on the manage stage." @@ -40,22 +40,22 @@ formula: "A formula is a mathematical expression intended to determine a numeric next_phase_event: "The next-phase event describes a market situation upon which the management of the trade should shift from one phase to the next." -initial_take_profit: "The initial take profit defines the initial target to take profit, before the trade gets to be managed." +initial_take_profit: "The initial take profit defines the initial target to take profit before the trade gets to be managed." 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 overriden 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. 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." open_execution: "Open execution is the node that will eventually hold the information regarding the execution of the trade opening orders." -manage_stage: "The manage stage is the third stage in the definition of a strategy and deals with the management of stop and take profit targets." +manage_stage: "The manage stage is the third stage in the definition of a strategy and deals with the management of stop and take-profit targets." -stop: "Stop sets a new stop loss target associated with the corresponding phase." +stop: "The stop node in the manage stage groups all phases managing stop loss targets as the trade develops." -phase_1: "Phase 1 is the first phase in the management of a stop or take profit target. The management of targets may have as many phases as required." +phase_1: "Phase 1 is the first phase in the management of a stop or take-profit target. The management of targets may have as many phases as required." -take_profit: "Take profit sets a new take profit target associated with the corresponding phase." +take_profit: "Take profit node in the manage stage groups all phases managing take profit targets as the trade develops." 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 trade closing orders." \ No newline at end of file +close_execution: "Close execution is the node that will eventually hold the information regarding the execution of the closing orders." \ No newline at end of file diff --git a/docs/_includes/trading_system/base-asset.md b/docs/_includes/trading_system/base-asset.md new file mode 100644 index 000000000..e28bcebb9 --- /dev/null +++ b/docs/_includes/trading_system/base-asset.md @@ -0,0 +1,64 @@ + + +{% assign title = "Base Asset" %} +{% assign definition = site.data.trading_system.base_asset %} +{% assign preposition = "a" %} + + + +{% if include.heading != "" %} +{{include.heading}} {{title}} +{% endif %} + +{% if include.icon != "no" %} + +{% endif %} + +**{{ definition }}** + + + +The basse asset must reference an asset in a specific market of a specific exchange in the Crypto Ecosystem hierarchy. + + + +{% if include.adding != "" %} + +{{include.adding}} Adding {{preposition}} {{title}} + + + +To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. + +{% include note.html content="After adding a base asset node, make sure you establish a reference to the asset in a specific market of a specific exchange in the Crypto Ecosystem hierarchy." %} + + + +{% endif %} + +{% if include.configuring != "" %} + +{{include.configuring}} Configuring the {{title}} + + + +Select *Configure Base Asset* on the menu to access the configuration. + +```json +{ +"initialBalance": 0.001, +"minimumBalance": 0.0001, +"maximumBalance": 0.1 +} +``` + +* ```initialBalance``` is the amount of capital you wish to allocate to the trading system. + +* ```minimumBalance``` is the threshold of accummulated losses that switches off the session; when your overall balance (balanceAssetA + balanceAssetB) drops to this value, all trading stops; think of the ```minimumBalance``` as a general safety switch. + +* ```maximumBalance``` is a similar concept as with the ```minimumBalance``` but on the high side of the ```initialBalance```. + + + + +{% endif %} \ No newline at end of file diff --git a/docs/_includes/trading_system/fee-structure.md b/docs/_includes/trading_system/fee-structure.md new file mode 100644 index 000000000..63723248c --- /dev/null +++ b/docs/_includes/trading_system/fee-structure.md @@ -0,0 +1,74 @@ + + +{% assign title = "Fee Structure" %} +{% assign definition = site.data.trading_system.free_structure %} +{% assign preposition = "a" %} + + + +{% if include.heading != "" %} +{{include.heading}} {{title}} +{% endif %} + +{% if include.icon != "no" %} + +{% endif %} + +**{{ definition }}** + + + +Exchange fees are a crucial part of trading. A strategy may work like a charm when you leave fees out of the equation but would lead you to bankruptcy in a live trading situation. + +Fee structures are factored both in the session reports and in the graphic representation of each trade provided by the simulation trades product of the trading bot. + +To illustrate how fees affect your bottom line, take a look at the image below. + +[![Trading-Simulation-Fees-Fails](https://user-images.githubusercontent.com/13994516/63636432-8d8cdf80-c66f-11e9-86a3-480d157d8126.gif)](https://user-images.githubusercontent.com/13994516/63636432-8d8cdf80-c66f-11e9-86a3-480d157d8126.gif) + +The trade hits the take profit target above the Position Rate level, however, due to fees, the trade has a negative 0.32% ROI. + +In the context of forward testing and live trading sessions, the fee structure assumptions do not affect actual transactions. However, the parameter is taken into account when creating simulation layers, which are also available during forward testing and live trading. + + + +{% if include.adding != "" %} + +{{include.adding}} Adding {{preposition}} {{title}} + + + +To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. + + + +{% endif %} + +{% if include.configuring != "" %} + +{{include.configuring}} Configuring the {{title}} + + + +Select *Configure Fee Structure* on the menu to access the configuration. + +```json +{ +"maker": 0.15, +"taker": 0.25 +} +``` + +* ```maker``` is the setting for the fee the exchange charges when an order adds liquidity to the market, such as with limit orders. + +* ```taker``` is the setting for the fee the exchange charges when an order takes liquidity from the market, such as with market or instant orders. + +{% include note.html content="Check the fees structure in your exchange, carefully looking into the tier you fall in to feed accurate assumptions to your backtesting and paper trading sessions." %} + +{% include note.html content="If the fee structure parameter is left empty or detached both from your session and your trading system, fees are not computed during simulations." %} + +{% include important.html content="Remember that, for the time being, and until the new execution engine is released, all orders placed by the trading bot are *market orders*, thus, the *taker* fee applies in all cases." %} + + + +{% endif %} \ No newline at end of file diff --git a/docs/_includes/trading_system/parameters.md b/docs/_includes/trading_system/parameters.md new file mode 100644 index 000000000..62a56dfbb --- /dev/null +++ b/docs/_includes/trading_system/parameters.md @@ -0,0 +1,50 @@ + + +{% assign title = "Parameters" %} +{% assign definition = site.data.trading_system.parameters %} +{% assign preposition = "" %} + + + +{% if include.heading != "" %} +{{include.heading}} {{title}} +{% endif %} + +{% if include.icon != "no" %} + +{% endif %} + +**{{ definition }}** + + + +Each testing session has its own set of parameters. This allows you to configure different trading sessions with different parameters, and go back and forth between them as required. For instance, you may have different backtesting sessions with different date ranges, different exchange fees or different slippage settings. + + + +{% if include.adding != "" %} + +{{include.adding}} Adding {{preposition}} {{title}} + + + +To add a parameters node, select *Add Parameters* on the session or the trading system menu, depending on the context. When a parameters node is added, the full set of parameters are created with it. + +If you already have a parameters node but are missing some of the parameters, then select *Add Missing Params* on the menu. + + + +{% endif %} + +{% if include.configuring != "" %} + +{{include.configuring}} Configuring the {{title}} + + + +XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + + + +{% endif %} + diff --git a/docs/_includes/trading_system/quoted-asset.md b/docs/_includes/trading_system/quoted-asset.md new file mode 100644 index 000000000..342867403 --- /dev/null +++ b/docs/_includes/trading_system/quoted-asset.md @@ -0,0 +1,49 @@ + + +{% assign title = "Quoted Asset" %} +{% assign definition = site.data.trading_system.quote_asset %} +{% assign preposition = "a" %} + + + +{% if include.heading != "" %} +{{include.heading}} {{title}} +{% endif %} + +{% if include.icon != "no" %} + +{% endif %} + +**{{ definition }}** + + + +The quoted asset must reference the second asset in the same market of the same exchange as the reference established with the base asset. + + + +{% if include.adding != "" %} + +{{include.adding}} Adding {{preposition}} {{title}} + + + +To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. + +{% include note.html content="After adding a quoted asset node, make sure you establish a reference to the second asset in the same market of the same exchange as the reference established with the base asset." %} + + + +{% endif %} + +{% if include.configuring != "" %} + +{{include.configuring}} Configuring the {{title}} + + + +XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + + + +{% endif %} \ No newline at end of file diff --git a/docs/_includes/trading_system/slippage.md b/docs/_includes/trading_system/slippage.md new file mode 100644 index 000000000..fcc674beb --- /dev/null +++ b/docs/_includes/trading_system/slippage.md @@ -0,0 +1,67 @@ + + +{% assign title = "Slippage" %} +{% assign definition = site.data.trading_system.slipage %} +{% assign preposition = "a" %} + + + +{% if include.heading != "" %} +{{include.heading}} {{title}} +{% endif %} + +{% if include.icon != "no" %} + +{% endif %} + +**{{ definition }}** + + + +In the context of forward testing and live trading sessions, slippage does not affect the actual transactions. However, the parameter is taken into account when creating simulation layers, which are also available during forward testing and live trading. + +Slippage is factored both in the session reports and in the graphic representation of each trade provided by the simulation trades product of the trading bot. + + + +{% if include.adding != "" %} + +{{include.adding}} Adding {{preposition}} {{title}} + + + +To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. + + + +{% endif %} + +{% if include.configuring != "" %} + +{{include.configuring}} Configuring the {{title}} + + + +Select *Configure Slippage* on the menu to access the configuration. + +```json +{ +"positionRate": 0.1, +"stopLoss": 0.2, +"takeProfit": 0.3 +} +``` + +* ```positionRate``` is the slippage value to be applied to the rate of the take position order, expressed as a percentage (*i.e.:* 0.1 means 0.1%). + +* ```stopLoss``` is the slippage value to be applied to the rate of the stop order, expressed as a percentage (*i.e.:* 0.2 means 0.2%). + +* ```takeProfit``` is the slippage value to be applied to the rate of the take profit order, expressed as a percentage (*i.e.:* 0.3 means 0.3%). + +The number you enter is applied as a percentage of the price of the order and added or subtracted from the price depending on the circumstances, always working against you. For instance, ```"positionRate": 0.1``` means the position will be set at a price 0.1% higher or lower depending on which of the assets in the pair is your base asset. + +{% include note.html content="If the slippage parameter is left empty or detached both from your session and your trading system, slippage is not computed during simulations."%} + + + +{% endif %} \ No newline at end of file diff --git a/docs/_includes/trading_system/template.md b/docs/_includes/trading_system/template.md new file mode 100644 index 000000000..46e129074 --- /dev/null +++ b/docs/_includes/trading_system/template.md @@ -0,0 +1,47 @@ + + +{% assign title = "XXXXXXXXXXXXXXXX" %} +{% assign definition = site.data.trading_system.XXXXXXXXXXXXXXXX %} +{% assign preposition = "XXXXXXXXXXXXXXXX" %} + + + +{% if include.heading != "" %} +{{include.heading}} {{title}} +{% endif %} + +{% if include.icon != "no" %} + +{% endif %} + +**{{ definition }}** + + + +XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + + + +{% if include.adding != "" %} + +{{include.adding}} Adding {{preposition}} {{title}} + + + +XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + + + +{% endif %} + +{% if include.configuring != "" %} + +{{include.configuring}} Configuring the {{title}} + + + +XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + + + +{% endif %} \ No newline at end of file diff --git a/docs/_includes/trading_system/time-frame.md b/docs/_includes/trading_system/time-frame.md new file mode 100644 index 000000000..a88f51457 --- /dev/null +++ b/docs/_includes/trading_system/time-frame.md @@ -0,0 +1,86 @@ + + +{% assign title = "Time Frame" %} +{% assign definition = site.data.trading_system.time_frame %} +{% assign preposition = "a" %} + + + +{% if include.heading != "" %} +{{include.heading}} {{title}} +{% endif %} + +{% if include.icon != "no" %} + +{% endif %} + +**{{ definition }}** + + + +In the context of backtesting sessions, what time frame you decide to run the session on depends on the strategies being tested. If strategies make decisions based on the 1 hour candle and above, then ```01-hs``` may be the best choice. However, if decisions are influenced by sub-hour candles then you should match the time frame accordingly. + +In the context of live sessions, that is, paper trading, forward testing and live trading, you should run the session on the ```01-min``` time frame so that the trading bot reacts fast when the price tags the take profit or stop loss targets. + + + +{% if include.adding != "" %} + +{{include.adding}} Adding {{preposition}} {{title}} + + + +To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. + + + +{% endif %} + +{% if include.configuring != "" %} + +{{include.adding}} Configuring the {{title}} + + + +Select *Configure Time Frame* on the menu to access the configuration. + +```js +{ +"value": "01-min" +} +``` + +* ```value``` is the setting for the time frame. You may use any of the values below. + +Available options at the sub-hour level are: + +```json +01-min +02-min +03-min +04-min +05-min +10-min +15-min +20-min +30-min +45-min +``` + +Available options at larger time frames are: + +```json +01-hs +02-hs +03-hs +04-hs +06-hs +08-hs +12-hs +24-hs +``` + + + +{% endif %} + diff --git a/docs/_includes/trading_system/time-range.md b/docs/_includes/trading_system/time-range.md new file mode 100644 index 000000000..f5b4f3f6c --- /dev/null +++ b/docs/_includes/trading_system/time-range.md @@ -0,0 +1,72 @@ + + +{% assign title = "Time Range" %} +{% assign definition = site.data.trading_system.time_range %} +{% assign preposition = "a" %} + + + +{% if include.heading != "" %} +{{include.heading}} {{title}} +{% endif %} + +{% if include.icon != "no" %} + +{% endif %} + +**{{ definition }}** + + + + + + + +{% if include.adding != "" %} + +{{include.adding}} Adding {{preposition}} {{title}} + + + +To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. + + + +{% endif %} + +{% if include.configuring != "" %} + +{{include.configuring}} Configuring the {{title}} + + + +Select *Configure Time Range* on the menu to access the configuration. The configuration varies slightly depending on the type of session you are running. + +{{include.configuring}}# On Backtesting Sessions + +```json +{ +"initialDatetime": "2019-09-01T00:00:00.000Z", +"finalDatetime": "2019-09-25T00:00:00.000Z" +} +``` + +* ```initialDatetime``` is the datetime the session starts at. If you don't set an *initialDatetime* the system's fallback mechanism will try to get it from the parameters defined at the level of the trading system. + +* ```finalDatetime``` is the datetime the session finishes at. If you don't set a *finalDatetime* at the level of the testing session or the trading system, then calculations will run until the date there is data available. + +{{include.configuring}}# On Paper Trading, Forward Testing and Live Trading Sessions + +These sessions always start at the datetime the session is run, therefore, there is no configuration of an initial datetime. + +```json +{ +"finalDatetime": "2019-09-25T00:00:00.000Z" +} +``` + +* ```finalDatetime``` is the datetime the session finishes at. If you don't set a *finalDatetime* at the level of the testing session or the trading system, then the session runs for one year. + + + +{% endif %} \ No newline at end of file diff --git a/docs/pages/suite/suite-network-hierarchy.md b/docs/pages/suite/suite-network-hierarchy.md index 5df1a765a..4dbdb31f2 100644 --- a/docs/pages/suite/suite-network-hierarchy.md +++ b/docs/pages/suite/suite-network-hierarchy.md @@ -470,263 +470,19 @@ To stop a backtesting session, select *Stop* on the menu. -## Parameters +{% include /trading_system/parameters.md heading="##" icon="150-" adding="###" configuring="" %} - +{% include /trading_system/base-asset.md heading="##" icon="150-" adding="###" configuring="###" %} -**{{site.data.trading_system.parameters}}** +{% include /trading_system/quoted-asset.md heading="##" icon="150-" adding="###" configuring="" %} -Each testing session has its own set of parameters. This allows you to configure different trading sessions with different parameters, and go back and forth between them as required. For instance, you may have different backtesting sessions with different date ranges, different exchange fees or different slippage settings. +{% include /trading_system/time-frame.md heading="##" icon="150-" adding="###" configuring="###" %} -### Adding Parameters - -To add a parameters node, select *Add Parameters* on the session or the trading system menu, depending on the context. When a parameters node is added, the full set of parameters are created with it. - -If you already have a parameters node but are missing some of the parameters, then select *Add Missing Params* on the menu. - - - - - -## Base Asset - - - -**{{site.data.trading_system.base_asset}}** - -The basse asset must reference an asset in a specific market of a specific exchange in the Crypto Ecosystem hierarchy. - -### Adding a Base Asset - -To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. - -{% include note.html content="After adding a base asset node, make sure you establish a reference to the asset in a specific market of a specific exchange in the Crypto Ecosystem hierarchy." %} - -### Configuring the Base Asset - -Select *Configure Base Asset* on the menu to access the configuration. - -```json -{ -"initialBalance": 0.001, -"minimumBalance": 0.0001, -"maximumBalance": 0.1 -} -``` - -* ```initialBalance``` is the amount of capital you wish to allocate to the trading system. - -* ```minimumBalance``` is the threshold of accummulated losses that switches off the session; when your overall balance (balanceAssetA + balanceAssetB) drops to this value, all trading stops; think of the ```minimumBalance``` as a general safety switch. - -* ```maximumBalance``` is a similar concept as with the ```minimumBalance``` but on the high side of the ```initialBalance```. - - - - - -## Quoted Asset - - - -**{{site.data.trading_system.quoted_asset}}** - -The quoted asset must reference the second asset in the same market of the same exchange as the reference established with the base asset. - -### Adding a Quoted Asset - -To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. - -{% include note.html content="After adding a quoted asset node, make sure you establish a reference to the second asset in the same market of the same exchange as the reference established with the base asset." %} - - - - - -## Time Range - - - -**{{site.data.trading_system.time_range}}** - -### Adding a Time Range - -To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. - -### Configuring the Time Range - -Select *Configure Time Range* on the menu to access the configuration. The configuration varies slightly depending on the type of session you are running. - -#### On Backtesting Sessions - -```json -{ -"initialDatetime": "2019-09-01T00:00:00.000Z", -"finalDatetime": "2019-09-25T00:00:00.000Z" -} -``` - -* ```initialDatetime``` is the datetime the session starts at. If you don't set an *initialDatetime* the system's fallback mechanism will try to get it from the parameters defined at the level of the trading system. - -* ```finalDatetime``` is the datetime the session finishes at. If you don't set a *finalDatetime* at the level of the testing session or the trading system, then calculations will run until the date there is data available. - -#### On Paper Trading, Forward Testing and Live Trading Sessions - -These sessions always start at the datetime the session is run, therefore, there is no configuration of an initial datetime. - -```json -{ -"finalDatetime": "2019-09-25T00:00:00.000Z" -} -``` - -* ```finalDatetime``` is the datetime the session finishes at. If you don't set a *finalDatetime* at the level of the testing session or the trading system, then the session runs for one year. - - - - - -## Time Frame - - - -**{{site.data.trading_system.time_frame}}** - -In the context of backtesting sessions, what time frame you decide to run the session on depends on the strategies being tested. If strategies make decisions based on the 1 hour candle and above, then ```01-hs``` may be the best choice. However, if decisions are influenced by sub-hour candles then you should match the time frame accordingly. - -In the context of live sessions, that is, paper trading, forward testing and live trading, you should run the session on the ```01-min``` time frame so that the trading bot reacts fast when the price tags the take profit or stop loss targets. - -### Adding a Time Frame - -To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. - -### Configuring the Time Frame - -Select *Configure Time Frame* on the menu to access the configuration. - -```js -{ -"value": "01-min" -} -``` - -* ```value``` is the setting for the time frame. You may use any of the values below. - -Available options at the sub-hour level are: - -```json -01-min -02-min -03-min -04-min -05-min -10-min -15-min -20-min -30-min -45-min -``` - -Available options at larger time frames are: - -```json -01-hs -02-hs -03-hs -04-hs -06-hs -08-hs -12-hs -24-hs -``` - - - - - -## Slippage - - - -**{{site.data.trading_system.slippage}}** - -In the context of forward testing and live trading sessions, slippage does not affect the actual transactions. However, the parameter is taken into account when creating simulation layers, which are also available during forward testing and live trading. - -Slippage is factored both in the session reports and in the graphic representation of each trade provided by the simulation trades product of the trading bot. - -### Adding a Slippage - -To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. - -### Configuring the Slippage - -Select *Configure Slippage* on the menu to access the configuration. - -```json -{ -"positionRate": 0.1, -"stopLoss": 0.2, -"takeProfit": 0.3 -} -``` - -* ```positionRate``` is the slippage value to be applied to the rate of the take position order, expressed as a percentage (*i.e.:* 0.1 means 0.1%). - -* ```stopLoss``` is the slippage value to be applied to the rate of the stop order, expressed as a percentage (*i.e.:* 0.2 means 0.2%). - -* ```takeProfit``` is the slippage value to be applied to the rate of the take profit order, expressed as a percentage (*i.e.:* 0.3 means 0.3%). - -The number you enter is applied as a percentage of the price of the order and added or subtracted from the price depending on the circumstances, always working against you. For instance, ```"positionRate": 0.1``` means the position will be set at a price 0.1% higher or lower depending on which of the assets in the pair is your base asset. - -{% include note.html content="If the slippage parameter is left empty or detached both from your session and your trading system, slippage is not computed during simulations."%} - - - - - -## Fee Structure - - - -**{{site.data.trading_system.fee_structure}}** - -Exchange fees are a crucial part of trading. A strategy may work like a charm when you leave fees out of the equation but would lead you to bankruptcy in a live trading situation. - -Fee structures are factored both in the session reports and in the graphic representation of each trade provided by the simulation trades product of the trading bot. - -To illustrate how fees affect your bottom line, take a look at the image below. - -[![Trading-Simulation-Fees-Fails](https://user-images.githubusercontent.com/13994516/63636432-8d8cdf80-c66f-11e9-86a3-480d157d8126.gif)](https://user-images.githubusercontent.com/13994516/63636432-8d8cdf80-c66f-11e9-86a3-480d157d8126.gif) - -The trade hits the take profit target above the Position Rate level, however, due to fees, the trade has a negative 0.32% ROI. - -In the context of forward testing and live trading sessions, the fee structure assumptions do not affect actual transactions. However, the parameter is taken into account when creating simulation layers, which are also available during forward testing and live trading. - -### Adding a Fee Structure - -To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu. - -### Configuring the Fee Structure - -Select *Configure Fee Structure* on the menu to access the configuration. - -```json -{ -"maker": 0.15, -"taker": 0.25 -} -``` - -* ```maker``` is the setting for the fee the exchange charges when an order adds liquidity to the market, such as with limit orders. - -* ```taker``` is the setting for the fee the exchange charges when an order takes liquidity from the market, such as with market or instant orders. - -{% include note.html content="Check the fees structure in your exchange, carefully looking into the tier you fall in to feed accurate assumptions to your backtesting and paper trading sessions." %} - -{% include note.html content="If the fee structure parameter is left empty or detached both from your session and your trading system, fees are not computed during simulations." %} - -{% include important.html content="Remember that, for the time being, and until the new execution engine is released, all orders placed by the trading bot are *market orders*, thus, the *taker* fee applies in all cases." %} +{% include /trading_system/time-range.md heading="##" icon="150-" adding="###" configuring="###" %} +{% include /trading_system/slippage.md heading="##" icon="150-" adding="###" configuring="###" %} +{% include /trading_system/fee-structure.md heading="##" icon="150-" adding="###" configuring="###" %} diff --git a/docs/pages/suite/suite-trading-system-hierarchy.md b/docs/pages/suite/suite-trading-system-hierarchy.md index bbc960a4b..b023b5188 100644 --- a/docs/pages/suite/suite-trading-system-hierarchy.md +++ b/docs/pages/suite/suite-trading-system-hierarchy.md @@ -955,7 +955,6 @@ toc: false - ## Trading System @@ -964,7 +963,7 @@ toc: false Think of a trading system as a framework; the low-level logic that serves to structure the processes and methods that you will use to implement your trading strategies. In practical terms, a trading system is a hierarchical arrangement organizing the actionable aspects of your investment plan. -Therefore, you will use this hierarchy to define strategies, following the trading framework implemented by the Superalgos Protocol, splitting strategies in four stages: trigger, open, manage and close. +Therefore, you will use this hierarchy to define strategies, following the trading framework implemented by the Superalgos Protocol, splitting strategies into four stages: trigger, open, manage and close. These stages are played in a sequence. Once a strategy is *triggered* it will look to *open* a position. Once a position is open, it is time to *manage* it as the trade develops. And once a stop or take profit target is hit, it is time to *close* the position. @@ -978,63 +977,19 @@ To add a trading system, select *Add Trading System* on the workspace node menu. -## Parameters +{% include /trading_system/parameters.md heading="##" icon="150-" adding="###" configuring="" %} - +{% include /trading_system/base-asset.md heading="##" icon="150-" adding="###" configuring="###" %} -**{{site.data.trading_system.parameters}}** +{% include /trading_system/quoted-asset.md heading="##" icon="150-" adding="###" configuring="" %} +{% include /trading_system/time-frame.md heading="##" icon="150-" adding="###" configuring="###" %} +{% include /trading_system/time-range.md heading="##" icon="150-" adding="###" configuring="###" %} +{% include /trading_system/slippage.md heading="##" icon="150-" adding="###" configuring="###" %} - - -## Base Asset - - - -**{{site.data.trading_system.base_asset}}** - - - - - - -## Time Frame - - - -**{{site.data.trading_system.time_frame}}** - - - - - -## Time Range - - - -**{{site.data.trading_system.time_range}}** - - - - - -## Slippage - - - -**{{site.data.trading_system.slippage}}** - - - - - -## Fee Structure - - - -**{{site.data.trading_system.fee_structure}}** +{% include /trading_system/fee-structure.md heading="##" icon="150-" adding="###" configuring="###" %} @@ -1046,9 +1001,9 @@ To add a trading system, select *Add Trading System* on the workspace node menu. **{{site.data.trading_system.strategy}}** -The concept of describing strategies in phases is fundamental to the methodical aspect of the trading system, as it provides a framework to run every strategy with the exact same logic, which contributes to developing scalable trading systems that may grow to any number of strategies. +The concept of describing strategies in phases is fundamental to the methodical aspect of the trading system, as it provides a framework to run every strategy with the same logic, which contributes to developing scalable trading systems that may grow to any number of strategies. -The definition of strategy points to the concept of *a trade*. A trade is the process that exchanges the base asset for the quoted asset and that—after some time, as the trade develops and targets are hit—exchanges back the quoted asset for the base asset. The first and foremost rule of a trade is to preserve capital and its main goal is to increase it. +The definition of strategy points to the concept of *a trade*. A trade is a process that exchanges the base asset for the quoted asset and that—after some time, as the trade develops and targets are hit—exchanges back the quoted asset for the base asset. The first and foremost rule of a trade is to preserve capital and its main goal is to increase it. @@ -1059,7 +1014,7 @@ To add a strategy, select *Add Strategy* on the trading system node menu. The st {% include tip.html content="You may work with as many strategies as you wish. " %} -{% include important.html content="Strategies within the same trading system work in the same market, have the same base asset, and —most importantly—share the same capital. This means that only one strategy in the trading system may be triggered at any one point, and that no other strategy in the trading system may be triggered until the first one is triggered off. If you wish to have more than one strategy trading at the same time, then those strategies must be put in separate trading systems. " %} +{% include important.html content="Strategies within the same trading system work in the same market, have the same base asset, and —most importantly—share the same capital. This means that only one strategy in the trading system may be triggered at any one point and that no other strategy in the trading system may be triggered until the first one is triggered off. If you wish to have more than one strategy trading at the same time, then those strategies must be put in separate trading systems. " %} @@ -1071,19 +1026,19 @@ To add a strategy, select *Add Strategy* on the trading system node menu. The st **{{site.data.trading_system.trigger_stage}}** -A trading system may have mutiple strategies designed for the same market, with the same base asset. +A trading system may have multiple strategies designed for the same market, with the same base asset. An important aspect of trading systems is that they are allocated a certain amount of capital (see the base asset parameter). As a consequence, strategies within a trading system have to share that capital allocation. -The logic behind the concept of the trigger stage makes the assumption that different strategies within a trding system are specialized for trading in different market conditions. The trigger stage in each strategy is, therefore, the mechanism by which any particular strategy may be selected to trade, given any particular market situation. +The logic behind the concept of the trigger stage assumes that different strategies within a trading system are specialized for trading in different market conditions. The trigger stage in each strategy is, therefore, the mechanism by which any particular strategy may be selected to trade, given any particular market situation. The triggering-on of a strategy effectively blocks the selection of any other strategy in the trading system, and reserves the whole capital allocation for a potential trade, until the strategy is triggered-off. -As a corolary, if certain strategies are meant to trade under the same market situations and open trades concurrently, then those strategies should be put in separate trading systems. +As a corollary, if certain strategies are meant to trade under the same market situations and open trades concurrently, then those strategies should be put in separate trading systems. ### Adding a Trigger Stage -To add a trigger stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them, and their events. +To add a trigger stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them and their events. @@ -1097,7 +1052,7 @@ To add a trigger stage node, select *Add Missing Stages* on the strategy node me In conceptual terms, the trigger-on event is the mechanism you use to define the specific situations in which you would consider trading with the corresponding strategy. Think of the trigger-on event as the definition of the scenario in which the trading idea behind the strategy should be carefully considered. -Once a strategy is triggered-on, the system starts evaluating the take postion event. In conceptual terms, it means that the system has been alerted that the trading idea behind the corresponding trading strategy has produced a signal, and that it should carefully monitor the market for the opportunity of taking a position. +Once a strategy is triggered-on, the system starts evaluating the take position event. In conceptual terms, it means that the system has been alerted that the trading idea behind the corresponding trading strategy has produced a signal and that it should carefully monitor the market for the opportunity of taking a position. ### Adding a Trigger-On Event @@ -1132,7 +1087,7 @@ To add a situation, select *Add Situation* on the corresponding event node menu. **{{site.data.trading_system.condition}}** -Therefore, conditions are used to mathematically describe what needs to happen with the market in order for a certain action to be taken. +Therefore, conditions are used to mathematically describe what needs to happen with the market for a certain action to be taken. **For example:** @@ -1181,7 +1136,7 @@ To add a trigger-off event node, select *Add Missing Events* on the trigger stag {{site.data.trading_system.take_position_event}} -Remember that the trigger-on event merely selects a strategy to be considered for trading under the current market situation. The actual decision to enter a position may require more specific conditions to be met. For that reasons, the take position event is a separate entity in regards with the trigger-on event. +The trigger-on event merely selects a strategy to be considered for trading under the current market situation. The actual decision to enter a position may require more specific conditions to be met. For that reason, the take position event is a separate entity from the trigger-on event. Therefore, the take position event is defined with its own set of situations and conditions. @@ -1201,7 +1156,7 @@ To add a take position event node, select *Add Missing Events* on the trigger st **{{site.data.trading_system.open_stage}}** -Conceptually, the open stage deals with the details that concern the opening of a trade once the decision to take a position has been made. In this stage you deal with the aforementioned parameters, each of which is defined by a formula. +Conceptually, the open stage deals with the details that concern the opening of a trade once the decision to take a position has been made. In this stage, you deal with the aforementioned parameters, each of which is defined by a formula. Ideally, the open stage would also handle the parameters that define the execution of the trade, that is, how and which kinds of orders are to be placed, on which exchanges and so on. However, the execution side of the system is still under development. For the time being, execution is drastically simplified: a single market order is placed for each order. @@ -1209,7 +1164,7 @@ Ideally, the open stage would also handle the parameters that define the executi ### Adding an Open Stage -To add an open stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them, and their events. +To add an open stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them and their events. @@ -1234,9 +1189,9 @@ To add an initial definition node, select *Add Initial Definition* on the open s **{{site.data.trading_system.initial_stop}}** -Notice that the setting of the stop target has no relation with the execution of orders. The stop is a target, not an order to be placed. That is, the system does not place stop orders. +Notice that the setting of the stop target has no relation to the execution of orders. The stop is a target, not an order to be placed. That is, the system does not place stop orders. -This is a design feature which allows you to keep your cards, not allowing anyone to anticipate what your strategy may be, not even the exchange. It is a known fact that some exchanges may attempt or allow to front run stop orders. +This is a design feature that allows you to keep your cards, not allowing anyone to anticipate what your strategy may be, not even the exchange. It is a known fact that some exchanges may attempt or allow to front-run stop orders. Instead, the trading bot instance monitors the market, and only once the stop target has been hit does it place the corresponding order to close the trade. @@ -1276,7 +1231,7 @@ Formulas may use [internal variables](suite-internal-variables.html) made availa **For example:** -* ```positionRate - positionRate * 2.5 / 100``` → This formula may be used to define an intial stop target 2.5% below the rate at which the position was taken. +* ```positionRate - positionRate * 2.5 / 100``` → This formula may be used to define an initial stop target 2.5% below the rate at which the position was taken. {% include note.html content="To learn which variables may be used in formulas, see the page about internal variables." %} @@ -1316,7 +1271,7 @@ The initial target is set in phase 0, which may shift to the following phase onc ### Adding an Initial Take Profit -To add an initial take profit node, select *Add Missing Items* on the initial definitions node menu. All items that may be missing are created along with the rest of the basic structure of nodes required to define each of them. +To add an initial take-profit node, select *Add Missing Items* on the initial definitions node menu. All items that may be missing are created along with the rest of the basic structure of nodes required to define each of them. @@ -1358,11 +1313,11 @@ To add a position rate node, select *Add Missing Items* on the initial definitio **{{site.data.trading_system.open_execution}}** -{% include note.html content="You don't need to do anything with this node for the time being, other than make sure its present once you are ready to trade live." %} +{% include note.html content="You don't need to do anything with this node for the time being, other than make sure it is present once you are ready to trade live." %} ### Adding an Open Execution Node -To add an open execution node, select *Add open Execution* on the open stage node menu. +To add an open execution node, select *Add Open Execution* on the open stage node menu. @@ -1374,23 +1329,23 @@ To add an open execution node, select *Add open Execution* on the open stage nod **{{site.data.trading_system.manage_stage}}** -The management of a trade aims to increase the efficiency of your trading system. Conceptually, a trade is not an instant event, but an event which has a opening, a period of maturation, and a closing. The management of the trade happens in that period of maturation. +The management of a trade aims to increase the efficiency of your trading system. Conceptually, a trade is not an instant event, but an event which has an opening, a period of maturation, and a closing. The management of the trade happens in that period of maturation. The concept of managing the trade means that the formulas to determine the take profit and stop may change as the trade develops. The typical situation in which you may want to change your original take profit and stop formulas is when the trade seems to be going well in your favor. -It may be in your best interest to manage both stop and take profit, moving them in the direction of the trade as the market moves, allowing some leeway for a larger profit than expected and, at the same time, cutting the potential for losses. +It may be in your best interest to manage both stop and take-profit targets, moving them in the direction of the trade as the market moves, allowing some leeway for a larger profit than expected and, at the same time, cutting the potential for losses. The management of the trade is handled in phases. Actually, the management of take profit and stop—while correlated—is done independently of each other, therefore, each concept has its own set of phases. -When a situation defined by a set of conditions is met, the event indicates that the take profit or stop formulas shall be changed. At the moment those predefined conditions are met, you enter the next phase. Keep in mind that the trade is in constant development, so there may be as many phases as you deem appropriate for your particular strategy. +When a situation defined by a set of conditions is met, the next phase event indicates that the take profit or stop formulas shall be changed. At the moment those predefined conditions are met, you enter the next phase. Keep in mind that the trade is in constant development, so there may be as many phases as you deem appropriate for your particular strategy. -The idea of having different phases comes from the notion that big market moves tend to provide clues as of what may come up next. For instance, rallies may accelerate as more traders join the move. Recognizable patterns may emerge. Signs of exhaustion may be identified. +The idea of having different phases comes from the notion that big market moves tend to provide clues as to what may come up next. For instance, rallies may accelerate as more traders join the move. Recognizable patterns may emerge. Signs of exhaustion may be identified. All of these considerations should feed the dynamic analysis performed as the trade develops, and may be contrasted with the predefined conditions that may push take profit or stop further, entering one phase after the next. ### Adding a Manage Stage -To add a manage stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them, and their events. +To add a manage stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them and their events. @@ -1401,9 +1356,9 @@ To add a manage stage node, select *Add Missing Stages* on the strategy node men **{{site.data.trading_system.stop}}** -stop: "Stop sets a new stop loss target associated with the corresponding phase." - +### Adding a Stop Node +To add a stop node, select *Add Missing Items* on the manage stage node menu. All items that may be missing are created along with the rest of the basic structure of nodes required to define each of them. @@ -1413,9 +1368,13 @@ stop: "Stop sets a new stop loss target associated with the corresponding phase. **{{site.data.trading_system.phase_1}}** -phase_1: "Phase 1 is the first phase in the management of a stop or take profit target. The management of targets may have as many phases as required." +The management of phases happens in a sequence. Phase 1 comes after phase 0, which holds the initial definitions for stop and take profit targets. You may continue adding phase 2, phase 3 and so on. Once the next phase event is triggered in one phase, the system applies the targets of the following phase and starts monitoring the situations defined in the corresponding next phase event. +{% include note.html content="Notice that stop loss and take profit phases are independent and defined separately from each other, each below the corresponding stop and take-profit branch of the manage stage." %} +### Adding a New Phase + +To add a new phase, select *Add Phase* on the stop or take-profit node menu. A new phase is added along with the basic structure of nodes required to define each of them and their events. @@ -1429,7 +1388,9 @@ phase_1: "Phase 1 is the first phase in the management of a stop or take profit **{{site.data.trading_system.take_profit}}** -take_profit: "Take profit sets a new take profit target associated with the corresponding phase." +### Adding a Take Profit Node + +To add a take profit node, select *Add Missing Items* on the manage stage node menu. All items that may be missing are created along with the rest of the basic structure of nodes required to define each of them. @@ -1446,13 +1407,13 @@ take_profit: "Take profit sets a new take profit target associated with the corr **{{site.data.trading_system.close_stage}}** -As explained earlier while discussing the open stage, the execution functionality is currently under development. Needless to say, execution of the closing orders is of the highest significance, but in the mean time some temporal execution limitations apply. +As explained earlier while discussing the open stage, the execution functionality is currently under development. Needless to say, execution of the closing orders is of the highest significance, but in the meantime some temporal execution limitations apply. -Also pending development is the keeping of a formal trading log. The current functionality allows you to see each trade on the screen, along with all the corresponding details, as well as a consolidated report on the live trading panel. This information is stored as a data product, thus, is not lost. In the future, the system should incorporate a user-friendly feature to browse such logs, and even help analyze them in search for potential optimizations of your trading systems. +Also pending development is the keeping of a formal trading log. The current functionality allows you to see each trade on the screen, along with all the corresponding details, as well as a consolidated report on the live trading panel. This information is stored as a data product, thus, it is not lost. In the future, the system should incorporate a user-friendly feature to browse such logs, and even help analyze them in search for potential optimizations of your trading systems. ### Adding a Close Stage -To add a close stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them, and their events. +To add a close stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them and their events. @@ -1463,4 +1424,8 @@ To add a close stage node, select *Add Missing Stages* on the strategy node menu **{{site.data.trading_system.close_execution}}** -close_execution: "Close execution is the node that will eventually hold the information regarding the execution of the trade closing orders." \ No newline at end of file +{% include note.html content="You don't need to do anything with this node for the time being, other than make sure it is present once you are ready to trade live." %} + +### Adding a Close Execution Node + +To add a close execution node, select *Add Close Execution* on the open stage node menu. \ No newline at end of file