Could-not-obtain-historical-data-for-symbol-on-ASCII-DataSet

Hi,

1. Make sure that the ASCII DataSet's entries in the Data Manager (Historical tab) are checked.
2. Double check your ASCII DataSet's configuration. The data format may not be uniform across all the files.

P.S. If the data is intraday it's quite likely that the two problematic files have irregular data in the beginning. We already fixed an issue like this before in a previous build but just to make sure, you can send them to support@wealth-lab.com.

Eugene, thanks for your reply!

Got the files and just like I suspected, the start of file looks irregular. The file that works is recognized as Minute data, the other two have gaps preventing WL7's auto-detection of timeframe. Try putting them in a new DataSet and avoid mixing such files in one ASCII DS.

They did, it didn't work.

In this case, as a workaround try deleting the first few lines of the irregular data file.

Did this option too. Still the data is not loaded. There are no such problems in WL6. Can you fix this bug in WL7?

Eugene, hello!
Went back to WL7 and couldn't load files with quotes 2019Test.txt and 2021Test.txt. So the bug is not fixed. What should be done so that the files with quotes 2019Test.txt and 2021Test.txt are loaded into WL7?

There was no build since 3/2/2022:
https://www.wealth-lab.com/Software/ChangeLog

So Dion's fix from 5/3 applies to an upcoming yet unreleased build.

Eugene, when will the fix build be released?

Hi Denis, it will likely be part of our next major WL8 release. We don’t plan on another WL7 release, but if this is something critical for you we might make an exception.

Hey Glitch!
Thanks for the answer!
For me this is critical. Can't produce test systems. The work is not being done. It is not possible to wait for a long time.
I ask you to make an exception and fix the decision of the error of the highest importance in WL7.

Hi Denis, due to some travel schedules we won’t be able to get another WL7 build out until March 19. What data scale do you intend to backtest against? I can compress these files to your desired scale(s) and provide you new ascii files.

Glitch, I understand correctly, until March 19, 2022 the error will be fixed?

That’s the earliest we can do another release.

Let's do this. I will wait until 03/19/2022. I'll wait for the bug to be fixed by then. Deal?

As you wish.

This is a major issue for me as well. Please let me know too when the new build is released.

I'll let you know. I'm visiting Egypt now and unless I contract COVID and am not able to fly back, I should be back Friday the 19th and can release the build then.

@mtahta
But what issue are you having? We haven't received any bug report or attached files from you.

I have an ascii dataset for DAX, that I am trying to visualize in the chart but getting a Could not obtain historical data for symbol: DAX error. The timestamps are not equally distributed in the CSV file. There is no problem importing the folder but the problem is I cant visualize the data on chart. Here are some screenshots and the file itself

Have you tried choosing a non-Daily bar scale from the chart window's toolbar (because this seems to be a second-based data)?

At any rate, let's wait for B51 with the fix.

Hey!
You wrote earlier that you would fix the above error.
In WL7, this bug has not yet been fixed.
WL8 came out and here, too, this error has not been fixed.
Please let me know if you will correct this error or not? If so, when will the bug be fixed?

Hi Denis,

From my perspective it's fixed, ASCII is working well as far as I can see in all scales. Can you email me the ASCII file in question so I can check it out? Also let me know exactly the issue you're facing with the file.

support@wealth-lab.com

Thanks :)

Denis, thanks for passing us the files. The intraday data in the beginning of the file is too irregular. Unlike WL6, Wealth-Lab 7/8 uses it in its guesswork process to make decision about the possible scale automatically. The bar scale in your file cannot be determined but this ain't a bug. Without you saying it's 1-minute data, the timestamps are too ambguous and even to me suggest it may be tick or second scale. Now that your data has confused a human, imagine how hard it's for the computer. :)

Thanks for providing the data. There were a few issues with the data. First off, it looks like there are multiple tickers in the same file. Our ASCII provider expects a single file per ticker. Second, as Eugene pointed out, the times were all over the place, so it was not possible to determine a proper frequency of the data. Nevertheless, I was able to create a DataSet and see the data in WL8, were you unable to do so?

Hey!

I assume that the files contain the above errors.

Created a DataSet for 2013.txt and 2021.txt files in WL8. I show you what happened:

1. File 2021.txt. The data from the file is not loaded. A window pops up with the following text: "Could not obtain historical data for symbol: 2021".



Thus, it was not possible to view the data in WL8.

2. File 2013.txt. <Per> value is loaded and displayed for 2 minutes or more.



However, the <Per> value of 1 minute is not displayed. A window appears with the following text: "Could not obtain historical data for symbol: 2013".



Created a DataSet for 2013.txt and 2021.txt files in WL6.

There are no such problems in WL6. Although there are errors in the files. These files are loaded and displayed on the screen. The <Per> value can be set to 1 minute or more. 2013.txt and 2021.txt are displayed correctly:



WL6 is simple, reliable and trouble-free, like a Kalashnikov assault rifle. WL8 needs to be improved.

Please fix this bug in WL8. Purpose: to display <Per> values ​​of 1 minute or more in 2013.txt and 2021.txt files.

Hi Denis, you'll need to adapt a little to get the data working in WL8, there is a restriction in that it expects all of the files in a DataSet to have the same frequency. Your two data files, 2013 and 2021, are determined to have two different underlying frequencies, so in order to consume the data, please create two different DataSets for them. I'll try to get this new restriction overcome, but for now this should get you up and running.

Thank you for your reply!
I will do everything according to your recommendations.
When can you work around this new limitation? Can you give an approximate time frame?

I'll work on it over the weekend.

Thank you.

OK, looks like it's taken care of for Build 5, let's revisit then!

Hello!

Installed the Build 7 update today.

In the DataSet, I select the symbol 2013 and again I cannot load it.



This issue was previously resolved. Symbol 2013 loaded without errors.

Please fix this error.

Hmm, I'm not seeing the issue. Can you post a full screen shot including the status bar?

I am fulfilling your request.

I see you have some additional files in the folder, would you mind sending them over? It could be something in those files which is why i’m not able to reproduce.

If anyone stumbles onto this thread, here's update: Dion determined that the user's default chart data range in his Preferences was set to 2021-2022 whereas the charted symbol in question had data in 2013. WL8 is working correctly as changing the data range to a more sensible choice like Most Recent Bars would obviously show the data.

Accepted the information. Thanks for the answer.