Yes, indeed, other values besides 1 or 4 do not work correctly. As a feature request then, can framesync() be made to work correctly for any divisor of 24?

PlusDI() being "accumulative" indicator, it uses only 1 past value of itself in the calculation of the next, right? So, an input series of length 50 should be more than enough (even if a simple average is used in the initial calc)...

Why would it work for an input series length of 54+?

Is it influenced by UnstablePeriod=40? But UnstablePeriod "strips off initial values from the indicator", not inputs....Ignoring it will lead to "meaningfully incorrect" indicator values, but should not influence the output of the indicator function per se...

Also, "Cumulative indicators that use series - such as LowPass, DominantPeriod, UO, etc. - use LookBack as unstable period" (which is set to 1500 in my script above).


So, how does it work and what are the rules?