Available translations
loading results
Debugging a New Indicator
Summary: 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.
My Indicator Is Not Running!
This is the logical checklist in such scenario:
- Make sure all dependencies are running.
- Determine which process is not running (Multi-Time-Frame-Daily or Multi-Time-Frame-Market).
- Check if the corresponding execution started event is referencing the proper process. Make sure the referenced process is running without error, at 100%.
- Check if data dependency references are in place. Make sure these dependencies are running without error, at 100%.
- Stop all bots and delete the Log-Files folder so that you may easily identify current logs.
- Run your indicator’s dependencies.
- Make sure they are running properly, without errors. Check the logs if in doubt.
- Run your indicator. Check your indicator’s log files.
My Indicator Runs With Errors
You may debug an indicator by Debugging a Task, that is, the Data Task that controls the indicator.
Troubleshooting — TOC
You just read page 15 in the topic.
1. How to Troubleshoot an Issue
3. How to Upgrade Your Existing Installation
4. Initial Setup - Node is not Recognized as an Internal or External Command
5. Initial Setup - Superalgos Failed to Connect Via Websockets
6. Perception Issues - My System Gets Slow
7. Perception Issues - There Are No Candles on The Charts
8. Perception Issues - Market Data or Indicators Seem to be Outdated
9. Perception Issues - Indicator Data Seems Wrong
10. Investigating Issues - I Think I Broke Something... How Do I Start Over?
11. Investigating Issues - On-Screen Errors and Warnings
12. Investigating Issues - Check for Errors at the Browser
13. Investigating Issues - Check the Integrity of Your Data
14. Debugging a Task