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)
BT OPENING RANGE INDICATOR - without vertical lines at session changes
I had waited for Ninajtrader 7.0.1000.5 for these bugs to disappear. I am partly disappointed.
One of the bugs has been fixed - the one that caused multiple first bars of sessions - the other one is still happily living within NinjaTrader.
I am …
I have checked again the code of the opening range indicator. It uses the flawed method GetNextBeginEnd() which which may return false values under specific conditions.
The bug only affects charts built from ticks (tick, volume, range, BetterRenko) with small periods, as used by scalpers. The problem is triggered by a first bar of session, which closes prior to 0:00:00:500 after the session begin.
Example: You trade ES and use a session template such that the session begin is the open at 8:30:00 CT. If the first bar of the session closes prior to 8:30:00:500, the bar will be attributed a time stamp of 8:30:00 by NinjaTrader. GetNextBeginEnd() may return the start time of the prior session instead of the current session.
I will leave a note here once the problem is fixed. The indicator can be used safely on minute bars and on all charts that do not fire bars within fractions of seconds.
I have to correct my previous post. GetNextBeginEnd() has a new overload, which I was not aware of, and which I could use for the indicator. The opening range indicator should now also work correctly on micro charts built from ticks.
I have also added some comfort to the indicator, the opening range can now be colored. Please test the version below, if you do not find any bugs, I will put it into the download sections.
The indicator requires NT 7.0.1000.5 or later, as the signature of GetNextBeginEnd() will not be recognized by earlier versions.
Exported using NT Version 7.0.1000.26
The indicator will only run on NT 7.0.1000.5 or later
Discretionary traders: Please use the multi-timeframe version of the indicator for odd minute charts and charts built from ticks.
https://www.bigmik …
Have updated the indicator again, as V32 sometimes refused to plot. The problem was related to the use of GetNextBeginEnd() in the custom Plot() of the indicator and should be fixed now.
The new version of the indicator can be downloaded here:
Exported using NT Version 7.0.1000.26
The indicator will only run on NT 7.0.1000.5 or later
Discretionary traders: Please use the multi-timeframe version of the indicator for odd minute charts and charts built from ticks.
https://www.bigmik …
I checked all V33 indicators again, the OpeningRangeV33 is the only one that shows this behavior. It only occurs when horizontally scrolling the chart to the beginning.
It is possibly linked to the custom plot of the indicator, so it won't do any harm. Will explore this today and come back.
Had a look at the indicator. It was problem with the training period. When the indicator is put on a chart, it first does not know, how many sessions per day were selected by the user for the template. So it has to collect this information, before it can properly work.
During the training period a different logic is necessary to produce the presession range. For this reason the OpeningRangeV33 indicator produced an exception in the plot override section of the indicator, when you scrolled back to the beginning of the chart.
Some users who do not have historical tick data, but use real-time tick data, which they store over a few days may have problems with it.
To address the problem I have modified the indicator, as per version V34X1 attached below. I would appreciate, if anyone has the time to test it against the old version. You need to put on the pre-session range to check for the difference.
I'm testing the 2 version against each other. so far no difference. except no error message with new version of course. will report back if I find anything else.
The new version should plot differently for the training period of the indicator, which are the first 24 hours of your chart. You will only notice, if you horizontally scroll back to the beginning. Otherwise there should not be any differences.
Exported using NT Version 7.0.1000.26
The indicator will only run on NT 7.0.1000.5 or later
Discretionary traders: Please use the multi-timeframe version of the indicator for odd minute charts and charts built from ticks.
https://www.bigmik …
