Conversation
First steps on processing LRAUV data in the auv-python code base
This gives a decent foundation for infilling the combine -> align -> resample steps using the existing framework that works for dorado and i2map data.
Implement first and "last" steps in process.py for LRAUV data.
Add m1_soundspeed.py script that really should be in a repo for mooring data processing
Add netcdf4 dependency to the documentation.
The coordiante variable (*time) for each data variable needs to be monotonically increasing. The data is unusable if this is not the case. Remove any data (the default behaviour) where time is not monotonically increasing
…eeded for stand-alone execution.
…er processing needed.
Metadata fixups and misc. fixes for problems encountered by more end-to-end testing.
Claude wrote some mocked data fixtures so it doesn't do the complete data processing pipeline the way the other tests do.
Move utility functions from AUV.py to utils.py to improve code organization and eliminate the need for linting exceptions. Changes: - Move monotonic_increasing_time_indices() to utils.py - Move nudge_positions() and _create_nudge_plots() to utils.py - Update imports in calibrate.py, combine.py, and logs2netcdfs.py - Remove AUV.py module (no longer needed) - Enhance utils.py module docstring with comprehensive overview Benefits: - Cleaner codebase with better utility function grouping - No more linting exceptions needed for AUV.py - All utility functions now in a single, well-documented location - Maintains all existing functionality with zero behavior changes
Testing with tethys/missionlogs/2012/20120908_20120920/20120917T025522/201209170255_201209171110.nc4 revealed this error: ValueError: conflicting sizes for dimension 'nudged_time': length 63728 on the data but length 63611 on coordinate 'nudged_time' which I gave to Claude. I told it to keep digging on the problem and it eventually found the initial cause: There it is! GPS fix 0 has a timestamp after GPS fix 1! The first two GPS fixes are out of order: GPS fix 0: 2012-09-17T03:05:44 GPS fix 1: 2012-09-17T03:04:52 This is why we now have this commit.
Add test for LRAUV processing.
This change clearly keeps the original variable names, but in lower case.
Also added _find_lat_lon_variables() for finding nav whether its dorado or lrauv. Also added test for lrauv ubat processing.
Also added _find_lat_lon_variables() for finding nav whether its dorado or lrauv. Also added test for lrauv ubat processing.
…er' from / Group.
Add bioluminescence (UBAT) processing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Initial test of loading processed ahi data into STOQS looks good. Ready to test from docker on the production server. Applies to #6.