julesrulesny Legend   Posts: 498 Joined: 8/28/2009 Location: NYC  User Profile | Jim, Wow. I was just mind twisted with that explanation turning out to be quite a learning experience. Thanks for explaining that in such detail regarding this problem with NTB charts..(not just with OT either.. as it seems to be across many or all platforms..).. Which would then make OT superior in that regard if they were the ones to fix this!! And just a date change! Sounds so simplistic! I'm sure its not though.. I do have some questions - As I'm sure your probably tired of discussing this.. But.. 1 - What was it in Olang that you were able to do, to fix this? Or, perhaps a simpler question - Did you actually code Omnilanguage to compile actual NTB Charts?? (Such as Renko? Point&Figure, etc??).. If that's the case.. I didn't even know that could be done due to some of the constraints.. 2 - As per the fix, you referenced having the ability to put in an exact date - Having this as an option along with loading bars/bars back seems like a very doable fix.. However, if its the construct of bars loaded that causes these issues where when you load up the same bars loaded, your going to get different results period after period.. (being that the first bar the NTB charts are constructed will differ so signals on the Voteline will differ as time progresses.) So.... Lets say a user put in 300 bars loaded today - does his/her BT, testing, Port.Sim., gets tradable signals, etc Then the next day, if he wants to get the same results, what if he put in 301 bars loaded? Followed by 302? 303? .. Thanks, Marc [Edited by julesrulesny on 8/9/2013 5:54 PM] | |
