qlib在client存储featrues的股票字段数据使用np进行二进制文件的存储，为何不使用HDF5操作数据呢？
Open
Nobody has claimed this yet.
question
- Dominant language
- Python
- Stars
- 48.7k
- Forks
- 7.7k
- PR merge metrics
- No merged PRs in 30d
Description
❓ Questions and Help
很想知道qlib的工程师为何要以bin的方式存储，而不用HDF5呢？
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 by tracing qlib's client-side feature storage entry points and how the NumPy-based bin files are read and written. Compare that behavior with the requested HDF5 approach, including performance and compatibility implications. Done would require a decided storage design and an agreed implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100