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

Note from Lupin on install errors #1

Open
jkanner opened this issue Mar 4, 2022 · 2 comments
Open

Note from Lupin on install errors #1

jkanner opened this issue Mar 4, 2022 · 2 comments

Comments

@jkanner
Copy link
Contributor

jkanner commented Mar 4, 2022

Tuto 1.4:

I obtained the following (error ??) message when I performed the installation of PYCBC 1.18.0 and LALsuit 6.82 although I can successfully run all the codes in each code cell. Should we take care it?

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
tensorflow 2.8.0 requires tf-estimator-nightly==2.8.0.dev2021122109, which is not installed.
tensorflow 2.8.0 requires numpy>=1.20, but you have numpy 1.19.5 which is incompatible.
datascience 0.10.6 requires folium==0.2.1, but you have folium 0.8.3 which is incompatible.
albumentations 0.1.12 requires imgaug<0.2.7,>=0.2.5, but you have imgaug 0.2.9 which is incompatible.
@jkanner
Copy link
Contributor Author

jkanner commented Mar 4, 2022

@linlupin Thanks for flagging this.

I tried removing the version numbers for pyCBC and lalsuite, the tutorial 1.4 seems to run without error. I'm tempted to try removing the version numbers from all of the pip install commands. There are pros and cons to doing it this way, but in principle, always having the latest version of a given package should be an OK default.

Do you agree we should try removing version numbers from the pip install commands? If needed, we could always add back in a specific version for some tutorials.

@linlupin
Copy link
Collaborator

linlupin commented Mar 5, 2022

No problem. I suppose that we can just remove the version number. But it is best to test whether the installation of the latest version has any bug or not.

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