Login Page - Create Account

Support Board


Date/Time: Sat, 21 Sep 2024 00:57:16 +0000



Post From: GetStudyPeakValleyLine doesn't work correctly with Volume by Price studies

[2018-12-09 00:07:04]
Usermb - Posts: 126

This does make sense. It would be 0 in this case.
To be honest, I was not able to find a single case, where it is not zero. I iterate over all profiles on the chart, hundreds of different ProfileIndex values.
StartIndex is always correct, EndIndex is always zero.
Could you please let us know, when EndIdex is being set? I would really love to understand how it can be used.
UPDATE: according to the updated documentation, this is always set to zero when "extend until future intersection" for Peaks and Valleys is not used.

To claim that there are no bars for a give TPO profile instance (ProfileIndex) can potentially be misleading and not what is observed or what this function is returning. The number of bars a TPO profile appears to span across is In:2 divided by In:5 of the given TPO. Since StartIndex is set correctly, it is imho a good enough indication that it is able to deal with bars fine. I need the StartIndex to compute when a profile starts (point in time).

You know, if you don't have time to look into this kind of stuff, I do understand and I accept that the case is closed just fine, I already have work arounds for everything, but please update the documentation to reflect the reality.
UPDATE: thank you for updating the documentation, the old version I looked at is attached as proof that I didn't waste your time.

UPDATE2: TPO mystery solved. GetStudyPeakValleyLine returns EndIndex set to the start bar index of the TPO profile that the extended valley/peak would first intersect, even when the TPO is set to extend the Valleys and Peaks only to the end of the period. Thus EndIndex is pseudo-correct for TPO. To be 100% correct as per your documentation, you'd have to return zero when the Peaks and Valleys for the TPO profile are set to extend to the end of the period (and maybe window too?).
You updating the documentation made it possible to figure this out. So thanks again for that.
Date Time Of Last Edit: 2018-12-09 00:22:13
imageCapture3.PNG / V - Attached On 2018-12-09 00:03:22 UTC - Size: 35.24 KB - 349 views