From ae0018348f44b8fac9a702a3d2db485afc625cf6 Mon Sep 17 00:00:00 2001 From: Philip Love Date: Fri, 28 May 2021 21:04:57 -0400 Subject: [PATCH 1/3] Docs: user-defined-variables --- .../Docs-Nodes/user-defined-variables.json | 29 +++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variables.json diff --git a/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variables.json b/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variables.json new file mode 100644 index 000000000..299e82b2f --- /dev/null +++ b/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variables.json @@ -0,0 +1,29 @@ +{ + "type": "User Defined Variables", + "definition": { + "text": "The User Defined Variables node structure is an unused area of the Trading Engine users can access from within their Trading System to store data.", + "updated": 1622234154032 + }, + "paragraphs": [ + { + "style": "Text", + "text": "

Overview

Oftentimes, when building a strategy, the need for a place to store some data may arise. The User Defined Variables nodes are is the correct place to do this. The children nodes, (User Defined variable nodes), of this node are unused by the base code of the Superalgos processes thus the data placed inside these variables will remain unchanged and available for the duration of the episode.", + "updated": 1622249947455 + }, + { + "style": "Text", + "text": "

Additional Info

", + "updated": 1622250099965 + }, + { + "style": "Text", + "text": "- Persistence: It should be noted that these variables will persist throughout the engine's episode; not just at the stage or strategy layer from which they are set.", + "updated": 1622250113448 + }, + { + "style": "Text", + "text": "- State: A user defined variable is mutable.", + "updated": 1622250209793 + } + ] +} \ No newline at end of file From fa64a8d37b197cf855048829dfc87120d876453a Mon Sep 17 00:00:00 2001 From: Philip Love Date: Sat, 29 May 2021 10:56:17 -0400 Subject: [PATCH 2/3] Update: Some Docs Definitions --- .../Schemas/Docs-Nodes/user-defined-code.json | 4 ++-- .../Schemas/Docs-Nodes/user-defined-variable.json | 14 ++++++++++++++ .../Schemas/Docs-Nodes/user-defined-variables.json | 12 ++++++++---- 3 files changed, 24 insertions(+), 6 deletions(-) create mode 100644 Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variable.json diff --git a/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-code.json b/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-code.json index 28d83d7ea..d2237142f 100644 --- a/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-code.json +++ b/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-code.json @@ -1,8 +1,8 @@ { "type": "User Defined Code", "definition": { - "text": "You can use this node to inject your own executable code into the the Trading System. The exact moment when this code will be run depends on its config properties. From your code you can access the Trading Engine, read and modify it's values, modifying the standar behaviour of the Trading Bot.", - "updated": 1621988586103 + "text": "You can use this node to inject your own executable code into the the Trading System. The exact moment when this code will be run depends on its config properties. From your code you can access the Trading Engine, read and modify it's values, modifying the standard behaviour of the Trading Bot.", + "updated": 1622299982600 }, "paragraphs": [ { diff --git a/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variable.json b/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variable.json new file mode 100644 index 000000000..d2eba788e --- /dev/null +++ b/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variable.json @@ -0,0 +1,14 @@ +{ + "type": "User Defined Variable", + "definition": { + "text": "The User-Defined-Variable is a mutable storage container for whatever arbitrary data the user may want to manage while running a Trading System.", + "updated": 1622299578764 + }, + "paragraphs": [ + { + "style": "Text", + "text": "These variables can be easily set or get by using the Copy Node Path in the node's popup modal.", + "updated": 1622299861437 + } + ] +} \ No newline at end of file diff --git a/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variables.json b/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variables.json index 299e82b2f..6435c92ea 100644 --- a/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variables.json +++ b/Projects/Superalgos/Schemas/Docs-Nodes/user-defined-variables.json @@ -7,8 +7,12 @@ "paragraphs": [ { "style": "Text", - "text": "

Overview

Oftentimes, when building a strategy, the need for a place to store some data may arise. The User Defined Variables nodes are is the correct place to do this. The children nodes, (User Defined variable nodes), of this node are unused by the base code of the Superalgos processes thus the data placed inside these variables will remain unchanged and available for the duration of the episode.", - "updated": 1622249947455 + "text": "

Overview

", + "updated": 1622299369556 + }, + { + "style": "Text", + "text": "Oftentimes, when building a strategy, the need for a place to store some data may arise. The User-Defined-Variables nodes are the correct place to do this. The children nodes, (User Defined variable nodes), of this node are unused by the base code of the Superalgos processes thus the data placed inside these variables will remain unchanged and available for the duration of the episode." }, { "style": "Text", @@ -17,8 +21,8 @@ }, { "style": "Text", - "text": "- Persistence: It should be noted that these variables will persist throughout the engine's episode; not just at the stage or strategy layer from which they are set.", - "updated": 1622250113448 + "text": "- Persistence: It should be noted that these variables will persist throughout the System's episode; not just at the stage or strategy layer from which they are set.", + "updated": 1622299441071 }, { "style": "Text", From f97a35b0052ecafa67f9c4f79f1665932aac96bb Mon Sep 17 00:00:00 2001 From: Philip Love Date: Sat, 29 May 2021 11:10:24 -0400 Subject: [PATCH 3/3] Update: Docs for Close Stage Behaviour --- Projects/Superalgos/Schemas/Docs-Nodes/close-stage.json | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Projects/Superalgos/Schemas/Docs-Nodes/close-stage.json b/Projects/Superalgos/Schemas/Docs-Nodes/close-stage.json index 8c36f2243..30d55526c 100644 --- a/Projects/Superalgos/Schemas/Docs-Nodes/close-stage.json +++ b/Projects/Superalgos/Schemas/Docs-Nodes/close-stage.json @@ -43,6 +43,11 @@ "style": "Text", "text": "For example, in the open stage, you probably defined the target size as a function of the capital allocated to the trading system. In the close stage, you will likely want to define the target size as a function of the size filled, that is, the amount of the orders placed that was filled during the open stage." }, + { + "style": "Text", + "text": "In the event that the target size of the asset to be traded in Close Stage is equal to zero then Close Stage will close as will the currently running strategy. For example: Suppose the Open Stage was to trade x amount of quoted asset at y price via a limit order. But instead price moved in the opposite direction and to the point that Open Stage closed prior to the accumulation of any of the Base Asset which was to be traded via the Close Stage. In that scenario Close Stage would not take any action and would Close the current instance of the Strategy and the system would resume polling for another Trigger On event.", + "updated": 1622300970890 + }, { "style": "Include", "text": "Superalgos->Topic->Why My Stage is not Closing?->The Stage Does Not Close",