Problems with ASCII data table and QM in 8.5 (32bit)
Posted: Jun 18 2013
Multicharts Version 8.5 Release (Build 6850)
Windows 7 Pro x64
I was looking for the same problem posted in the past, but could not find it. I'm mapping daily ASCII data downloaded from Yahoo via Python program. Most of the time data of OHLCV are shown in the correct way. But whenever Yahoo delivers just one Open price in the history with a high amount of decimals, the Quotemanager will sort OHLCV totally different. This is the outcome :
But as you can see in the following screenshot, the QM seems to mix it up on it's own where the L(ow) is not the lowest price.
Maybe the missing header, when downloading data from Yahoo, is the reason for messing the data up. Here is the original data table without the headers.
It would be nice to have a routine where OHLC data structure will be tested (L is lowest of all 4 and H ist highest off al 4 etc etc.) or I could tell the QM that one specific data structure, like Sym-Date-Time-O-H-L-C-V is always to be used. The problem I see is, that data with more then 2 places after the decimal are getting messed up only.
Need help to solve this problem ....
Thank you.
Mike
Windows 7 Pro x64
I was looking for the same problem posted in the past, but could not find it. I'm mapping daily ASCII data downloaded from Yahoo via Python program. Most of the time data of OHLCV are shown in the correct way. But whenever Yahoo delivers just one Open price in the history with a high amount of decimals, the Quotemanager will sort OHLCV totally different. This is the outcome :
But as you can see in the following screenshot, the QM seems to mix it up on it's own where the L(ow) is not the lowest price.
Maybe the missing header, when downloading data from Yahoo, is the reason for messing the data up. Here is the original data table without the headers.
It would be nice to have a routine where OHLC data structure will be tested (L is lowest of all 4 and H ist highest off al 4 etc etc.) or I could tell the QM that one specific data structure, like Sym-Date-Time-O-H-L-C-V is always to be used. The problem I see is, that data with more then 2 places after the decimal are getting messed up only.
Need help to solve this problem ....
Thank you.
Mike