microsoft / microsoft/qlib

Environment setup confusions

Open
#1,654 2 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
48.7k
Forks
7.7k
PR merge metrics
No merged PRs in 30d

Description

🐛 Bug Description

Only using pip install pyqlib always can't really prepare necessary environment.
If I only do condo create and pip install pyqlib, even the data retrieve process can's work.
It will show ImportError: cannot import name 'init' from 'qlib' (/Users/bernoulli_hermes/opt/anaconda3/lib/python3.9/site-packages/qlib/__init__.py).
And when using models except LightGBM, other troubles will happen, like torch is not installed. Which shouldn't happen when a user go along with your guide.

And if I use the other alternative to build the environment, I need to go to the source package to build it. But this process is not mentioned in your guide, which is not friendly to newcomers.

And a embarrassing thing is when I run cd scripts && python collect_info.py all, it says that my Mac is x86-64, which is truly arm64.

I'm on Mac M1.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the documented pip-install path and the alternative source-package setup described in the issue, then inspect scripts/collect_info.py for the Mac architecture report. Check the environment and data-retrieval paths, including the reported qlib.init and missing PyTorch errors; done means the guide supports a working setup and collect_info.py identifies an M1 as arm64.

Written by the indexing model from the issue text.

Assessment

Tech stack
anaconda, python, pytorch
Domain
build-system, developer-experience, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.