Disliked{quote} It seems that bar lengths that exceed some pre-determined lengths need to be counted as 2, 3 or more bars, when storing the lengths of zigzags. This oversight could be why so many of us see lots of signals, when we really should not. More lengths will be pushed into a longer space. So, SET1 needs to include the increased bar lengths. So, that when these lengths happen in the future, the database has them. CarlIgnored
I'm doing that bar length calclulation in my algo and not in the database.
The reason for that is it gives me more control of what is the "normal" or "standard" length using a parameter for it.
If you do it in the database itself you will loose that ability and destroy raw data.
G.