Support team: I am seeing an issue where QuoteManager is truncating prices on import: the price supplied in the source csv file is showing a proper 5 decimal precision (ie: 1.60377), yet after importing to the database, the precision is cut at 2 places (ie: 1.60, or 1.6).
I am guessing that I need to multiply prices? I cannot find a step by step guide in the online documentation, maybe I missed it?
As my datasource for backtest data, I am using TickStory/Dukascopy. Upon inspecting the files, there is nothing incorrect about the sources. Images below.
My procedure:
Step 0: set up a new symbol in QuoteManager, in this case "GBPUSD_test" a forex pair.
Step 1: ASCII data import from CSV. See the image 1_ImportingData.
- The file contents clearly show 5 place precision OHLC
- Note the "volume" is total ticks, time is GMT, resolution is 1 min
- All looks ok
Step 2: See image 2_ImportedSuccessfully. No issues seen
Step 3: Image 3_TruncatedPrices shows:
- on left, the data file with prices at high precision
- center, the data viewer showing a full database but with truncated prices
- right, the matching chart with this data
Image 4_EOFTruncatedData shows the end of the same file and the database contents for completeness.
Help needed: ASCII data import truncating price decimal places
-
- Posts: 45
- Joined: 07 Mar 2024
- Has thanked: 13 times
- Been thanked: 1 time
-
- Posts: 45
- Joined: 07 Mar 2024
- Has thanked: 13 times
- Been thanked: 1 time
Re: Help needed: ASCII data import truncating price decimal places
I think I may have figured this out by looking at some of the other pre-made settings, but I am not really sure. I ended up not using the price multiplier - it made things more confusing. But, in the symbol settings there is a relationship between the exchange listing and a multiplier and "big points" which is opaque.
It would be helpful is someone could point me to the right documentation on this.
It would be helpful is someone could point me to the right documentation on this.
- Kate MultiCharts
- Posts: 598
- Joined: 21 Oct 2020
- Has thanked: 9 times
- Been thanked: 149 times
Re: Help needed: ASCII data import truncating price decimal places
Hello Talky_Zebra,
If you need the prices to be imported as is, leave the Price Multiplier set to 1.
As for the symbol settings in QuoteManager, please see this page for more info.
If you need the prices to be imported as is, leave the Price Multiplier set to 1.
As for the symbol settings in QuoteManager, please see this page for more info.
-
- Posts: 45
- Joined: 07 Mar 2024
- Has thanked: 13 times
- Been thanked: 1 time
Re: Help needed: ASCII data import truncating price decimal places
Honestly, I don't understand what "big point value" means from that description. Also, since I am importing data from a third party, and I don't see that they reference that... its hard to tell what to do with it.