66 lines
3.2 KiB
JSON
66 lines
3.2 KiB
JSON
{
|
|
"type": "Portfolio Engine",
|
|
"definition": {
|
|
"text": "The portfolio engine hierarchy is the data structure used by the portfolio bot to keep runtime information highly accessible and exposed to others.",
|
|
"translations": [
|
|
{
|
|
"language": "ES",
|
|
"text": "La jerarquia portfolio engine es la estructura de datos utilizada por el robot comercial para mantener la información en tiempo de ejecución altamente accesible y expuesta a otros.",
|
|
"updated": 1624452474129
|
|
}
|
|
]
|
|
},
|
|
"paragraphs": [
|
|
{
|
|
"style": "Block",
|
|
"text": "Content"
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "You will use this hierarchy for two main purposes:"
|
|
},
|
|
{
|
|
"style": "List",
|
|
"text": "To let your portfolio systems access the information processed by the portfolio bot. This allows strategies to keep track of and react to current and past events—including those involving the exchange, such as orders placed or filled—as the bot is running."
|
|
},
|
|
{
|
|
"style": "List",
|
|
"text": "To keep track of the actions of the portfolio bot via the design space visual environment and panels over the charts. By analyzing runtime information, you may gain a detailed understanding of what happens, when, and why, throughout a portfolio session."
|
|
},
|
|
{
|
|
"style": "Title",
|
|
"text": "Frequently Asked Questions"
|
|
},
|
|
{
|
|
"style": "Subtitle",
|
|
"text": "Can a Portfolio Engine be shared between two Portfolio Bots?"
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "The same portfolio engine can be used from multiple portfolio sessions, because it is just a node-based representation of a data structure.",
|
|
"updated": 1621987910896
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "Every time a Task is ran, a snapshot of that data structure, together with a snapshot of the Network and the Bots definitions at their Data Mine is sent from the UI to the Task Server, and from there is consumed by the running Bot. That means that a second Bot can receive the same Portfolio Engine snapshot and it will never know if other bots were fed with the same information or not.",
|
|
"updated": 1621987965915
|
|
},
|
|
{
|
|
"style": "Subtitle",
|
|
"text": "Do I need to change something at the Portfolio Engine?"
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "You don't need to physically change anything inside portfolio engine via the UI. The portfolio engine is a visual representation of the data structure that the portfolio system uses to store its values, so to speak."
|
|
},
|
|
{
|
|
"style": "Subtitle",
|
|
"text": "Can I change the values inside the Portfolio Engine?"
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "You access the Portfolio Engine from within your portfolio system if there is something in there you would like to change. This is the whole purpose of the User Defined Code node.",
|
|
"updated": 1621988418300
|
|
}
|
|
]
|
|
} |