Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 28 Apr 2024 09:30:12 +0000
Post From: Logical comparison functions in Alerts not using full precision
| [2015-06-23 18:12:39] |
| FFTrader - Posts: 180 |
|
The Value Format that applies is for each individual main price graph or study used in the calculation.
So if you are comparing the CL price to a Moving Average value and you want a greater precision for the Moving Average, then increase the number of decimal places for the Value Format setting for the Moving Average. So you should be able to accomplish what you need in this way. Yes, I can use the above method - in theory. However, I have 2 concerns: 1. I have noticed that I cannot - or quite a tedious task in order to - determine how many digits I need in order to match a study's calculations in order to be consistent with what is being plotted. For example, the "colour change by slope" option is using full / maximum precision (as far as I can tell) and thus a study can have subtle change and the colour will change in the plot on the screen. However, in order for an alert to identify the same "colour change", it requires enough precision. The above method would mean that I have to try a precision and increase it should a precision is not reflected in a logical comparison. The task above itself would be a one time thing but it is nonetheless a disconnect between what is plotted and what is logically compared (in an alert). Currently, I use the maximum precision available to mitigate the issue. 2. Also, when I use maximum precision in the value format box, I have one less item to deal with if I put my setup on another instrument with different amount of decimals / fractions. Before I noticed this issue, I used the "inherited" option in the value format. Now, I just use the maximum precision in the value format selection box. As such, if you can have maximum precision inside the calculations AND the alerts' logical comparisons - while the value format is only limited to how many digits are displayed (on the y-scale, on chart value labels, etc.), it will be ideal. Date Time Of Last Edit: 2015-06-23 18:20:54
|