Supertrend on ATR by William210
- Indicators
- Gerard Willia G J B M Dinh Sy
- Version: 1.0
- Activations: 5
=== > What does this indicator do?
It draws a line that represents the Supertrend, based on an ATR
Choose
The ATR multiple
The ATR period
and that's all !!!
**** See screenshot 01 to 2
Do not hesitate to ask me for the iCustom code to easily integrate this SuperTrend into your own codes
=== > Example on Bitcoin
**** See screenshot 03
=== > For whom?
Whether you are a discretionary trader, algorithmic trader or developer, the indicator is designed to meet your needs. I understand the importance of reliability and efficiency when money is involved, and I take this responsibility very seriously.
The indicator consumes few resources on your PC or VPS.
For algorithmic traders and developers, I offer full access to both buffers:
buffer 1 for the SuperTrend values
buffer 2 for the orientation of the Supertrend
=== > Why?
The SuperTrend on ATR has many advantages which can certainly help you in your trading
- Clear identification of trends
- Accurate input/output signals
- Optimized risk management
- Adaptable to various instruments
- Trend confirmation with other indicators
- Simplicity and flexibility
- Tool for trading forex, stocks, commodities
-Allows you to follow trends intact for longer
-Filters fluctuations due to volatility
- Developed by a recognized French trader, Olivier Seban
=== > Development rules applied
Variable naming => All variables are named consistently and descriptively, making the code easier to understand and maintain.
Minimal use of global variables => Very few global variables are used.
Low memory consumption => The indicator is designed to consume little memory, ensuring optimal performance.
Initialization of variables => All variables are initialized, which minimizes unexpected behavior and reinforces code stability.
Loop optimization => All loops are optimized to ensure efficient traversal, thus increasing the speed of calculations.
Limitation of the number of loops=> The number of loops has been reduced by combining several treatments.
Error handling => All function returns are carefully managed to detect and handle possible errors, ensuring maximum reliability.
Limitation of log size => A procedure limits the writing of repetitive messages, thus avoiding log overload and facilitating debugging.
=== > Robust code
It is essential to have robust code that always works. In the event of a problem, clear error messages are provided. Despite these systematic checks, the indicator remains fast thanks to the optimization of data flows.