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)
does the current version of UniRenko bars type support the following:
1) New bar only when current bar is exceeded by 1 tick
2) No new bars on session start
3) Filled gaps
my apologies in advance if this has been covered earlier in the discussion. also, does anyone have something like this for Python/R ?
@buylosellhi
does the current version of UniRenko bars type support the following:
1) New bar only when current bar is exceeded by 1 tick
--> Yes
2) No new bars on session start
---> Not sure
3) Filled gaps
--> Yes
Justtrader,
Thank You so much for coding this indicator. It is absolutely awesome! I've used it for the past few days and, it works perfectly on my uni-renko charts. It solves the only issue (in my opinion) that I was having on my uni-renko charts. It helps me see the price without having to rely on the price axis panel. Thanks Again, Great Job!
oh btw, it will also work on other chart types as well, (min, tick,other renko types, etc.. Although it only prints the current price, w/o the projections. All the way around it works great!
justtrader,
Thanks for your reply. I see the code is not checking for Session start (unlike Renko in @BarsType.cs) but where do you see the 'New Bar When Exceeded' in the calculation ? Is it the hard inequality "</>" in lines 61/62 as opposed to ">=" and "<=" ?
Funny you ask for it - I was thinking about this recently as with this change UniRenko would truly become universal (oh, ok plus some more like new session treatment, new bar on hit or exceed).
@mrmuggins version of UniRenko (screenshot from your journal) most likely uses a workaround that hardcodes some values, eg. Offset == 98 (or >=98) is considered as zero. This should work fine, but it is still a workaround for the fact that native Period.BarsPeriodValue is set to have minimum value of 1 (ie: Math.Max(1, value)).
I don't see a way to override this property to change its behaviour but maybe someone had achieved this.
Alternatively it would be also interesting to try adding completely new property and not relying on the existing Period.XXXXX fields.
