Hi there,
Of course your test shows your “right”. Why it is so (wrong) is something else. My reasoning (FWIW) :
UpdateOnClose vs Default may not give the AdaptiveAverage sufficient data to make any proper calculation. I did not test this (nor ran your code), but it feels logic to me. This includes any other (like ExponentialAverage) does working, which would be logic because it will be able to use the last data on its own, which AdaptiveAverage will (?) not.
Again, this is by looking at your (debug) code, and things make sense to me. But :
You should also apply JS’ test with the If / Else on Kama1Fast = Close; This is a little effort. Why do I say this ? because people like JS may check their statements before saying something. Bute merely :
(kama1Fast=Close) is indeed a Boolean test; inside a parenthesis it becomes a single statement which is evaluated before it is passed to the GRAPH function as a parameter. You can take shortcuts like that in most programming languages.
Here you may make a mistake because ProBuilder or whatever it’s called is hardly a programming language; it is the product of people who apply “intelligence” in the parser which fails in a 1000 places (ask me for real and I may come up with 20 examples). Graph is a very first command to fail (ask me about that and I need 2 A4 pages to lay it all out). Anyway, I too would attest that your “=” would be a proper boolean test, but I would try the If/Else too.
Of course you come up with this topic for a reason, and I am of the stance that I believe people first. For me to prove that they may be wrong. And thus so far you are correct. 🙂
If the If/Else still gives you the same result, try to move the Graph outside of all TimeFrame command. Thus, reset it to the fastest TF at the bottom of your program and then do the Graph again (after possible adjustment because of moving it out of the TF commands). You may be surprised on the results (yes, Graph s*cks).
You may try to use Print too (Print is decent, says me).
Still no dice ? then try to “fit” the two TF’s within each other by different factors. Thus, change the 1 minute to 10 minutes and/or change the 10 second to 1 second or 20 seconds etc. You will start to learn what’s going on really and possibly may even come to the conclusion that your assumptions on how to use the PRT programming language must be adjusted a little (I am thinking of your real code and where this could fail, you working on the proof in the same direction – which is human).
Let’s for fun bet on a nice beer that in the end you’ll say “ahhhh, like that !”. It happened to me a 100 times, just because I assume PRT to have/be a normal programming language which makes it a killing job to “live in”. People without the experience won’t notice. People with the experience will hate it. Or in the end, get used to it.
I am used to it. 🙂
.
.
