|
PureBytes Links
Trading Reference Links
|
Alex,
Multicharts uses it as the same as their OpenInt. Open interest.
Jimmy
On Thu, 17 Dec 2009, Gene Pope wrote:
Thanks for all the replies.
The print() statement seems to be the problem. The code works fine without
it. The code works fine the FIRST time it's run with the print()
statement. After that, re-verifying will produce the floating point error.
Bob: I don't know why "if CurrentBar <= 1" would behave any different than
"if CurrentBar = 1". I have always used the <= convention because I can
never remember if the first bar starts at 1 or 0.
Jimmy: What does MultiCharts use the variable 'i' for? Open Interest?
In any case you don't see 'i' in my code because I didn't include the
parts I commented out. I can change it to 'ii' I guess. I recall doing
that in the past, maybe because of the conflict with 'interest'?
Gene: I did actually start clipping out all the remarked code and posted
what was left. After I posted it, I clipped further and found out the
print() statement was generating the error. I still have no idea why.
-Alex
>From: Gene Pope <gene@xxxxxxxxxxxxx>
>To: omega-list@xxxxxxxxxx
>Subject: RE: TS2Ki: Floating point invalid numbers in calculation
>
> Sometimes even "remarked out" code will generate errors as if it was still
> active, same deal with if...then loops even when if = false. Sam's advice to
> clip out the bare bones code (and then add other code slowly until error
> occurs) is a good starting point.
>
> Gene
|