mine is nowhere near matching yours. I get a flat line, then occassionally a "blip up" then a flat line for a while. My whole range for the day you have posted the chart of is only 69.37 to 69.40 on the chart.
Yes, that would have fixed it, however I've just posted version 1.2 which changes the defaults back to the proper tick indexs, sorry about that. Somehow after I completed version 1.1, I started to "experiment" with an idea on the other indexes and that code was exported into 1.1, the proper defaults are restored in 1.2.
You will need to delete the indicator from your indicator list on the *chart*, hit apply, then re-add it, that'll fixer ya up.
Quick-Summary has been updated and the download page has had its changelog updated as well.
Works like a charm now I have TICKQ as my primary data source and using the template you provided. I've read the description on how to use it but I was wondering if it could also be used as an entry trigger at predetermined support/resistance?
Thanks for this tool...looking forward to experimenting with it
I was doing a bit of experimenting myself with it this morning, I set the weights (TickQ, Tick and TickDJ) to 1, 10 and 25 and was getting some interesting results, but they are really hard to tell with the market being so choppy, going to keep playing though till I find a settings combo that works best. My range was about 20 to -20 with these settings.
btw, if you right click the right margin where the price levels are, you can set a fixed range (set this one to 25 to -25), I was using 65 to -65 on my template chart.
Since the plot is a "Public" dataseries, I don't see why you can't use it in a strategy, you dabble in code at all?
The following 2 users say Thank You to Zxeses for this post:
thank you for your indicator, I am trying litte bit with.
What I see is when I set it to COBC == True itīs still calculating (but different) on each incoming tick and / but the calculation are shown 1 bar delayed.
When I set it to COBC == False it seems to be correct.
When you compare both Panels (Panel 2 COBC = False -- Panel 3 COBC == True) you see the last 20 bars (about) are different and shown incoming calculation differs. The chart load / refresh has been about 20 bars ago.
It would be great if you could explain if itīs possible to run the indicator (perhaps after a fix) on COBC = True to save CPU load.
I attach the screenshot. Perhaps I am wrong but I wanted to tell you my observation.
Please register on futures.io to view futures trading content such as post attachment(s), image(s), and screenshot(s).