diff --git a/Projects/Superalgos/PNGs/Docs/troubleshooting/debugging-tasks.png b/Projects/Superalgos/PNGs/Docs/troubleshooting/debugging-tasks.png new file mode 100644 index 000000000..e419fe91f Binary files /dev/null and b/Projects/Superalgos/PNGs/Docs/troubleshooting/debugging-tasks.png differ diff --git a/Projects/Superalgos/Schemas/Docs-Books/user-manual.json b/Projects/Superalgos/Schemas/Docs-Books/user-manual.json index 9228a5643..5b843e811 100644 --- a/Projects/Superalgos/Schemas/Docs-Books/user-manual.json +++ b/Projects/Superalgos/Schemas/Docs-Books/user-manual.json @@ -83,6 +83,11 @@ "text": "XIV->Superalgos->Topic->Productivity Tools->This chapter discusses a collection of tools that help optimize productivity.", "updated": 1611503697142 }, + { + "style": "Chapter", + "text": "XV->Superalgos->Topic->Troubleshooting->Superalgos is a vast system and you will run into confusing situations while learning it. You must acquire the knowledge on how to analyze the issues that you may encounter. There usually is a good explanation for what is going on. This chapter helps you in that process.", + "updated": 1611649840313 + }, { "style": "Text", "text": "" diff --git a/Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-014-debugging-a-task.json b/Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-014-debugging-a-task.json new file mode 100644 index 000000000..9a85f734b --- /dev/null +++ b/Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-014-debugging-a-task.json @@ -0,0 +1,46 @@ +{ + "topic": "Troubleshooting", + "pageNumber": "14", + "type": "Debugging a Task", + "definition": { + "text": "Run the TaskManager project in your preferred IDE and use the Debug button on the task's menu.", + "updated": 1611648881024 + }, + "paragraphs": [ + { + "style": "Text", + "text": "You may debug any task, either a data mining task or a trading task by following these steps.", + "updated": 1611648894746 + }, + { + "style": "Text", + "text": "1. Run the Superalgos Client In the usual manner.", + "updated": 1611648991679 + }, + { + "style": "Text", + "text": "2. Open the TaskServer project in your preferred IDE, place a breakpoint in the part of the code you wish to debug, and run the TaskServer." + }, + { + "style": "Text", + "text": "3. Click the Debug button on the menu of the task you wish to debug. The request will be routed to the TaskServer running in your IDE." + }, + { + "style": "Png", + "text": "PNGs/Superalgos/Docs/troubleshooting/debugging-tasks.png", + "updated": 1611649086110 + }, + { + "style": "Text", + "text": "4. Run the trading session in case it is a trading task." + }, + { + "style": "Text", + "text": "After a few seconds, execution should pause in the line where you put the breakpoint. Bear in mind the system runs slower in debug mode, thus, it may take a little while for the session to start processing, after loading all dependencies." + }, + { + "style": "Text", + "text": "" + } + ] +} \ No newline at end of file diff --git a/Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-015-debugging-a-new-indicator.json b/Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-015-debugging-a-new-indicator.json new file mode 100644 index 000000000..093e86abb --- /dev/null +++ b/Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-015-debugging-a-new-indicator.json @@ -0,0 +1,61 @@ +{ + "topic": "Troubleshooting", + "pageNumber": "15", + "type": "Debugging a New Indicator", + "definition": { + "text": "A case study for developers on how to debug an indicator-in-the-making. These are a few notes taken during a real issue when building the RSI indicator.", + "updated": 1611649401081 + }, + "paragraphs": [ + { + "style": "Title", + "text": "My Indicator Is Not Running!", + "updated": 1611649414736 + }, + { + "style": "Text", + "text": "This is the logical checklist in such scenario:" + }, + { + "style": "List", + "text": "Make sure all dependencies are running." + }, + { + "style": "List", + "text": "Determine which process is not running (Multi-Period-Daily or Multi-Period-Market)." + }, + { + "style": "List", + "text": "Check if the corresponding execution started event is referencing the proper process. Make sure the referenced process is running without error, at 100%." + }, + { + "style": "List", + "text": "Check if data dependency references are in place. Make sure these dependencies are running without error, at 100%." + }, + { + "style": "List", + "text": "Stop all bots and delete the Log-Files folder so that you may easily identify current logs." + }, + { + "style": "List", + "text": "Run your indicator’s dependencies." + }, + { + "style": "List", + "text": "Make sure they are running properly, without errors. Check the logs if in doubt." + }, + { + "style": "List", + "text": "Run your indicator. Check your indicator’s log files." + }, + { + "style": "Title", + "text": "My Indicator Runs With Errors" + }, + { + "style": "Text", + "text": "You may debug an indicator by Debugging a Task, that is, the Data Task that controls the indicator.", + "updated": 1611649534218 + } + ] +} \ No newline at end of file diff --git a/Projects/Superalgos/UI/Spaces/Floating-Space/UiObjectConstructor.js b/Projects/Superalgos/UI/Spaces/Floating-Space/UiObjectConstructor.js index c3224f343..f90321a4d 100644 --- a/Projects/Superalgos/UI/Spaces/Floating-Space/UiObjectConstructor.js +++ b/Projects/Superalgos/UI/Spaces/Floating-Space/UiObjectConstructor.js @@ -264,7 +264,7 @@ function newUiObjectConstructor() { currentStatus: true, label: undefined, visible: true, - icons: ['set-node-arrangement-to-concave', 'set-node-arrangement-to-convex ', 'set-node-arrangement-to-vertical-right', 'set-node-arrangement-to-vertical-left', 'set-node-arrangement-to-horizontal-bottom', 'set-node-arrangement-to-horizontal-top'], + icons: ['set-node-arrangement-to-concave', 'set-node-arrangement-to-convex', 'set-node-arrangement-to-vertical-right', 'set-node-arrangement-to-vertical-left', 'set-node-arrangement-to-horizontal-bottom', 'set-node-arrangement-to-horizontal-top'], rawRadius: 12, targetRadius: 0, currentRadius: 0,