OmniTrader Professional Forum OmniTrader Professional Forum
forums calendars search
today this week
 
register logon control panel Forum Rules
You are currently browsing as a guest.
You should logon to access more features
A Self-Moderated Community - ALL MEMBERS, PLEASE READ!
Vote for Members who contribute the most to your trading, and help us moderate content within the Forums.


Only Forum Moderators, Administrators, and the owner of this message may delete it.

 
Jim Dean

Sage
2000100010010010010025
Posts: 3433

Joined: 3/13/2006
Location: L'ville, GA

User Profile
 
Subject : RE: OP & Renko
Posted : 8/9/2013 9:39 PM
Post #22156 - In reply to #22154

Hi Marc

First - yes - I actually have coded the entire suite of NTB's using OLang, plus many extra capabilities beyond the normal ones. So far (I keep adding to it) it is over 6500 lines of code. I've created "overlays" that draw the NTB candles on top of the normal charts so you can see both. But there's not much point in discussing this further. It would be a loooong story. Suffice to say it has been one of the most exhaustive/ing OLang projects that I've done.

Re the date thing. It's simple. Instead of the curren input for bars to be loaded (not in addition to, not optional, but a replacement), that field goes away and a new one, labelled "starting date" is added, where you fill in YYMMDD. That's the only diff the user would see or do. That change would only need to apply to NTB's - the existing bars input method could remain for TB bars.

Behind the scenes, the data-sucker-inner routine would be educated to not just load a fixed number of bars, but rather to keep on loading bars "backwards" from the HRE until a bar appears that is an earlier date than the input date. At that point the loading stops and throws out that one extra bar. The first bar in the series therefore is the first bar for that particular YYMMDD - and all the subsequent NTB bricks are built using that bar as a reference.

As time moves forward, whether a day or a month of five years - as long as that input reference date is not changed, the data-sucker-inner routine will just dutifully load in more and more bars, to assure that the starting point remains the same.

Of course any time the user CHOOSES to change the date he can, but in doing so he will be consciously deciding to allow the bricks to change and the signals that are derived from them. So if changes occur, it's under the users control rather that being an unpleasant surprise periodically.

Hopefully that clears it up.

I'm sure that N can implement it, but since that data engine is a "core" tool they can't just do it as a bandaid patch. I do know there are a lot of other data related things in the works - Forex is one and folding together intraday Test Profiles with EOD to something much easier to work with. So hopefully this will get fixed at the same time.



[Edited by Jim Dean on 8/9/2013 9:41 PM]

Deleting message 22156 : RE: OP & Renko


Nirvana Systems
For any problems or issues please contact our Webmaster at webmaster@nirvsys.com.