Update Acoustics Module

[jmcvey3]

Enhancements:

• Adds ability to convert sound spectral densities to millidecade format (https://doi.org/10.1121/10.0003324)
• Adds reader for WISPR (Wideband Intelligent Signal Processing and Recording) system for hydrophones
• Updates the export_audio function to input voltage timeseries and allow resampling to speed up recordings

Bugfixes

• Refactors band-averaging for spectral density levels and sound pressure levels. This refactor avoids losing information at frequencies located at band boundaries, and conducts all of the band-averaging immediately after the PSD calculation.

The jupyter notebook has been updated with these changes as well.

[simmsa]

@jmcvey3 there is a test failure on python 3.10. Any ideas on a fix there? I don't know why python 3.10 would have a different numerical result for one calculation?

The other test failures don't seem to be caused by any of your changes.

https://github.com/MHKiT-Software/MHKiT-Python/actions/runs/27647812694/job/81902073822#step:8:419

=========================== short test summary info ============================
FAILED .github/workflows/mhkit/tests/acoustics/test_metrics.py::TestMetrics::test_spl - AssertionError: 
Not equal to tolerance rtol=1e-07, atol=1e-06

Mismatched elements: 2 / 25 (8%)
Max absolute difference among violations: 9.94873047e-06
Max relative difference among violations: 1.20091383e-07
 ACTUAL: array([[82.13845 , 80.43939 , 81.25442 , 83.51936 , 80.834045],
       [83.07329 , 81.89704 , 81.74825 , 83.87166 , 81.16063 ],
       [82.84301 , 81.24031 , 81.632744, 83.92746 , 81.09888 ],...
 DESIRED: array([[82.13845 , 80.43939 , 81.25442 , 83.51936 , 80.834045],
       [83.07329 , 81.89704 , 81.748245, 83.87166 , 81.16063 ],
       [82.843   , 81.24031 , 81.632744, 83.92745 , 81.09888 ],...
=========== 1 failed, 343 passed, 218 warnings in 627.76s (0:10:27) ============

[jmcvey3]

@jmcvey3 there is a test failure on python 3.10. Any ideas on a fix there? I don't know why python 3.10 would have a different numerical result for one calculation?

The other test failures don't seem to be caused by any of your changes.

https://github.com/MHKiT-Software/MHKiT-Python/actions/runs/27647812694/job/81902073822#step:8:419

=========================== short test summary info ============================
FAILED .github/workflows/mhkit/tests/acoustics/test_metrics.py::TestMetrics::test_spl - AssertionError: 
Not equal to tolerance rtol=1e-07, atol=1e-06

Mismatched elements: 2 / 25 (8%)
Max absolute difference among violations: 9.94873047e-06
Max relative difference among violations: 1.20091383e-07
 ACTUAL: array([[82.13845 , 80.43939 , 81.25442 , 83.51936 , 80.834045],
       [83.07329 , 81.89704 , 81.74825 , 83.87166 , 81.16063 ],
       [82.84301 , 81.24031 , 81.632744, 83.92746 , 81.09888 ],...
 DESIRED: array([[82.13845 , 80.43939 , 81.25442 , 83.51936 , 80.834045],
       [83.07329 , 81.89704 , 81.748245, 83.87166 , 81.16063 ],
       [82.843   , 81.24031 , 81.632744, 83.92745 , 81.09888 ],...
=========== 1 failed, 343 passed, 218 warnings in 627.76s (0:10:27) ============

Thanks for looking so quick. Looks like a machine precision error, since it's saying 9.94873047e-06 < 1e-7. I'll set the relative tolerance to 1e-6.

[simmsa]

@jmcvey3 I think the code looks good here, but am deferring specific acoustic knowledge to you and your team.

I found 1 minor typo, everything else looks good here.

[simmsa]

Typo here in applicable

[jmcvey3]

Thanks Andrew for hopping on this! We're going to do a data comparison from work up in Igiugig with the UW research group soonish, so I'd like to wait to merge until we've started that.

[simmsa]

Thanks Andrew for hopping on this! We're going to do a data comparison from work up in Igiugig with the UW research group soonish, so I'd like to wait to merge until we've started that.

Sounds good, happy to wait.

We are planning a 1.1 release by the end of this quarter (Jun 30). Do you think this your planned work for this work will fall outside of that timeline? That is fine IMO, just wondering if we should try to include this in the next release and if we need to adjust the release timeline accordingly.

[jmcvey3]

Thanks Andrew for hopping on this! We're going to do a data comparison from work up in Igiugig with the UW research group soonish, so I'd like to wait to merge until we've started that.

Sounds good, happy to wait.

We are planning a 1.1 release by the end of this quarter (Jun 30). Do you think this your planned work for this work will fall outside of that timeline? That is fine IMO, just wondering if we should try to include this in the next release and if we need to adjust the release timeline accordingly.

I'll try to have it done by then, yes, because I'd like to have this in the next release.

[jmcvey3]

@simmsa Is this notebook error a new error from pandas 3.0?