Of course, ability to remove/correct bad ticks is a big progress in NT7. However the process is very tedious.
Because of certain problems with MB Trading data feed, I have ~100 bad ticks last week, all of them have value = 0.0.
I'm refraining myself here from discussing the problem details in this thread, because it appears to be caused by Beta 13 / MBT Navigator 11.5.0.5 combination and I was asked to report only most recent beta problems.
I installed Beta 14 just now and I'll see what's going on.
However I cannot live with such data, because I'm using Renko bars and they go crazy when 0.0 tick occurs.
Currently, the only way to correct/remove these ticks is to edit them and to change/remove every bad tick separately. It takes hours of work.
Being unable to do my work in the "end user way" I began to hack.
I brought the database (.SDF and .MDB files) to my SQL Server 2008 Express hoping to apply a simple query to remove the wild ticks.
I connected the file to Compact SQL machine.
I was able to see tables layout, however it appears to be that the data is either encrypted, or just password protected and it was unreachable.
Therefore I have quite an urgent request and I propose a solution, much better than nothing.
The solution is to define range parameters for every instrument, either in instrument definition or in the data editor. Every tick out of range will be removed automatically, either by Data Editor upon "remove out of range" command, or even better, during a data aquisition, according to instrument range definition.
If you have any trick to get rid out of bad ticks quickly and effectively, please let me know urgently.
Because of certain problems with MB Trading data feed, I have ~100 bad ticks last week, all of them have value = 0.0.
I'm refraining myself here from discussing the problem details in this thread, because it appears to be caused by Beta 13 / MBT Navigator 11.5.0.5 combination and I was asked to report only most recent beta problems.
I installed Beta 14 just now and I'll see what's going on.
However I cannot live with such data, because I'm using Renko bars and they go crazy when 0.0 tick occurs.
Currently, the only way to correct/remove these ticks is to edit them and to change/remove every bad tick separately. It takes hours of work.
Being unable to do my work in the "end user way" I began to hack.
I brought the database (.SDF and .MDB files) to my SQL Server 2008 Express hoping to apply a simple query to remove the wild ticks.
I connected the file to Compact SQL machine.
I was able to see tables layout, however it appears to be that the data is either encrypted, or just password protected and it was unreachable.
Therefore I have quite an urgent request and I propose a solution, much better than nothing.
The solution is to define range parameters for every instrument, either in instrument definition or in the data editor. Every tick out of range will be removed automatically, either by Data Editor upon "remove out of range" command, or even better, during a data aquisition, according to instrument range definition.
If you have any trick to get rid out of bad ticks quickly and effectively, please let me know urgently.
Comment