detailed_workflow.ipyb collector.py not working
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 48.7k
- Forks
- 7.7k
- PR merge metrics
- No merged PRs in 30d
Description
❓ Questions and Help
Thank you for making this tool.
I am learning the ropes and was going through [\examples\tutorial\detailed_workflow.ipynb](https://github.com/microsoft/qlib/blob/main/examples/tutorial/detailed_workflow.ipynb)
I am stuck at at cell where it is suppose to download extra data
if not p.exists():
!cd ../../scripts/data_collector/pit/ && pip install -r requirements.txt
!cd ../../scripts/data_collector/pit/ && python collector.py download_data --source_dir ~/.qlib/stock_data/source/pit --start 2000-01-01 --end 2020-01-01 --interval quarterly --symbol_regex "^(600519|000725).*"
!cd ../../scripts/data_collector/pit/ && python collector.py normalize_data --interval quarterly --source_dir ~/.qlib/stock_data/source/pit --normalize_dir ~/.qlib/stock_data/source/pit_normalized
!cd ../../scripts/ && python dump_pit.py dump --csv_path ~/.qlib/stock_data/source/pit_normalized --qlib_dir ~/.qlib/qlib_data/cn_data --interval quarterly
I just stays at stalls for a couple hrs and does not download the data. You can see the output here -
https://gist.github.com/vishalkhialani/1b15eb9a50511f67e05cf2d3d7835f75
I am on win11 and tried it on linux too but it did not help.
I tried to debug it but its taking very long as I am new to the tool. Please can someone guide me on this.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with examples/tutorial/detailed_workflow.ipynb and reproduce the data-download cell, then compare its output with the linked gist. Read scripts/data_collector/pit/collector.py and scripts/dump_pit.py to identify where execution stalls. Done means the PIT data downloads, normalizes, and reaches the dump step on the reported environments, or the issue documents a specific reproducible failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100