You're right and with these as basis, its coded for a "the classless, non-interchangeable concept," the same method met by different hypothesis means, mine coded to access data for one on the ground (targeting) and using the other above looking down, targeting solid. And agreed, "stacking too many overlapping or conceptually similar indicators in the name of confluence can be harmful, so that any hesitation" to me is good. So mine seems more like a burrito and yours a taco?Awesome - They are not actually the same class of indicator. They only look similar because both are smoothed and recursive.
This script is full of hidden constants:
Those will behave very differently between:
- 0.35
- heartbeatSeconds
- heartbeatLookback
- entropyLength
The Z-score engine answers the question "Are we stretched relative to today’s behavior and did momentum turn?” This new engine answers “Are we near a detected cycle swing and is the market orderly?” Those are different trading philosophies. They solve different problems. The z-score is designed to detect abnormal price location; (how far pressure is away from normal operating range and is it stretched). The other engine is designed to detect swing phase in a cyclical process, (what part of the rotation cycle you are in, and how chaotic the flow is.). Those are not interchangeable concepts, nor would I use them together. They could signal in the same areas but mean different things. In a broad sense, the Z is a trigger/timing layer (not to be used alone) and the other Environment / regime / swing suitability layer. In other words, one is on the ground the other high above looking down.
- SPX
- TSLA
- futures
The new script is best for range trading, swing turning points and rhythm / oscillatory markets.
Not to be argumentative, but for newer and intermediate traders, one of the biggest challenges in technical analysis is learning that indicators which look similar on a chart often solve very different problems under the hood.
It’s easy to assume two tools are interchangeable simply because both “turn up and down” or plot stretch-like patterns.
As @useThinkScript , @merryDay , and others have pointed out many times, stacking too many overlapping or conceptually similar indicators in the name of confluence can actually be harmful.
Instead of improving decision quality, it often creates conflicting signals and leads to hesitation, paralysis by analysis, and missed executions.
Understanding what a tool is designed to measure, not just what it visually resembles; is far more important than how many indicators agree on a bar.
I have talked too much, and I do like the script and I think you need to continue to add to the database of good scripts for sure!!!!
Instead of improving decision quality, just take a trade and even though it often creates conflicting signals and leads to hesitation, most takes are profitable. A taco is like a burrito almost.
A Theory that runs parallel with the A_LethEffectGreekRiver_02 lower indicator.
z-score is not relative to me right now, I will put some time into reviewing that, thanks.