Eur/jpy

[Tomcat8]

Hello,

is it possible for esignal to delete the wrong data in eurjpy a0-fx,
28.01.05, 23:00 - 23:45 cet.

ONE QUESTION:

Esignal is the owner of Comstock.

Comstock is one of the leading forex data provider. Why doesn´t esignal implement the clear Comstock data? Is it not possible?

Is it possible for me to delete the weekend data in forexcharts?

Wrong data also 21.01.05 at 23:00 in eurjpy a0-fx and eur a0-fx.

Thanks.

Tomcat

[ScottJ]

Hi Tomcat,

You have a few options in regards to bad ticks. 1) Report them to us 2) use the price filter or 3) use the Bar Editor. Options 2 and 3 are desktop based solutions you do yourself. In terms of #1, please use the bad tick reporter when you see bad prices, as we store and track all submittals for patterns. We have limited QA coverage on the weekends so the ticks may not be corrected on our servers until Monday.

For more on all 3 options, please visit this KB article on bad ticks and check the subesquent links for further info.

When it comes to Forex data, one strength of the GTIS/Comstock feed is that has close to 200 contributors providing prices. This gives great coverage and frequency of updates on currency pairs across the globe. One downside is that with that many contributors, some bad prints are more likely. We are working on ways of improving our Forex feed and trying to avoid bad ticks as far "up-stream" as possible.

Thanks.

[Tomcat8]

How long do you need to correct a bad tick if reported?

Thanks

[DuaneG]

Hi Tomcat,

This is from the KB article on bad ticks

We tend to review Bad Tick Reports each hour or so and fix ASAP, especially if the symbol in question is highly followed. Since this is a completely manual process, it is possible, that we may not get around to fixing bad ticks until 12-24 hours later. In some cases (weekends & holidays) it may even take a little longer. Using the Bad Tick reporter is important not only so that we get the incorrect tick fixed but also so that we have a tracking mechanism for all these data errors. By tracking these issues, we can spot trends that we can address up-stream in our Network and, in some cases, prevent from occurring in the first place.