Fix tests for numpy 2.0

[e-koch]

Test fixes against numpy 2.0

[codecov]

Codecov Report

Attention: Patch coverage is 25.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 79.93%. Comparing base (7bc6bac) to head (46e5804).
Report is 4 commits behind head on master.

Files	Patch %	Lines
spectral_cube/conftest.py	0.00%	2 Missing ⚠️
spectral_cube/io/casa_image.py	0.00%	2 Missing ⚠️
spectral_cube/analysis_utilities.py	50.00%	1 Missing ⚠️
spectral_cube/spectral_cube.py	50.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #917      +/-   ##
==========================================
- Coverage   79.94%   79.93%   -0.02%     
==========================================
  Files          24       24              
  Lines        6013     6019       +6     
==========================================
+ Hits         4807     4811       +4     
- Misses       1206     1208       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[e-koch]

Failures resulting from ndarray.ptp being removed in numpy >2.0 (see astropy/astropy@fbf7c89)

[e-koch]

Removing ptp as a method fixed this issue.

Remaining issues are related to the casadata package. @keflavich the fix that was working in the uvcombine doesn't seem to be working anymore

[e-koch]

Updating the data manually via casaconfig seems to fix the casadata path error: https://casadocs.readthedocs.io/en/stable/notebooks/external-data.html#Populating-the-Data-Directory-Manually

[keflavich]

just commenting as a reminder since this is a temp check

[e-koch]

thanks. still trying to figure out why the dict structure seems to have changed.

[e-koch]

@keflavich @preshanth the tests are hitting 2 failures that seem to imply underlying changes in the image tool? I'm somewhat lost on where the change actually occurred.

The current failures have 2 sources:

1. https://github.com/radio-astro-tools/spectral-cube/actions/runs/10256840948/job/28376751741?pr=917#step:6:933 - Creation of the multi-beam test casa image is failing to set the restoring beam: https://github.com/radio-astro-tools/spectral-cube/actions/runs/10256840948/job/28376751741?pr=917#step:6:224 Ok I solved this one by forcing the correct dtypes input to ia.setrestoringbeam
2. The desc dict that casa-formats-io returns has a different key structure: https://github.com/radio-astro-tools/spectral-cube/actions/runs/10256840948/job/28376751741?pr=917#step:6:720. The list of keys the test is returning right now is here: https://github.com/radio-astro-tools/spectral-cube/actions/runs/10256840948/job/28376751741?pr=917#step:6:727 This issue remains

[e-koch]

also note that the CASA builds are pinned to numpy<2.0.

There were a bunch of additional errors related to a build numpy 1.X build somewhere in the casa module stack. That seems firmly upstream of handling in spectral-cube.

[preshanth]

On casa numpy issue. There is ongoing work to fix casa and put out an updated version. That should fix the numpy 2.0 problems. Will look at the dict when I get a chabce