Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PyPI Versions and Compatibility with Torch #90

Open
ziqihuangg opened this issue Dec 24, 2024 · 1 comment
Open

PyPI Versions and Compatibility with Torch #90

ziqihuangg opened this issue Dec 24, 2024 · 1 comment
Assignees

Comments

@ziqihuangg
Copy link
Contributor

No description provided.

@ziqihuangg
Copy link
Contributor Author

ziqihuangg commented Dec 24, 2024

We address some common questions recently shared by our users (thanks for the feedback!). A fix will be included in the upcoming vbench 0.1.5 release.

Q1: Why does pip install vbench install version 0.1.0 instead of 0.1.4?
A1: That's probably because torch 2.0.0 (or above) is already installed in your environment. Only vbench 0.1.0 allows torch 2.0.0 and above. vbench 0.1.1 to vbench 0.1.4 requires torch<2.0.0 and >=1.12. This strict dependency on Torch version is to ensure reproducibility of numerical results in some scenarios. We will try to relax this restriction to improve compatibility with newer Torch versions, and provide the fix in vbench 0.1.5.

Q2: When using vbench installed via pip, why do I encounter errors like unrecognized arguments: --mode=custom_input?
A2: That's because the vbench package is not up-to-date (see Q1 above for why).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants