doc updated
This commit is contained in:
Luis Fernando Molina committed
1 parent
3156e2c680
commit
4cc57408ee
12 files changed
+118
-68
No files matched your search
File renamed without changes.
@@ -60,6 +60,10 @@ entries:
|
||||
url: /suite-step-4.html
|
||||
output: web
|
||||
|
||||
- title: "Step 5: Import a workspace"
|
||||
url: /suite-step-5.html
|
||||
output: web
|
||||
|
||||
# - title: Run your first backtest
|
||||
# url: /suite-run-your-first-backtest.html
|
||||
# output: web
|
||||
@@ -95,7 +99,7 @@ entries:
|
||||
folderitems:
|
||||
|
||||
- title: Fundamental concepts
|
||||
url: /suite-fundamental-concepts.html
|
||||
url: /suite-fundamental-design-space-concepts.html
|
||||
output: web
|
||||
|
||||
- title: Interface
|
||||
@@ -110,6 +114,10 @@ entries:
|
||||
output: web
|
||||
folderitems:
|
||||
|
||||
- title: Fundamental concepts
|
||||
url: /suite-fundamental-charting-space-concepts.html
|
||||
output: web
|
||||
|
||||
- title: Interface
|
||||
url: /suite-charting-space-interface.html
|
||||
output: web
|
||||
@@ -225,8 +233,8 @@ entries:
|
||||
output: web
|
||||
folderitems:
|
||||
|
||||
- title: How bots work
|
||||
url: /suite-how-bots-work.html
|
||||
- title: Fundamental concepts
|
||||
url: /suite-fundamental-infrastructure-concepts.html
|
||||
output: web
|
||||
|
||||
- title: Crypto ecosystem
|
||||
@@ -420,25 +428,25 @@ entries:
|
||||
url: /suite-upgrading-your-existing-instalation.html
|
||||
output: web
|
||||
|
||||
# - title: My system gets slow
|
||||
# url: /suite-my-system-gets-slow.html
|
||||
# output: web
|
||||
- title: My system gets slow
|
||||
url: /suite-my-system-gets-slow.html
|
||||
output: web
|
||||
|
||||
# - title: On-screen errors and warnings
|
||||
# url: /suite-on-screen-errors-and-warnings.html
|
||||
# output: web
|
||||
- title: On-screen errors and warnings
|
||||
url: /suite-on-screen-errors-and-warnings.html
|
||||
output: web
|
||||
|
||||
# - title: Market data seems to be outdated
|
||||
# url: /suite-market-data-indicators-seem-to-be-outdated.html
|
||||
# output: web
|
||||
- title: Market data seems to be outdated
|
||||
url: /suite-market-data-indicators-seem-to-be-outdated.html
|
||||
output: web
|
||||
|
||||
# - title: Reporting bugs
|
||||
# url: /suite-reporting-bugs.html
|
||||
# output: web
|
||||
- title: Reporting bugs
|
||||
url: /suite-reporting-bugs.html
|
||||
output: web
|
||||
|
||||
# - title: Consulting logs
|
||||
# url: /suite-consulting-logs.html
|
||||
# output: web
|
||||
- title: Consulting logs
|
||||
url: /suite-consulting-logs.html
|
||||
output: web
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -51,8 +51,6 @@
|
||||
|
||||
<!--------------------------------------------- CONTENT starts -->
|
||||
|
||||
Conceptually, Superalgos places the focus on the visual experience. Not just because it's *nice* to see data in a graphical representation, but because our analysis capabillities expand when we incorporate senses in the mix. Human's capacity to think abstractly may be more or less developed across individuals, but one thing is clear: our thought process benefits from being able to see.
|
||||
|
||||
Think of the charting space as a huge drawing board. You may have lots of information plotted on different parts of the space and use a viewport to look into that space.
|
||||
|
||||
There is only one charting space hierarchy, thus all charts are configured here. As is common throughout the system, different concepts and elements of the charts such as scales, data layers and so on, are represented by nodes in the hierarchy. The system allows great flexibility on how to visualize information over the charts by adding, configuring, and arranging these nodes.
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
---
|
||||
title: Consulting Logs
|
||||
summary: ""
|
||||
summary: "Log files are available in a format that should be understandable to most technically-oriented people."
|
||||
sidebar: suite_sidebar
|
||||
permalink: suite-consulting-logs.html
|
||||
---
|
||||
|
||||
If you are a technical person, you may be interested in consuting the logs of the different bots that run in the system.
|
||||
If you are a technical person, you may be interested in consulting the logs of the different bots that run in the system.
|
||||
|
||||
Each bot keeps its own set of execution log files, stored under a similar folder structure as bot's Output and Reports. The difference is that the Log-Files folder is at the root level of the release folder, instead of being inside Data-Storage:
|
||||
|
||||
```
|
||||
\Log-Files\AAMasters\AAMasters
|
||||
\Log-Files\AAMasters\
|
||||
```
|
||||
Log files contain detailed information about each execution of the bot. As such, a new folder is created for each execution, labeled with the exact DateTime.
|
||||
|
||||
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: Fundamental Charting Space Concepts
|
||||
summary: "The charting space provides great control over how information generated on other hierarchies is visualized."
|
||||
sidebar: suite_sidebar
|
||||
permalink: suite-fundamental-charting-space-concepts.html
|
||||
---
|
||||
|
||||
Conceptually, Superalgos places the focus on the visual experience. Not just because it's *nice* to see data in a graphical representation, but because our analysis capabilities are extended when we incorporate senses in the mix. Human's capacity to think abstractly may be more or less developed across individuals, but one thing is clear: our thought process benefits from being able to see.
|
||||
|
||||
The <a data-toggle="tooltip" data-original-title="{{site.data.charting_space.charting_space}}">charting space</a> is conceived to provide an unprecedented level of flexibility and control over the way information is displayed graphically. Everything that you see in the form of charts when you pull the slider down is configured in the charting space hierarchy while using the information available in other <a data-toggle="tooltip" data-original-title="{{site.data.concepts.hierarchy}}">hierarchies</a>.
|
||||
|
||||
In other words, you use the charting space hierarchy to create <a data-toggle="tooltip" data-original-title="{{site.data.charting_space.time_machine}}">time machines</a> and <a data-toggle="tooltip" data-original-title="{{site.data.charting_space.timeline_chart}}">timeline charts</a>, and to configure their scales and so on, but the information feeding those charts come from <a data-toggle="tooltip" data-original-title="{{site.data.concepts.bot}}">bots</a> running on the <a data-toggle="tooltip" data-original-title="{{site.data.network.network}}">network</a> hierarchy. Those bots obtain exchange and market information from the <a data-toggle="tooltip" data-original-title="{{site.data.crypto_ecosystem.crypto_ecosystem}}">crypto ecosystem</a> hierarchy via <a data-toggle="tooltip" data-original-title="{{site.data.concepts.reference}}">references</a>, and their source code is defined in <a data-toggle="tooltip" data-original-title="{{site.data.data_mine.data_mine}}">data mines</a>.
|
||||
|
||||
The above means that, in order to have information to visualize, you will first need to run <a data-toggle="tooltip" data-original-title="{{site.data.concepts.sensor_bot}}">sensor</a> and <a data-toggle="tooltip" data-original-title="{{site.data.concepts.indicator_bot}}">indicator</a> bots. We call that <a data-toggle="tooltip" data-original-title="{{site.data.network.data_mining}}">data mining</a>, and it's done from the data mining section of the network hierarchy.
|
||||
|
||||
The <a data-toggle="tooltip" data-original-title="{{site.data.concepts.workpace}}">workspace</a> shipping with the system features an extensive configuration of exchanges, markets, and charts that you may start using right away. To configure your own charts, you will need to learn the basics of the charting space, and that is exactly the information covered on these pages.
|
||||
+6
-4
@@ -1,13 +1,15 @@
|
||||
---
|
||||
title: "Fundamental Concepts"
|
||||
title: "Fundamental Design Space Concepts"
|
||||
summary: "The design space controlling the workspace, nodes, structures of nodes, and their parent-offspring relationships are the overarching concepts arranging all information handled by the system."
|
||||
sidebar: suite_sidebar
|
||||
permalink: suite-fundamental-concepts.html
|
||||
permalink: suite-fundamental-design-space-concepts.html
|
||||
---
|
||||
|
||||
Superalgos handles numerous concepts encompassing fields such as market information, trading strategies, visualization features, workflows, infrastructure, technical resources, and many more. Superalgos structures these concepts in an attempt to make their use intuitive.
|
||||
Trading intelligence emerges from the effective use of information, strategies, technical resources, visualization tools, infrastructure, workflows, collaboration, and several other concepts.
|
||||
|
||||
However, each of the above are complex subjects in their own merit. Therefore, it is necessary to acquire a basic level of understanding of the Superalgos paradigm for the desired intuition to emerge. Understanding the following concepts is a first step in that direction.
|
||||
Superalgos structures these concepts in an attempt to make their use intuitive and efficient. However, each of the above are complex subjects in their own merit. The quest for the effective use of several complex concepts is titanic.
|
||||
|
||||
Therefore, it is necessary to acquire a basic level of understanding of the Superalgos paradigm for the desired intuition to emerge. Understanding the following concepts is a first step in that direction.
|
||||
|
||||
## Design Space
|
||||
|
||||
+6
-12
@@ -1,17 +1,11 @@
|
||||
---
|
||||
title: How Bots Work
|
||||
title: Fundamental Infrastructure Concepts
|
||||
summary: "There are three types of bots required to process data, and to trade: sensors bots, indicators bots, and the trading bot. Their definitions and the information required to operate them are scattered on all five hierarchies."
|
||||
sidebar: suite_sidebar
|
||||
permalink: suite-how-bots-work.html
|
||||
permalink: suite-fundamental-infrastructure-concepts.html
|
||||
---
|
||||
|
||||
{% include /data_mine/sensor-bot.md heading="" icon="" adding="" configuring="" starting="" content="no" definition="yes" table="yes" more="no" %}
|
||||
|
||||
{% include /data_mine/indicator-bot.md heading="" icon="" adding="" configuring="" starting="" content="no" definition="yes" table="yes" more="no" %}
|
||||
|
||||
{% include /data_mine/trading-bot.md heading="" icon="" adding="" configuring="" starting="" content="no" definition="yes" table="yes" more="no" %}
|
||||
|
||||
Bots are defined in <a data-toggle="tooltip" data-original-title="{{site.data.data_mine.data_mine}}">data mines</a>. That is, data mines hold the source code and configuration—the complete set of definitions—of the three existing kinds of bots.
|
||||
<a data-toggle="tooltip" data-original-title="{{site.data.concepts.bot}}">Bots</a> are defined in <a data-toggle="tooltip" data-original-title="{{site.data.data_mine.data_mine}}">data mines</a>. That is, data mines hold the source code and configuration—the complete set of definitions—of the three existing kinds of bots: <a data-toggle="tooltip" data-original-title="{{site.data.concepts.sensor_bot}}">sensors</a>, <a data-toggle="tooltip" data-original-title="{{site.data.concepts.indicator_bot}}">indicators</a>, and the <a data-toggle="tooltip" data-original-title="{{site.data.concepts.trading_bot}}">trading bot</a>.
|
||||
|
||||
Using any of these bots entails creating an instance of the bot definition, so that this instance may run the bot's code. This is done from within the <a data-toggle="tooltip" data-original-title="{{site.data.network.network}}">network</a> hierarchy.
|
||||
|
||||
@@ -19,17 +13,17 @@ A bot instance is a reference to a bot as defined in a data mine. The instance o
|
||||
|
||||
You use <a data-toggle="tooltip" data-original-title="{{site.data.network.task_manager}}">task managers</a> and <a data-toggle="tooltip" data-original-title="{{site.data.network.task}}">tasks</a> within the network hierarchy 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.
|
||||
|
||||
Upon execution, bot instances run in a branched sequence determined by their <a data-toggle="tooltip" data-original-title="{{site.data.data_mine.status_dependency}}">status</a> and <a data-toggle="tooltip" data-original-title="{{site.data.data_mine.data_dependency}}">data dependencies</a>. For instance, if bot Alice depends on the data produced by bot Bob, then Alice will be configured to run as soon as Bob finishes its execution. These configurations are all set up for existing bots in the corresponding data mine, so you only need to worry about this if your create new bots.
|
||||
Upon execution, bot instances run in a branched sequence determined by their <a data-toggle="tooltip" data-original-title="{{site.data.data_mine.status_dependency}}">status</a> and <a data-toggle="tooltip" data-original-title="{{site.data.data_mine.data_dependency}}">data dependencies</a>. 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 for all existing bots, in the corresponding data mine. Therefore, you only need to worry about this if you create new bots.
|
||||
|
||||
What you do need to understand 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.
|
||||
|
||||
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 is that bots are prepared to receive virtually live data and process it online.
|
||||
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.
|
||||
|
||||
Bots need to know which <a data-toggle="tooltip" data-original-title="{{site.data.crypto_ecosystem.market}}">market</a> of which <a data-toggle="tooltip" data-original-title="{{site.data.crypto_ecosystem.crypto_exchange}}">exchange</a> they should work with. Exchanges and markets are defined in the <a data-toggle="tooltip" data-original-title="{{site.data.crypto_ecosystem.crypto_ecosystem}}">crypto ecosystem</a> hierarchy. Bots obtain that information by establishing <a data-toggle="tooltip" data-original-title="{{site.data.concepts.reference}}">references</a> with the appropriate markets in that hierarchy.
|
||||
|
||||
In the case of the trading bot, it also needs to know which type of <a data-toggle="tooltip" data-original-title="{{site.data.concepts.session}}">trading session</a> it should run, and what <a data-toggle="tooltip" data-original-title="{{site.data.trading_system.trading_system}}">trading system's</a> rules it should follow. For those reasons, trading bots are paired with a specific session, which in turn, references a trading system.
|
||||
|
||||
{% include note.html content="The information covered *en passant* in this page is explained in detail throughout these * infrastructure* pages." %}
|
||||
{% include note.html content="The information covered *en passant* on this page is explained in detail throughout these infrastructure pages." %}
|
||||
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Market Data or Indicators Seem to be Outdated
|
||||
summary: ""
|
||||
summary: "For data to be up to date, the Masters Datasets and Sparta Indicators tasks need to be running."
|
||||
sidebar: suite_sidebar
|
||||
permalink: suite-market-data-indicators-seem-to-be-outdated.html
|
||||
---
|
||||
|
||||
If you are running the system for the first time or you stopped running the system for some time, data will not be up to date. Every time you start the system, it will take some time for data to catch up with the present time.
|
||||
|
||||
To update your datasets until the present time you need to *Run All Tasks* in your *Masters Datasets* task manager, and allow enough time for the processes to go through the missing data.
|
||||
To update your datasets until the present time you need to *Run All Tasks* in your *Masters Datasets* task manager, and allow enough time for the processes to go through the missing data. If you are using the indicators provided by the Sparta data mine, you should start those tasks as well.
|
||||
|
||||
[](https://user-images.githubusercontent.com/13994516/67281294-5b60f800-f4cf-11e9-8f22-27655ec9e2a6.gif)
|
||||
@@ -1,25 +1,27 @@
|
||||
---
|
||||
title: My System Gets Slow
|
||||
summary: ""
|
||||
summary: "Understand how the system uses the available hardware so that you may implement workarounds and best practices."
|
||||
sidebar: suite_sidebar
|
||||
permalink: suite-my-system-gets-slow.html
|
||||
---
|
||||
|
||||
Dynamically rendering all the visual features we use on the system tends to put a significant load on the machine's processor. Depending on your machine's capacity, this may result in the system getting slow and sometimes even unresponsive.
|
||||
Dynamically rendering all the visual features in the system puts a significant load on the machine's graphics processing unit (GPU). Running multiple tasks at the same time is demanding on the central processing unit (CPU). Depending on your machine's capacity, this may result in the system getting slow and sometimes even unresponsive.
|
||||
|
||||
If you experience such symptoms, there are several workarounds you may implement to mitigate them:
|
||||
If you experience such symptoms, there are several workarounds you may implement to mitigate them.
|
||||
|
||||
{% include note.html content="Learn about the [system requirements](suite-system-requirements.html) to better understand what to expect in terms of the performance of your hardware." %}
|
||||
|
||||
## Display Less Data on the Charts
|
||||
|
||||
If you are zooming out too far in the horizontal time scale with too many candles on the screen, try zooming-in a bit or changing time frames so that candle density decreases.
|
||||
|
||||
You may also want to switch off the layers you may not be using. Remember, every piece of graphical information you see on screen represents data your system is reading from your disk and processing to display in a visual environment.
|
||||
You may also want to switch off the layers you may not be using. Remember, every piece of graphical information you see on the screen represents data your system is reading from your disk and processing to display in a graphical form.
|
||||
|
||||
## Close Unused Hierarchies
|
||||
|
||||
The physics that govern nodes in the design space help the hierarchical structure of information to self-organize. This comes at a cost in terms of processing power.
|
||||
The physics that govern nodes in the design space help structures of nodes to self-organize. This comes at a cost in terms of GPU processing power.
|
||||
|
||||
Make sure the two exiting team hierarchies are closed:
|
||||
Make sure the two exiting data mine hierarchies are closed:
|
||||
|
||||
* Hit <kbd>Ctrl or ⌘</kbd> + <kbd>Alt</kbd> + <kbd>M</kbd> (*M* for *Masters*) to go the the Masters team hierarchy and click  if the hierarchy is open.
|
||||
|
||||
@@ -27,14 +29,14 @@ Make sure the two exiting team hierarchies are closed:
|
||||
|
||||
* Hit <kbd>Ctrl or ⌘</kbd> + <kbd>Alt</kbd> + <kbd>M</kbd> (*N* for *Network*) to go the the Network hierarchy and click  if the hierarchy is open.
|
||||
|
||||
You may also want to close any of the structure of nodes in your trading system that you may not be using.
|
||||
You may also want to close any of the structures of nodes that you may not be using in the trading system.
|
||||
|
||||
## Freeze the Nodes You Need to Remain Visible
|
||||
|
||||
| Definition | Freeze |
|
||||
| :---: | :---: |
|
||||
|  |  |
|
||||
You will find that freezing the nodes that you need to remain visible contributes to reducing the load in your GPU.
|
||||
|
||||
You will find that freezing the nodes that you need to remain visible contributes to reducing the load in your CPU.
|
||||
## Stop Tasks That You May Not Need to Run at All Times
|
||||
|
||||
> **NOTE:** If these workarounds do not solve your problem and you often experience slowness or unresponsiveness when using your computer, you may want to consider upgrading your equipment. You shouldn't risk your capital with an insufficient trading infrastructure.
|
||||
Data mining is a CPU-intensive activity. If you are designing a strategy, you probably don't need to have a live stream of information being processed in realtime. Learn to segment your activities and only start the tasks that you need for the work you are doing.
|
||||
|
||||
{% include important.html content="If these workarounds do not solve your problem and you often experience slowness or unresponsiveness when using your computer, you may want to consider upgrading your equipment. You shouldn't risk your capital with an insufficient trading infrastructure." %}
|
||||
@@ -1,14 +1,14 @@
|
||||
---
|
||||
title: On-Screen Errors and Warnings
|
||||
summary: ""
|
||||
summary: "When working on a strategy, errors in the syntax of conditions and formulas are signaled at the offending node."
|
||||
sidebar: suite_sidebar
|
||||
permalink: suite-on-screen-errors-and-warnings.html
|
||||
---
|
||||
|
||||
It may happen that your simulation or live trading is not working as expected. The first thing to do in such a case is to turn on the *Formulas & Conditions* layer of the corresponding session and look around within your workspace. Errors are signaled with a red circle surrounding the relevant node of the workspace. Hover the mouse pointer over the node and you should get a description of what is that is causing the unexpected behavior.
|
||||
It may happen that your simulation, live trading, or anything else you may be doing is not working as expected. The first thing to do in such a case is to turn on the *Formulas & Conditions* layer of the corresponding session and look around within your workspace. Errors are signaled with a red circle surrounding the relevant node of the workspace. Hover the mouse pointer over the node and you should get a description of what is that is causing the unexpected behavior.
|
||||
|
||||
[](https://user-images.githubusercontent.com/13994516/63213696-b52ff500-c10f-11e9-9bc1-741ecb0858ef.gif)
|
||||
|
||||
Bear in mind that when the split tab is fully closed, errors will no longer show up in the design space, as shown in the below video:
|
||||
Bear in mind that when the slider is fully closed, errors will no longer show up in the design space, as shown in the below video:
|
||||
|
||||
[](https://user-images.githubusercontent.com/13994516/63213579-528a2980-c10e-11e9-8464-76cb4b369db4.gif)
|
||||
@@ -1,28 +1,42 @@
|
||||
---
|
||||
title: Reporting Bugs
|
||||
summary: ""
|
||||
summary: "It is of the utmost importance for developers to understand how to reproduce the issue."
|
||||
sidebar: suite_sidebar
|
||||
permalink: suite-reporting-bugs.html
|
||||
---
|
||||
|
||||
We highly appreciate bug reports. This is what you need to do:
|
||||
|
||||
**1.** Make sure you are running the latest release and that you have upgraded to the latest patch. You may find information about releases and patches on the [releases](https://github.com/Superalgos/Platform/releases) page. If you are not running the latest patch, please upgrade and test your issue again before reporting anything. We do not maintain of fix bugs on past versions.
|
||||
**1. Make sure you are running the latest release**. You may find information about releases on the <a href="https://t.me/superalgos" rel="nofollow" rel="noopener" target="_blank">Official Superalgos Telegram Announcements Channel</a>. If you are not running the latest version of the software, please upgrade and test your issue again before reporting anything. We do not maintain of fix bugs on past versions.
|
||||
|
||||
**2.** Go to the [Issues](https://github.com/Superalgos/Platform/issues) page in this repository and take a moment to search for similar existing open issues. If you find one similar to yours, you may find helpful to follow the thread and may contribute by commenting and introducing new information about the issue.
|
||||
**2. Go to the <a href="ttps://github.com/Superalgos/Superalgos/issues" rel="nofollow" rel="noopener" target="_blank">Issues</a> page** in the Superalgos repository.
|
||||
|
||||
**3.** If there are no similar issues, then open a new one. Do your best to describe the problem as thoroughly as possible.
|
||||
**3. Search for similar existing issues**. If you find one similar to yours, you may find helpful to follow the thread, and may contribute by introducing new information about the issue.
|
||||
|
||||
**Developers will be interested in knowing how to reproduce the issue in their systems, so please describe the process that leads to the issue as clearly as possible. Capturing a GIF video showing the steps that lead to the issue would be of great help!**
|
||||
**4. Open a new issue only if there are no existing similar issues**. Do your best to describe the problem as thoroughly as possible.
|
||||
|
||||
[LICEcap](https://www.cockos.com/licecap/) is a lightweight, simple system that can help you with that. If developers can reproduce the issue, half of the problem is solved already.
|
||||
{% include tip.html content="Developers will be interested in knowing how to reproduce the issue in their systems, so please describe the process that leads to the issue as clearly as possible. Capturing a GIF video showing the steps that lead to the issue would be of great help!" %}
|
||||
|
||||
If the issue happens within the browser, you may use the systems' video capture feature:
|
||||
|
||||
* Hit <kbd>Ctrl</kbd> + <kbd>F8</kbd> to capture a static PNG image.
|
||||
|
||||
* Hit <kbd>Ctrl</kbd> + <kbd>F9</kbd> to start capturing a GIF video, and hit the same key combination again to end the capture. Once the capture ends, it takes some time to process the capture and generate the final file.
|
||||
|
||||
* <kbd>Ctrl</kbd> + <kbd>F10</kbd> to start capturing a WEBM video, and hit the same key combination again to end the capture. WEBM videos are processed instantly.
|
||||
|
||||
In all three cases, the browser downloads the resulting file and makes it available in the downloads folder.
|
||||
|
||||
In case the issue does not happen at the browser, for example, if it happens at the console, <a href="https://www.cockos.com/licecap/" rel="nofollow" rel="noopener" target="_blank">LICEcap</a> is a lightweight, simple system that can help you capture GIF videos outside of Superalgos.
|
||||
|
||||
If developers can reproduce the issue, half of the problem is solved already.
|
||||
|
||||
If the issue seems to happen under specific conditions, you might want to share your _Definitions_ with developers. To do this, go to the Definitions node in your workspace and select _Share_ in the menu. A file containing your strategy and other parameters, but NOT your API keys, will download to your browser's download folder. Upload this file to the issue only if you feel comfortable with sharing it openly. If not, then wait for developers to contact you.
|
||||
If the issue seems to happen under specific conditions, you may want to share a backup of the corresponding data structures with developers. To do this, go to the concerned node and select _Share_ in the menu. A file containing the structure of nodes with no personal information downloads to your browser's download folder. Upload this file to the issue only if you feel comfortable with sharing it openly. If not, then wait for developers to contact you.
|
||||
|
||||
Please make sure you enable Github notifications when someone responds to the issue, as developers may want to ask questions.
|
||||
If the issue happens while using the system at the browser, then please include a screen capture of Chrome's Console. Open DevTools with the F12 key (when the browser is in focus) and click the Console tab, then go back and reproduce the issue. Take a screen capture of the Console and paste it along with your report.
|
||||
|
||||
If the issue happens while using the system at the browser, then please include a screen capture of Chrome's Console. Open DevTools with the F12 key (when the browser is in focus) and click the Console tab, then go back and reproduce the issue. Take a screen capture of the Console and paste it along with your report.
|
||||
Feel free to also include screen captures of the system itself if there is anything relevant you wish to show to developers.
|
||||
|
||||
Feel free to also include screen captures of the system itself if there is anything relevant you wish to show to developers.
|
||||
|
||||
[](https://user-images.githubusercontent.com/13994516/63112941-c18e4380-bf91-11e9-95e2-6fb064d5aead.png)
|
||||
[](https://user-images.githubusercontent.com/13994516/63112941-c18e4380-bf91-11e9-95e2-6fb064d5aead.png)
|
||||
|
||||
**5. Enable Github notifications when someone responds to the issue**, as developers may want to ask questions.
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: Import a workspace
|
||||
summary: Importing a workspace is a simple drag and drop operation.
|
||||
sidebar: suite_sidebar
|
||||
permalink: suite-step-5.html
|
||||
---
|
||||
|
||||
The <a data-toggle="tooltip" data-original-title="{{site.data.concepts.design_space}}">workspace</a> is a substantial concept within Superalgos. It is the entity that holds all the information handled by the system. In practical terms, it is a file that can be backed up, shared, and restored in the system.
|
||||
|
||||
For your convenience, the system ships with a default workspace containing a ready-to-use set-up.
|
||||
|
||||
**1. Locate the file ```Share - Default Workspace.json```** in the root of the ```Superalgos-master``` folder.
|
||||
|
||||
**2. Left-click on the file and drag it over the browser** where the system is running. You will notice the system recognizes your intent and pulls de slider up, showing the designer.
|
||||
|
||||
**3. Drop the workspace file on the designer** and wait for a few seconds. You should see a ring around the workspace icon, indicating the progress of the import action. Once the ring dissappears, the import operation is over an you are free to start using the system.
|
||||
Reference in new issue
Block a user