ZTLs Percentage-based Renko EmulatorHere is another version of my Flex Renko script. It is uses percentage-based brick sizes to draw the Renkos instead of ATR or static brick sizes. What makes the percentage-based drawing style great is that one doesn't need to adjust stops so many times like they would with a ATR based Renko. It also makes moving between tickers smooth as well as one doesn't have to adjust the brick-size for each name.
to use: By default the setting is ".001" or 10 basis points. So ".01" is 1 percent or 100 basis points and so-forth. This style is perfect for those traders who make trades on a percentage basis over a price-level basis. It's also good for percentage-based stops.
The yellow lines represent where the price needs to go to draw another Renko brick.
Trendtrading
ZTLs Bar_TrendHere is an adaptation of TTM_Trend I coded. It's all pretty self explanatory. Aqua = buy and red = sell.
There's only one setting to tweak and it's the look-back for highest and lowest.
I have found that this indicator gives signals at almost identical areas to the TTM_Trend but tend to actually be a little more efficient (earlier buy/sell signals), although I haven't thoroughly back-tested it.
Enjoy!
Please comment below if you have any questions.
Flex Renko Emulatorupdate:
As far as my algorithm design will take me this is it. So It's complete in my eyes. Here is a "working" version of something I've been looking for for a long time: "Flex" Renko Charting.
Bricks' sizes are determined by ATR and are set by simply choosing a resolution for the ATR calculation. No need to go in and choose renko granulation(resolution) AND brick size. Renko granulation is current chart resolution. Feel free to send me feedback on how to manage the reversal bricks' calculation or any other thoughts and ideas.
Replace the "close" in the main body of the renko calculation with 'high' and 'low' to get more consistent paintings across different aggregations since renkos aren't technically based off closing prices but where the price has been. Of course it's all a matter of preference:
Brick1 = high >
nz(Brick1) + BrickSize ? nz(Brick1) + BrickSize : low <
nz(Brick1) - BrickSize ?
nz(Brick1) - BrickSize
: nz(Brick1)
