-
Notifications
You must be signed in to change notification settings - Fork 2
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
Casacore related version fixes #170
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #170 +/- ##
==========================================
- Coverage 59.20% 59.17% -0.03%
==========================================
Files 33 33
Lines 5530 5536 +6
==========================================
+ Hits 3274 3276 +2
- Misses 2256 2260 +4 ☔ View full report in Codecov by Sentry. |
It appears that there are conditions that can (somehow) corrupt large measurement sets when packages across the host virtual environment (
python-casacore
) and thecasacore
in the set of singularity containers differ. It is not entirely understood, but the general failure mode is:casacore
is usedThe error presents immediately as an error like:
This means very little to me.
The issue seems to be completely avoided by using a casacore that is somewhat consistent between all packages.
No idea what actually goes wrong with the MS, or whether the error is elsewhere. Inspecting the MS through
casacore.tables
seems to imply things are OK.Part of this change is to allow pyhton 3.11 as well.