Hey Eugene, Russian community is online))
When I create a dataset using Finam group, like "MOEX Bonds" the size of the dataset will be the same every time (or very close, like 2522 and 2528), but the size of "with data" subset will be vey different.
I've created two dataset fo "MOEX Bonds" on two different servers. First was 2522, second was 2528, but with data was like 600 and 400. And trying DataSets -> Update DataSet and Historical Providers -> Update Finam Data looks like not helping. And I'm also sure 600 is not a full dataset with data - there are more symbols with data. I do also suspect they should all be with data)).
Could you please check that?
When I create a dataset using Finam group, like "MOEX Bonds" the size of the dataset will be the same every time (or very close, like 2522 and 2528), but the size of "with data" subset will be vey different.
I've created two dataset fo "MOEX Bonds" on two different servers. First was 2522, second was 2528, but with data was like 600 and 400. And trying DataSets -> Update DataSet and Historical Providers -> Update Finam Data looks like not helping. And I'm also sure 600 is not a full dataset with data - there are more symbols with data. I do also suspect they should all be with data)).
Could you please check that?
Rename
Michael, long time no see :)
Looked into it under debugger and found no glaring issues in the data provider. Many randomly picked bonds can be charted successfully while the data for some bonds isn't returned by Finam. It's a free feed and data availability is not guaranteed. 🤷
Re: 2522 vs 2528 symbols. The classification of Finam symbols is cached and refreshed automatically every week. Different devices may and will have different snapshots of the classification.
Looked into it under debugger and found no glaring issues in the data provider. Many randomly picked bonds can be charted successfully while the data for some bonds isn't returned by Finam. It's a free feed and data availability is not guaranteed. 🤷
Re: 2522 vs 2528 symbols. The classification of Finam symbols is cached and refreshed automatically every week. Different devices may and will have different snapshots of the classification.
QUOTE:
2522 vs 2528 symbols
I'm OK with it. Although the time gep between creating these datasets is an hour or so, adding new bonds can be a reason. Doesn't matter.
My main concern is Symbols with data. I hoped there is some kind of error or something)).
I also get errors like this:
The order of symbols suggests the "MOEX Shares" group. Looks like the security codes returned by Finam may be incorrect there. Use "MOEX Top" instead - it works.
Also, their website's Export section now uses Google captcha. Don't get caught if the data feed breaks beyond repair any time soon.
Also, their website's Export section now uses Google captcha. Don't get caught if the data feed breaks beyond repair any time soon.
No those records are from my stocks dataset (all MOEX stocks without "RM-{...}" tickers).
These symbols work if you use "MOEX Top".
Moreover, these symbols work fine on my laptop (from the same All Moex Stocks group). But when I created a dataset on new server - I got these errors for some of the symbols.
Which suggests that their classification file (which the provider downloads) may get messed up lately.
P.S. I've retracted "MOEX Bonds DataSet" from the topic title since their issue may have a broader impact.
P.S. I've retracted "MOEX Bonds DataSet" from the topic title since their issue may have a broader impact.
I respect Occam's razor, but it doesn't help in this case at all))
I'll try MOEX API provider, I didn't like it last time, I'll give it another chance).
I didn't spot an issue in the provider which doesn't leave out the chance of a server-side issue with classification group file. The proposed workaround seems to do the trick.
Your Response
Post
Edit Post
Login is required