- ago
I've recently encountered an issue after importing data in ASCII format across different timeframes. Everything seemed fine until I attempted to use one timeframe to display data in a higher timeframe on the chart. At this point, I noticed that the candles are not displaying correctly.

Although my current workaround involves importing data in different timeframes, I'm concerned about the inaccuracies it presents, especially in strategies or indicators that utilize various timeframes.

To give a clearer context, I've attached an image that exactly illustrates the problem. As you can see, the candles are incorrect compared to what would be expected for this higher timeframe (I checked this). In the image, I used M5 data to draw the M15 chart.



I am seeking assistance in understanding what might be causing this issue and how I can resolve it. Any insights or suggestions on how to correct this discrepancy would be greatly appreciated.

Thank you in advance for your help!
0
218
Solved
10 Replies

Reply

Bookmark

Sort
Glitch8
 ( 12.72% )
- ago
#1
And how can we tell this is incorrect? We can’t see and don’t have access to your 5 minute data.
0
- ago
#2
Thank you for your reply, Glitch! 🙏

To provide more context, I have randomly checked the values from other sources and even the 15-minute data from the same source (TickStory), and they appear to be different from what's shown in my chart.

May I ask if it's permissible to attach the data here on the forum?
0
Glitch8
 ( 12.72% )
- ago
#3
You can email me the file support@wealth-lab.com.

Also be sure to set the market to Currencies and not USA Stocks otherwise the data will get filtered for the US stock market hours.
0
Cone8
 ( 24.06% )
- ago
#4
All WealthLab chart data is timestamped end-of-bar.
Probably your ASCII source timestamps are start-of-bar, the typical default for most non-WealthLab data.
For data to be scaled correctly in WealthLab, the source data timestamps need to be end-of-bar.

For now, you'll have to export your data with end-of-bar timestamps.

Later, we'll need to add an option in the ASCII configuration that converts the source data to end-of-bar.
0
Glitch8
 ( 12.72% )
- ago
#5
The ASCII DataSet wizard already has an option to adjust the timestamps of the bars to end of bar. It's in the preview page.
0
Cone8
 ( 24.06% )
- ago
#6
I thought we had it, but I was looking for it on the configuration page :)

Here's it is for posterity -

0
Glitch8
 ( 12.72% )
- ago
#7
I thought it would make more sense on the preview page where you can see it’s effect immediately when you turn it on or off.
0
- ago
#8
Hi everyone!
I had altered the end-of-bar option before, but it turns out there was more to the problem.

In WealthLab, there are two different market selectors: one in the chart window and another beside the program's clock. Initially, my focus was on the selector in the chart window. However, I've learned that this selector primarily influences the "Filter Pre/Post" setting, while the selector next to the clock affects the calculation of the candlesticks.

An interesting issue I encountered involved the USDJPY symbol. When I changed the timeframe, the market selector in the chart window would automatically switch to "Stocks," leading to incorrect "Filter Pre/Post" calculations for my purposes. This is particularly problematic since the filter only applies when changing the timeframe. To resolve this, I've found that creating a new symbol is necessary to ensure accurate application of the filter to Currencies.

Partially solved problem!
It seems to have been another case of newbie-user 😅.
Thanks for all the support and suggestions!
0
Cone8
 ( 24.06% )
- ago
#9
Most providers are able to automatically choose the correct Market, but ASCII isn't able to do that. US Stocks is the default Market.

When a provider isn't able to identify the correct market, is up to you to create a Symbol record for that purpose (as you did).

Thinking out loud - US Stocks is usually a good default for most users, but it would be an improvement to allow the user to select their own default market - juste by right clicking the market and selecting "Make this my default market".
1
Best Answer
Glitch8
 ( 12.72% )
- ago
#10
What part of the problem is not solved?

I think it would make more sense to assign the market in the ASCII setup itself.
1

Reply

Bookmark

Sort