Renko Bars

[roonius]

Ed or Roonius,

I wonder if either of you have solved the wicks issue, such that the Renko bar plots with its correct body plus just wick overhang(s) ?

Here's what it looks like in Tradestation :

It is not doable in NT 6.5

[aslane]

This will be doable in NT7. I have been working with NT to get Renko bars with correct wick values stored in the bars. Once there, using candle stick style would show you the wicks.

[jtrade]

Thanks for your responses.

[omares]

Historical Data with RENKO BARS

First sorry for my english.

I would know if it's possible to convert a 1 minute historical data to RENKO bars, so that interpolating the internal data of each bar minute it generates a new graphic Renko. If it's possible, someone who can program could try? Thank you.

[NinjaTrader_JoshP]

I believe renko bars requires tick data to build.

[rt-trader]

Hi aslane,

re post #77 - have you had any success with this yet?

If so - are you able to post the relevant code?

Thanks...

[aslane]

Rt-trader,

Yes, I have given my RenkoBarType code to Ninja, and some form of it should be in NT7B6.

[rt-trader]

Thats great,

thanks

[omares]

Historical Data with RENKO BARS

Hi Josh,

I know that Renko needs tick data, but I don't have more than 6 months of historical ticks data, and supose that other traders have similar quantity (from Gain for example). I have a mq4 code that converts historical 1 minute data to renko bars (with some limitations of course), but for backtest more years is good. Can someone convert this code to NT please?

Thanks.

[NinjaTrader_JoshP]

omares,

Understood. As a last resort you could also try one of the 3rd party NinjaScript Consultants here: http://www.ninjatrader.com/webnew/pa...injaScript.htm

[mrlogik]

omares,

As this could work, its drastically flawed because the slightest inconsistency or assumption can completely change the chart for any specific day. Perturbation theory and its application to Renko states that a small change in an assumption can have a drastic change in the result. That is why when you load 5 days vs 6 days of data on two separate renko charts and compare any given date, you will see a difference in the anatomy of the charts.

I am writing up a paper that explains may aspects of the Renko bars; their flaws, benefits, and modifications to give them greater value. When its completed, i'll post it here.

[roonius]

omares,

As this could work, its drastically flawed because the slightest inconsistency or assumption can completely change the chart for any specific day. Perturbation theory and its application to Renko states that a small change in an assumption can have a drastic change in the result. That is why when you load 5 days vs 6 days of data on two separate renko charts and compare any given date, you will see a difference in the anatomy of the charts.

I am writing up a paper that explains may aspects of the Renko bars; their flaws, benefits, and modifications to give them greater value. When its completed, i'll post it here.

Thank you in advance

[Mike Winfrey]

The big reason renko charts change depending on number of days back selected is because they they don't honor the session begins and session ends parameters in chart properties. Phantom bars fill in any gaps in data. Volume charts on the other hand will honor the session times and allow the gaps to occur. I use a session begins of 12:00 am and session ends of 11:59 PM. That means I could miss a few ticks if something happens in the 1 minute interval but i really don't care because i'm more interested in my charts looking the same every day no matter how many days of back data are selected. Just wish renko would honor that.

Having said that, i truly love EdsRenko in spite of that issue.

Mike Winfrey

[aslane]

The NT7 RenkoBars will honor session boundaries, as they start a new bar at the start of a new session. This is good or bad depending on your view point.

[mrlogik]

That's right. Depending on the price of the first tick of the entire data set loaded, since the starting reference doesn't restart at the beginning of each session.