Appears to have unintended results when used with oscillators (like ROC) that have negative numbers. Below is a simple example you can input and see.
Rename
Just to drop the air of mystery from your post, is the unintended result that the exit keeps getting triggered while the indicator remains negative w/o a change?
1% greater than -10 is -10.1. That's correct, so it's just a mistake to use a rule like that with an oscillator. The result won't be what you intended.
Just switch to Indicator Compare to Indicator for 1 bar ago.
If you really want %, and since TrendScore oscillates between -10 and 10, you could also use the MathIndOpValue indicator to add 10 (or more) to TrendScore.
Just switch to Indicator Compare to Indicator for 1 bar ago.
If you really want %, and since TrendScore oscillates between -10 and 10, you could also use the MathIndOpValue indicator to add 10 (or more) to TrendScore.
Cone,
Dont respond to any post I make,
Did you really state -10.1 > -10.0. You really dont care about your product or your customers.
1% > +10 = +10.1
1% > -10 = -9.9
The only mistake I have made is thinking you may want to be helpful and look at a plausible logic error where an absolute value could be used in an indicator to make it better for everyone.
Eugene,
When below 0 signals blink (enter and exit). Look at where trendscore is at -10 and erroneously enters and then exits, repeats. Block for entry requires Trendscore be greater than the bar before by stated %, but it enters anyway. Then immediately exits.
Yes there are workarounds by adding and or other math on indicators. I've done so in the past.
The main reason Ive done many workarounds in the past is due to this response. I refrain from asking questions here because often the first and or only response is either not helpful, rude, or self centered or defensive around the responder. Unprofessional.
UNHAPPY CUSTOMER.
Dont respond to any post I make,
Did you really state -10.1 > -10.0. You really dont care about your product or your customers.
1% > +10 = +10.1
1% > -10 = -9.9
The only mistake I have made is thinking you may want to be helpful and look at a plausible logic error where an absolute value could be used in an indicator to make it better for everyone.
Eugene,
When below 0 signals blink (enter and exit). Look at where trendscore is at -10 and erroneously enters and then exits, repeats. Block for entry requires Trendscore be greater than the bar before by stated %, but it enters anyway. Then immediately exits.
Yes there are workarounds by adding and or other math on indicators. I've done so in the past.
The main reason Ive done many workarounds in the past is due to this response. I refrain from asking questions here because often the first and or only response is either not helpful, rude, or self centered or defensive around the responder. Unprofessional.
UNHAPPY CUSTOMER.
I see this isn't working properly for negative values, will work on it for the next release.
QUOTE:Both unfair and uncalled for. I gave you 2 solutions that you could use right now. But so be it, I will be delighted not help you.
Dont respond to any post I make,
Since we're talking about negative numbers, -10.1 is a greater negative number than -10.0.
You guys can fight over your perspective. Here's what AI says about that -
Again, totally uncalled for. Where's that shrugman icon?
🤷♂️
The Block is not even saying greater than/less than, it's saying "above" or "below", as in above or below on the chart. But no matter how you look at it, it should not be triggering signals when both the current value and previous values are -100. I've got it in my work queue.
We have it corrected for the next build, appreciate the report!
Your Response
Post
Edit Post
Login is required