Reformat example data names: use {region}_data for 1-day data, and {region}_data_1min for 1-min data#781
Conversation
|
|
|
@cning112 Thanks for your contribution. I found a lot of commands with different format Would you like to format them to the same path? |
|
sure, will make the change in the next commit. Thanks |
|
Actually I think the |
|
@cning112 Yes. Removing the redundant prefix make it simpler |
|
@cning112 Please check the Paths in CI workflows Thanks |
yahoo_cn_1min to cn_data_1min{region}_data for 1-day data, and {region}_data_1min for 1-min data
{region}_data for 1-day data, and {region}_data_1min for 1-min data{region}_data for 1-day data, and {region}_data_1min for 1-min data
|
It looks great! Thanks so much! |
…`{region}_data_1min` for 1-min data (microsoft#781)
* Fix high-freq data name from `yahoo_cn_1min` to `cn_data_1min`
* re-format example data names using `qlib_{region}_{feq}`, e.g. qlib_cn_1d
* re-format example data names using `{region}_{feq}`, e.g. us_1d and cn_1min
* keep using for 1day data, and change 1min data to
…ft#781) * feat: add DocDev for auto-generating workspace documentation * fix: update markdown instructions in tpl.yaml * feat: add enable_doc_dev flag and conditionally call DocDev


Description
Use the same name for 1min data
Motivation and Context
The same data has two names, meaning the same data needs to be downloaded twice to run some examples.
How Has This Been Tested?
Screenshots of Test Results (if appropriate):
Types of changes