Bug Fixes Table and Gif
This commit is contained in:
1 parent
125d16f755
commit
4c3b825caf
18 files changed
+101
-771
No files matched your search
@@ -0,0 +1,36 @@
|
||||
{
|
||||
"type": "The Docs Explained",
|
||||
"definition": {
|
||||
"text": "This book will walk you through everything you need to know about the Docs.",
|
||||
"updated": 1609762580891
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Chapter",
|
||||
"text": "Superalgos->I->Docs Basics->Read Chapter I to learn the basics concepts. They are the foundation that will let you understand the commands and styles explained later in this book.",
|
||||
"updated": 1609763076399
|
||||
},
|
||||
{
|
||||
"style": "Chapter",
|
||||
"text": "Superalgos->II->Docs Commands->The Docs include a powerful command line interface that allows you to quickly fire commands from the search box. Dive into Chapter II to learn the details of each available command.",
|
||||
"updated": 1609763122458
|
||||
},
|
||||
{
|
||||
"style": "Chapter",
|
||||
"text": "Superalgos->III->Docs Commands Errors"
|
||||
},
|
||||
{
|
||||
"style": "Chapter",
|
||||
"text": "Superalgos->IV->Docs Commands Messages",
|
||||
"updated": 1609783744261
|
||||
},
|
||||
{
|
||||
"style": "Chapter",
|
||||
"text": "Superalgos->V->Docs Paragraph Styles"
|
||||
},
|
||||
{
|
||||
"style": "Chapter",
|
||||
"text": "Superalgos->VI->Docs Context Menu Actions"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,53 @@
|
||||
{
|
||||
"type": "Test",
|
||||
"definition": {
|
||||
"text": "Write here the summary / definition of this Concept."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "|Left click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode. |",
|
||||
"updated": 1610003511503
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "| otro row |"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "| y otro |"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "| otro row |"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "| y otro |"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "| otro row |"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "| y otro |"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "| otro row |"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "| y otro |"
|
||||
},
|
||||
{
|
||||
"style": "Gif",
|
||||
"text": "Test link"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "link"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -3,10 +3,5 @@
|
||||
"definition": {
|
||||
"text": "Limit buy orders is the section of the data structure that keeps track of this specific type of order."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Left click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode."
|
||||
}
|
||||
]
|
||||
"paragraphs": []
|
||||
}
|
||||
@@ -3,10 +3,5 @@
|
||||
"definition": {
|
||||
"text": "Limit sell orders is the section of the data structure that keeps track of this specific type of order."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Left click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode."
|
||||
}
|
||||
]
|
||||
"paragraphs": []
|
||||
}
|
||||
@@ -3,10 +3,5 @@
|
||||
"definition": {
|
||||
"text": "Market sell orders is the section of the data structure that keeps track of this specific type of order."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Left click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode."
|
||||
}
|
||||
]
|
||||
"paragraphs": []
|
||||
}
|
||||
@@ -1,12 +1,3 @@
|
||||
{
|
||||
"type": "Nodes Announcements",
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Left click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode."
|
||||
}
|
||||
],
|
||||
"definition": {
|
||||
"text": "Right click to edit this text and replace it with a definition / summary for this page. ESC to exit edit mode."
|
||||
}
|
||||
"type": "Nodes Announcements"
|
||||
}
|
||||
@@ -11,16 +11,6 @@
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Beyond the graphic representation of data over the charts, plotters may also feature a data panel, that is, a numerical representation of the data showing the exact figures corresponding to the column or period that is in focus (the point of the charts where the mouse pointer is at any point)."
|
||||
},
|
||||
{
|
||||
"style": "Block",
|
||||
"text": "Configuring",
|
||||
"updated": 1609932499869
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Plotter Panel Configuration",
|
||||
"updated": 1609932508408
|
||||
}
|
||||
]
|
||||
}
|
||||
+1
-1
@@ -27,4 +27,4 @@
|
||||
"updated": 1609945833844
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -1,42 +0,0 @@
|
||||
{
|
||||
"topic": "How To",
|
||||
"pageNumber": "1",
|
||||
"type": "Detach and Attach Nodes",
|
||||
"definition": {
|
||||
"text": "To detach a node, click on the detach button on the node's menu. To attach a node, right-click it and drag it closer to the node you wish to attach it to. Release the right-click when the target node is highlighted.",
|
||||
"updated": 1609948586650
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Block",
|
||||
"text": "Content",
|
||||
"updated": 1609948673015
|
||||
},
|
||||
{
|
||||
"style": "Gif",
|
||||
"text": "GIFs/Superalgos/Docs/design-space/fundamental-design-space-concepts-01.gif",
|
||||
"updated": 1609948684397
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "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."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "This feature is useful when testing different configurations, rules or parameters, as it allows to keep alternatives handy in the workspace."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Nodes may be attached only to potential parents. The system limits the way in which nodes may be attached, according to the logic of the information they contain."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "Nodes may not be detached or attached to frozen nodes. You need to unfreeze them before attaching or detaching.",
|
||||
"updated": 1609948096499
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The verbs to chain and to attach may be used interchangeably, as synonyms. Similarly, to unchain and to detach are both valid."
|
||||
}
|
||||
]
|
||||
}
|
||||
-34
@@ -1,34 +0,0 @@
|
||||
{
|
||||
"topic": "How To",
|
||||
"pageNumber": "2",
|
||||
"type": "Establish and Remove References",
|
||||
"definition": {
|
||||
"text": "To establish a reference, right-click on the first node and drag it close to the target node. The remove a reference, use the delink button on the menu.",
|
||||
"updated": 1609949247846
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Block",
|
||||
"text": "Content",
|
||||
"updated": 1609950313725
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "When establishing a reference, grey rings show which nodes you may establish the reference with. In case there are multiple nodes that would accept the reference, the one closer to the node where the reference originates is highlighted with a golden ring. Releasing the mouse button establishes the reference with the highlighted node."
|
||||
},
|
||||
{
|
||||
"style": "Gif",
|
||||
"text": "GIFs/Superalgos/Docs/design-space/establish-and-remove-references.gif",
|
||||
"updated": 1609949883448
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The reference is visually represented by a faint grey dotted line. Such line is visible only when both ends of the reference are visible."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "To remove a reference or delink two nodes, use the delink button on the node where the reference originates.",
|
||||
"updated": 1609949517565
|
||||
}
|
||||
]
|
||||
}
|
||||
-60
@@ -1,60 +0,0 @@
|
||||
{
|
||||
"topic": "Introduction",
|
||||
"pageNumber": "1",
|
||||
"type": "Fundamental Superalgos Concepts",
|
||||
"definition": {
|
||||
"text": "Superalgos breaks up complexity and describes the fundamental concepts that make up trading intelligence in hierarchies of nodes. Nodes may reference other nodes to access information in other hierarchies.",
|
||||
"updated": 1609943915544
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Algorithmic trading is a data-driven application. It is the superior ability to derive intelligence from data—above all—that gives automated trading an edge over trading manually.",
|
||||
"updated": 1609943931550
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "However, it would be simplistic to assume that trading intelligence emerges from data alone."
|
||||
},
|
||||
{
|
||||
"style": "Callout",
|
||||
"text": "Trading intelligence emerges from harnessing the interactions of multiple complex concepts."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Superalgos is a software infrastructure that contributes to harnessing those concepts and interactions by breaking complexity into small units of information called nodes and arranging them into larger data structures called hierarchies."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "A hierarchy is a data structure representing an overarching, top-level concept, resulting in a long chain of nodes, usually with many ramifications. The system manages different types of hierarchies, each of them with a specific focus. For example, crypto ecosystem, data mines, or charting space."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "A node is a small data structure containing information that may be related to market information, trading intelligence, the operation of the system, or other concepts. They are visually represented by icons in the design space."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The design space is the visual environment that hosts all system and user definitions. In practical terms, it is the black space below the slider that splits the screen horizontally, separating the design space in the bottom from the charting space on top. As a hierarchy, it features nodes that enable user-control over certain aspects of the look, feel, and behavior of the space."
|
||||
},
|
||||
{
|
||||
"style": "Callout",
|
||||
"text": "In other words, nodes arranged in hierarchical data structures describe the top-level concepts that make up trading intelligence in a way that helps users visualize and better understand them."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "These top-level concepts described as hierarchies interact with other concepts, that is, with other hierarchies. Interactions among hierarchies are called references."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "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."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "To organize all of this information, Superalgos manages the concept of workspaces. A workspace is an entity storing all system and user-generated information, excluding the state and contents of plugins. In technical terms, a workspace is a JSON file."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": " Note: The Bots page brings these conceptual definitions down to earth and offers an overview of how what these top-level concepts are and how they interact with each other."
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,109 +0,0 @@
|
||||
{
|
||||
"topic": "Introduction",
|
||||
"pageNumber": "2",
|
||||
"type": "Bots In Superalgos",
|
||||
"definition": {
|
||||
"text": "Bots are a crucial concept in Superalgos, and a good thread to explain how hierarchies interact with each other.",
|
||||
"updated": 1609944023850
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "While sometimes people use the terms trading bot, trading strategy, and trading system interchangeably, in Superalgos the distinction is sharp and unequivocal. Let’s start by offering three fundamental definitions:",
|
||||
"updated": 1609944046617
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "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."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Trading Strategy: A trading strategy is the description of a set of actions or events run in stages. Events are triggered upon the validation of precise conditions describing specific market situations. Trading strategies are designed to achieve a specific goal within the broader plan of a trading system via taking and managing positions."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Trading Bot: A trading bot is a computer program that—based on datasets exposed as products by other bots (counting sensors, indicators and even other trading bots)—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."
|
||||
},
|
||||
{
|
||||
"style": "Callout",
|
||||
"text": "In Superalgos, trading systems and trading strategies are definitions describing trading logic, while the trading bot is the computer program that uses the trading logic to test strategies, produce simulations, and trade."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "This documentation expands extensively on these three concepts. For the time being, the above distinction is sufficient to continue.",
|
||||
"updated": 1609944079526
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Before diving into an in-depth exploration of each hierarchy, a quick overview is in order. One of the most important underlying concepts in Superalgos is that of bots. Let’s then use bots as the guiding thread to show you how the different hierarchies in Superalgos interact with each other."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Bot Definitions"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "In the pages describing data mines and trading mines you will learn that bots are algorithms defined in such mines. That is, mines hold the source code and configuration—the complete set of definitions—of the three existing kinds of bots: sensors, indicators, and the trading bot."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "As a user, you may use all bots in data mines shipping with the system. As a developer, you may create your own mines to develop your own sensors, indicators, and even a new trading bot."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Bot Instances"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Using any of these bots entails creating an instance of the bot definition, so that this instance may run the bot’s code. You will seldom need to create bot instances manually, as the process of installing a new market creates all necessary bot instances for your data mining operation and for running trading sessions (by the way, markets are defined and installed from within the crypto ecosystem hierarchy)."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "A bot instance is a reference to a bot as defined in a data or trading mine. The instance of the bot runs the defined processes and generates the defined data products."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Bot instances are run from within the network hierarchy. You use task managers and tasks to control bot instances, meaning, to start and stop them. Also in the network hierarchy lies the configurations about where the data they generate is to be stored."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Bot Dependencies"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Upon execution, bot instances run in a branched sequence determined by their status and data dependencies. For instance, if bot Alice depends on the data produced by bot Bob, then Alice is configured to run as soon as Bob finishes its execution. These configurations are already set up in the corresponding data mines for all existing bots. Therefore, you only need to worry about this if you develop new bots."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "What you do need to understand as a user is that, if Alice depends on data Bob produces, then Bob needs to be running for Alice to do her job. If Bob is not running, then Alice can only sit and wait for Bob to do his part first."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "A good example of such dependencies may be found when running a live trading session. In such a case, the trading bot depends on the sensor and all indicator bots used in the referenced trading system. Indicators must process the data so that the trading bot may analyze it in realtime. Therefore, before running a live trading session, the data mining operation must be running and up to date."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Bots Execution"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Each bot runs for as long as it may require to perform its job, usually in the order of a few seconds, and remains asleep until the next cycle is due. That is, bots run for short bursts, in frequent cycles. The reason for this behavior is that bots are prepared to read live data feeds and process it online."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Bots need to know which market of which exchange they should work with. Exchanges and markets are defined in the crypto ecosystem hierarchy. Bots obtain that information by establishing references with the appropriate markets in that hierarchy."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "In the case of the trading bot, it also needs to know which type of trading session it should run, and what trading system’s rules it should follow. For those reasons, trading bots are paired with a specific session, which in turn, references a trading system."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Trading systems are themselves hierarchies. You may create a trading system by following a framework in which strategies are described in stages. You do not need to code to create a strategy, as the rules are written with simple mathematical statements. However, both basic and advanced knowledge of JavaScript will give you an edge. You may test and deploy your trading system by running trading sessions from within the network hierarchy."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,203 +0,0 @@
|
||||
{
|
||||
"topic": "Introduction",
|
||||
"pageNumber": "3",
|
||||
"type": "Hierarchies",
|
||||
"definition": {
|
||||
"text": "A hierarchy is a data structure representing an overarching, top-level concept, resulting in a long chain of nodes, usually with many ramifications. The system manages different types of hierarchies, each of them with a specific focus.",
|
||||
"updated": 1609945718294
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": " In the design space, the head or parent node of each hierarchy is represented by the corresponding icon surrounded by an ever-present white ring, so that they are easier to locate within the workspace.",
|
||||
"updated": 1609944331184
|
||||
},
|
||||
{
|
||||
"style": "Important",
|
||||
"text": " Hierarchies included in the workspace as plugins are not saved at the workspace level. As such, changes made in those hierarchies do not persist. If you wish to modify a plugin and keep working with the modified version in the future, you must either clone or backup the plugin and work on the resulting copy instead.",
|
||||
"updated": 1609945802943
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Superalgos Project",
|
||||
"updated": 1609945005370
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Superalgos Project->Definition",
|
||||
"updated": 1609944933341
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Superalgos Project->Content",
|
||||
"updated": 1609944944285
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Design Space",
|
||||
"updated": 1609945819410
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Design Space->Definition",
|
||||
"updated": 1609945823788
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Design Space->Content",
|
||||
"updated": 1609945827564
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Crypto Ecosystem"
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Crypto Ecosystem->Definition",
|
||||
"updated": 1609945187089
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Crypto Ecosystem->Content",
|
||||
"updated": 1609945202345
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Network",
|
||||
"updated": 1609945037649
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Network->Definition",
|
||||
"updated": 1609945860234
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Network->Content",
|
||||
"updated": 1609945864347
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Charting Space",
|
||||
"updated": 1609945048562
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Charting Space->Definition",
|
||||
"updated": 1609945880962
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Charting Space->Content",
|
||||
"updated": 1609945886008
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Trading System",
|
||||
"updated": 1609945101604
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Trading System->Definition",
|
||||
"updated": 1609945942207
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Trading System->Content",
|
||||
"updated": 1609945952584
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Trading Mine"
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Trading Mine->Definition",
|
||||
"updated": 1609945981528
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Trading Mine->Content",
|
||||
"updated": 1609945984960
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Trading Engine",
|
||||
"updated": 1609945113032
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Trading Engine->Definition",
|
||||
"updated": 1609945998216
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Trading Engine->Content",
|
||||
"updated": 1609946001567
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Data Mine",
|
||||
"updated": 1609945134789
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Data Mine->Definition",
|
||||
"updated": 1609946022992
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Data Mine->Content",
|
||||
"updated": 1609946026584
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Plugins",
|
||||
"updated": 1609945527199
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Plugins->Definition",
|
||||
"updated": 1609946038957
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Plugins->Content",
|
||||
"updated": 1609946042538
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Tutorial",
|
||||
"updated": 1609946064589
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Tutorial->Definition",
|
||||
"updated": 1609946067573
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Tutorial->Content",
|
||||
"updated": 1609946070683
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Super Scripts",
|
||||
"updated": 1609945544452
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Super Scripts->Definition",
|
||||
"updated": 1609946084954
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Node->Super Scripts->Content",
|
||||
"updated": 1609946088312
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,55 +0,0 @@
|
||||
{
|
||||
"topic": "Introduction",
|
||||
"pageNumber": "4",
|
||||
"type": "Workflows",
|
||||
"definition": {
|
||||
"text": "Your preferred workflow will emerge from the understanding of how Superalgos administers the complexity of multiple concepts that make up trading intelligence.",
|
||||
"updated": 1609946305313
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Superalgos features multiple intertwining workflows, each with multiple ramifications and variations. Use cases for a trading automation platform like Superalgos abound and are probably impossible to extricate from one another:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Users may download data from multiple exchanges and multiple markets."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "They may process data using existing indicators, modify those indicators, or create their own technical studies with varying degrees of complexity."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "They may use simple charts or may configure complex charts superimposing information from different markets and different exchanges."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "They may use and modify existing trading systems or create their own, both with or without coding."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "They may trade in a fully automated fashion, use the system for backtesting, or for generating signals from paper trading sessions."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "They may run minimalistic, home-sized trading operations or deploy industrial-grade trading farms."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "They may operate in a single market or leverage multiple exchanges and markets with a complex web of trading systems."
|
||||
},
|
||||
{
|
||||
"style": "Callout",
|
||||
"text": "All of these use cases and the infinite permutations that may result from combining each dimension of use in varying measures may as well produce infinite workflows."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The best approach to start developing your workflow is to build up your understanding of how the system is structured, and—in particular—how information is made available to each of the components of the system."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "As a rule of thumb, one of the foremost system design criteria for Superalgos is flexibility. The system should impose no constraints and let your imagination and hardware resources set the limits of what you may or may not do."
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,93 +0,0 @@
|
||||
{
|
||||
"topic": "Introduction",
|
||||
"pageNumber": "5",
|
||||
"type": "Workspace",
|
||||
"definition": {
|
||||
"text": "A workspace is an entity storing all system and user-generated information, excluding the state and contents of plugins. In technical terms, a workspace is a JSON file.",
|
||||
"updated": 1609946727314
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "A workspace stores information about:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Any hierarchy that is not included as a plugin."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Nodes that may be floating around, detached from hierarchies."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Information regarding the physical position and state of all nodes within the design space, even those detached from the hierarchies."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "A workspace is not part of any of the hierarchies; instead, it contains them."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Working With Workspaces"
|
||||
},
|
||||
{
|
||||
"style": "Subtitle",
|
||||
"text": "Saving Workspaces"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Workspaces are saved as .json files in the My-Workspaces folder."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "They are saved automatically every 60 seconds, or at the moment the browser or browser tab is closed. You may also save it manually using the following hot-key combination: Ctrl or ⌘ + Shift + S."
|
||||
},
|
||||
{
|
||||
"style": "Success",
|
||||
"text": " Backing up a workspace downloads the same file to your local Downloads folder. This is a good way to store old versions in case you ever need to go back to a previous state of affairs.",
|
||||
"updated": 1609946808755
|
||||
},
|
||||
{
|
||||
"style": "Important",
|
||||
"text": " Plugin workspaces may not be modified. When you load a plugin workspace, a new file is created in your My-Workspaces folder as soon as the workspace is saved for the first time, resulting in a copy of the plugin workspace. Any modifications you introduce in the workspace are stored in the copy, not the original plugin.",
|
||||
"updated": 1609946816684
|
||||
},
|
||||
{
|
||||
"style": "Subtitle",
|
||||
"text": "Creating Workspaces"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "To create a new workspace, rename any of the existing workspaces by changing the label of the workspace node, and save it as explained above. After you change the label and once the workspace is saved (by any of the usual means), a new file is stored in the My-Workspaces folder."
|
||||
},
|
||||
{
|
||||
"style": "Subtitle",
|
||||
"text": "Loading Workspaces"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Users may manage multiple workspaces, but only one workspace may be loaded in the system at any point."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "To load a workspace, click the workspaces tab on the left-hand side of the screen and select one of the available files."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "To load a workspace you got from a third party, you may place the file in the My-Workspaces folder so that you may open it from the workspaces tab, or you may drag it and drop it on the design space."
|
||||
},
|
||||
{
|
||||
"style": "Subtitle",
|
||||
"text": "Deleting Workspaces"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "To delete a workspace, delete the corresponding workspace file from within the file system application of your operating system."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
-50
@@ -1,50 +0,0 @@
|
||||
{
|
||||
"topic": "Introduction",
|
||||
"pageNumber": "6",
|
||||
"type": "Nodes and Structures of Nodes",
|
||||
"definition": {
|
||||
"text": "A node is a small data structure containing information that may be related to market information, trading intelligence, the operation of the system, or other concepts. They are visually represented by icons in the design space.",
|
||||
"updated": 1609946951589
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Structure of Nodes",
|
||||
"updated": 1609946982728
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "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."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "As a consequence, structures of nodes are hierarchical structures, and a logical representation of how the concepts embodied by each node relate to each other."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Parent-Offspring Relationships"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "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."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The direction of the relationship is determined, in most cases, by the ability of a node to produce the offspring node. That is, the parent node is the one which, by software design, may produce the offspring node."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How to Detach and Attach Nodes"
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Topic->Detach and Attach Nodes->Definition",
|
||||
"updated": 1609948512326
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Topic->Detach and Attach Nodes->Content",
|
||||
"updated": 1609948536788
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,71 +0,0 @@
|
||||
{
|
||||
"topic": "Introduction",
|
||||
"pageNumber": "7",
|
||||
"type": "References",
|
||||
"definition": {
|
||||
"text": "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.",
|
||||
"updated": 1609950165954
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Direction",
|
||||
"updated": 1609950210690
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "References have a direction property relative to each of the nodes involved in the reference: the node establishing the reference sets an outgoing reference, while the one accepting the reference sets an incoming reference."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "For example, a session establishes an outgoing reference with a trading system. This allows the session to access the information within the whole trading system hierarchy, including strategies. At the trading system level, the same reference is viewed as an incoming reference."
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "Scope"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "A reference established between nodes of any particular structure within a hierarchy is said to be an internal reference relative to the said structure of nodes. Similarly, a reference established with a node outside of the said structure, that is, in a different part of the hierarchy or in another hierarchy, is said to be an external reference."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Examples of internal references may be found in the data mine and crypto ecosystem hierarchies. For example, let’s briefly look into one such case within a plotter module:"
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The capture below shows the shapes node and several offspring nodes: on one hand, several polygons; on the other hand, the chart points node."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Notice that vertices under each polygon reference to points under the chart points node."
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "This means that the node shapes feature several internal references."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": " The backup, clone and share operations make different uses of the properties of references. We will cover the three of them extensively so that you may make the most of these features.",
|
||||
"updated": 1609950276151
|
||||
},
|
||||
{
|
||||
"style": "Title",
|
||||
"text": "How to Estabish and Remove References",
|
||||
"updated": 1609950438203
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Topic->Establish and Remove References->Definition"
|
||||
},
|
||||
{
|
||||
"style": "Include",
|
||||
"text": "Superalgos->Topic->Establish and Remove References->Content",
|
||||
"updated": 1609950361692
|
||||
},
|
||||
{
|
||||
"style": "Text",
|
||||
"text": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -100,8 +100,8 @@ function newSuperalgosUtilitiesDocs() {
|
||||
function reverseParseGIF(HTML) {
|
||||
let result = HTML
|
||||
result = result.replace(' <img class="docs-gif" src="', '')
|
||||
result = result.replace('"> ', '')
|
||||
return result
|
||||
result = result.replace('">', '')
|
||||
return result.trim()
|
||||
}
|
||||
|
||||
function parsePNG(text) {
|
||||
@@ -111,8 +111,8 @@ function newSuperalgosUtilitiesDocs() {
|
||||
function reverseParsePNG(HTML) {
|
||||
let result = HTML
|
||||
result = result.replace(' <img class="docs-png" src="', '')
|
||||
result = result.replace('"> ', '')
|
||||
return result
|
||||
result = result.replace('">', '')
|
||||
return result.trim()
|
||||
}
|
||||
|
||||
function parseTable(text) {
|
||||
@@ -194,14 +194,6 @@ function newSuperalgosUtilitiesDocs() {
|
||||
return HTML
|
||||
}
|
||||
|
||||
function parseChapter(text) {
|
||||
let HTML = ''
|
||||
let splittedText = text.split('->')
|
||||
if (splittedText.length < 1) { return }
|
||||
HTML = '<a params="' + text + '" onClick="UI.projects.superalgos.spaces.docsSpace.navigateTo(\'' + splittedText[0] + '\', \'Topic\', \'' + splittedText[1] + '\')" class="docs-chapter-link">' + splittedText[1] + '</a>'
|
||||
return HTML
|
||||
}
|
||||
|
||||
function parseYoutube(text) {
|
||||
let HTML = ''
|
||||
|
||||
@@ -232,7 +224,7 @@ function newSuperalgosUtilitiesDocs() {
|
||||
|
||||
/* Single occurrance replacements */
|
||||
text = text.replace('<table class="docs-info-table"> ', '')
|
||||
text = text.replace(' </table>', '')
|
||||
text = text.replace('</table>', '')
|
||||
text = text.replace('<thead>', '')
|
||||
text = text.replace('</thead>', '')
|
||||
text = text.replace('<tbody>', '')
|
||||
@@ -251,13 +243,13 @@ function newSuperalgosUtilitiesDocs() {
|
||||
|
||||
/* We break lines where needed */
|
||||
text = text.replaceAll('||', '|' + String.fromCharCode(10) + '|')
|
||||
return text
|
||||
return text.trim()
|
||||
|
||||
function removeRGB(HTML) {
|
||||
let text = HTML
|
||||
text = text.replaceAll('<div style="display: block; background: ', '')
|
||||
text = text.replaceAll('; border: 1px solid black;"> </div>', '')
|
||||
return text
|
||||
return text.trim()
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in new issue
Block a user