Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I am hitting a small problem and am not seeing what the issue is. The problem is that for data2 the values are not working intrabar even with intrabarpersist enabled. I am only getting values as of the close of data2.
The chart illustrates the problem - as data2 makes a new high or low, the + and - signs printed on the chart should be moving. Instead they are static, representing only the last completed data2 bar.
Hm, nice challenge. I don't see a solution (yet), but will try to work on it this weekend.
In the meantime, not to 'play down' this problem or oversimplify it, but why not use a Donchian channel (found in the download section here at futures.io (formerly BMT)), based on Data2 but plotted on Data1? That would also make this indicator less memory consuming with all those +,- and ='s. Or wouldn't that work?
(Off topic: how do you keep the scale of Data1 (6 Range) so nicely aligned (i.e. same space between bars) when adding a Data2 (1 hour)?)
Hi, I am new to your very helpful website and was searching for some workaround about some issues with MC regarding the bar magnifier feature of MC and i think your issue is the same as mind.
My understanding is that the bar magnfier can only be apllied to the trading instrument; therefore if you use multiple data series, calculations involving secondary data series are based on end of bar value. This would create a "look to the future" issue when backtesting if you use IOG in combination with intrabarpersist involving "non-tick" secondary data series because orders are generated within a bar but based on end of bar value of the secondary data series.
Just wondering if anyone has encountered similar issue and is there a workaround? I have made a feature request in MC forum and will see if there is any positive response.