Dear all,

We are currently developing a new Data Download tool and are looking for testers. On release, this will be for 'Active' and above subscription levels.

If you are interested please click here.

Your comments and suggestions are welcome.

Karl.

Hil,

Point taken and I agree - I have sent a message to Geoff who will be in at around 9.30 and I will also speak to him so that we can get to work on trying to iron out the bugs in this.

In answer to the 'wat happened to Karl' question, he is now in the Carribean working on an eco yatch - it is apprently raining a lot!


Ian

It sounds like a rotten job. Someone's got to do it, I suppose.

The problem revolves around the fact that there are two sets of high/close values for the day.

The Traded HL and the Mid price HL.

MoneyAM's Stockwatch (and hence data feed) currently uses the former which I imagine feeds into the database and hence is used for the OHLCV end of day data.

Using the Traded HL for EOD data leads to all kinds of problems.

qwento,

Thanks I will pass this onto Geoff,

Ian

What's the official plan for this? Bottom of list or just one up?

BT,

Don't worry - we will get this resolved as soon as possible.

Ian

Hello All,

i see Ian has let it out of the bag that i am in the firing line for the datadownloads in Karl's absence. and it is obviously a joy :)

could soemopne please suggest an epic or 2 that would be good examples of the problem.

cheers,

g

Will get you some from tonight's download...

:) BT many thanks ...

Some of the FT350 offenders

LLOY Low 410 (mid traded low of 443.25)
BB. Low 278.39 (mid traded low of 294)
HNS Low 403 (mid traded low 414)

When fixed we'll get to see more of hilary....

qwento, exotoxin,

sorry for tardiness this morning ... been saving a kitten's from up trees .. will get onto it ... many thanks for the epics,

g

A cracking example of the perils of basing OHLCV data on traded high/low

AZN Low of 2p

I know it had a bad day but somebody got a bargain ;-)

(The high looks a bit suspect too)

Thanks Qwento,

I will pass onto Goeff,

Ian

Dear All,

have looked into the problem (and many thanks for the epics).

the good news is: we have patched the problem. thanks to spook(JT) getting up at 3am - such a selfless man!

the bad news is: unfortunately this will only hold for data to last night.

the better news is: that we now know what the problem is and will be working on the solution.

Thanks very much for all patience and help on this.

will get back to you as soon as it is solved :)

G

Has this been pushed to the bottom of the list?
Would be nice if it was completed and we all could rely on it's accuracy.

BT,

I will speak to the developers and find out a timescale.

Ian

BrianTrayda,

Can you please give me an epic and date where there is a problem? I need to find the source of the error and correct that rather than just constantly reloading the data.

Cheers,
Jonathan.

Spooky: Look at Msg.#167 from Geoff.. Is that complete?