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

Pin lalsuite version and fix error in pycbc_plot_singles_vs_params #4997

Merged

Conversation

GarethCabournDavies
Copy link
Contributor

@GarethCabournDavies GarethCabournDavies commented Dec 19, 2024

This was a testing PR for some error in pycbc_plot_singles_vs_params, but I identified and fixed an error with lalsuite during the testing, so it is now both fixes.

The changes are discussed in the comments (and linked issue), but the summary is:

The matplotlib version testing failed when 3.10 was used, as it did not understand semantic versioning, this has now been added

The lalsuite version mentioned requires a data file which is not public, and so we pin to before that version until the data file is public and we can point to it

Fixes #4993

@GarethCabournDavies GarethCabournDavies marked this pull request as draft December 19, 2024 12:30
@GarethCabournDavies
Copy link
Contributor Author

This is testing the bugfix now

@@ -32,7 +32,7 @@ jobs:
cd lalsuite-extra
git lfs pull -I "data/lalsimulation/SEOBNRv2ROM_*.dat"
git lfs pull -I "data/lalsimulation/*ChirpTime*.dat"
git lfs pull -I "data/lalsimulation/SEOBNRv4ROM_v2.0.hdf5"
git lfs pull -I "data/lalsimulation/SEOBNRv4ROM_v*.hdf5"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious about this. Looking at the Gitlab repo, that file has not been changed in 8 years (!).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, looking deeper in the errors, it seems to be wanting v3.0 of that file, and it doesn't exist that I can see

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact it could be this change that caused the error

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait, is this on a lalsuite release? How did that slip through??

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking the latest lalsuite version is a viable workaround (latest tests), but I know that we generally don't like blocking versions of dependencies.

It is not planned for the required files to be on lalsuite-extra, so we will need to access an alternative.

I think blocking that version for now until the new location is decided, and then we can unblock it once we point to the new location

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pinning lalsuite to less than this version might be needed temporarily (don't block the release, pin to less than)

@GarethCabournDavies GarethCabournDavies changed the title DRAFT: trying out what is going wrong with pycbc_plot_singles_vs_params Pin lalsuite version and fix error in pycbc_plot_singles_vs_params Dec 20, 2024
@GarethCabournDavies GarethCabournDavies marked this pull request as ready for review December 20, 2024 12:51
@GarethCabournDavies GarethCabournDavies merged commit 1d995f8 into gwastro:master Dec 20, 2024
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

plot_singles_vs_params failing
3 participants