GreyingSurfer
Active member
- Messages
- 173
- Likes
- 0
Excuse me if this is perhaps not the ideal thread to host this, but this seems to be where the active PnFers are hanging out at present.
I have a little problem with a differnce between the output of my PnF calcs and Sierras, using the same data file. It's more of a theoretical than a coding question, really.
The problem arises with some oldish data I'm using at the moment which is only stored at 5 mins. Using a 10x3 chart some bars are long enough to get a reversal within the bar. My code simply looks for a new box in the direction of the current PnF bar, and only considers the possibility of a reversal if that step fails. So if the PnF is up, and the current price bar goes up enough to plot a new O then that's it, however far down the close of the bar might end up.
Sierra does it differently, I'm still working out exactly how. But clearly it looks at the open first. In one case I'm looking at I'm in a PnF down bar/column. The next price bar opens up, but not far enough to reverse, it then goes on far enough to reverse the PnF at the high. Finally the close of the price bar is also the low, and far enough down to reverse again. So Sierra ends up drawing 2 PnF columns for a single price column.
In the case I've given it's pretty clear that the price went up, and then closed at the low, so it went down afterwards. However, things aren't always so clear cut, so if I'm trying to code this more globally, what sort of rules should be applied?
What is the answer here? I know the real answer is not to use 5 min data, so this doesn't arise. However, it's what I have at present, and I still want to get this sorted more generally. Which approach is "more correct"? And does anyone know if there are any generally approved strategies to apply in this case?
I have a little problem with a differnce between the output of my PnF calcs and Sierras, using the same data file. It's more of a theoretical than a coding question, really.
The problem arises with some oldish data I'm using at the moment which is only stored at 5 mins. Using a 10x3 chart some bars are long enough to get a reversal within the bar. My code simply looks for a new box in the direction of the current PnF bar, and only considers the possibility of a reversal if that step fails. So if the PnF is up, and the current price bar goes up enough to plot a new O then that's it, however far down the close of the bar might end up.
Sierra does it differently, I'm still working out exactly how. But clearly it looks at the open first. In one case I'm looking at I'm in a PnF down bar/column. The next price bar opens up, but not far enough to reverse, it then goes on far enough to reverse the PnF at the high. Finally the close of the price bar is also the low, and far enough down to reverse again. So Sierra ends up drawing 2 PnF columns for a single price column.
In the case I've given it's pretty clear that the price went up, and then closed at the low, so it went down afterwards. However, things aren't always so clear cut, so if I'm trying to code this more globally, what sort of rules should be applied?
What is the answer here? I know the real answer is not to use 5 min data, so this doesn't arise. However, it's what I have at present, and I still want to get this sorted more generally. Which approach is "more correct"? And does anyone know if there are any generally approved strategies to apply in this case?
