Short list of VMDAS updates #405
Merged
Conversation
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
…ble error for if the day rolls over in the GGA sentence
akeeste
reviewed
Jul 15, 2025
It's a VMDAS software issue - all of the NMEA0183 sentences record the timestamp in UTC, but not the date. (Only the RMC sentence records the date.) When VMDAS saves the timestamps, it saves them in order, but using the date from the laptop/ADCP. This means the date will not change when UTC time rolls over from 23:00 to 00:00. |
|
@jmcvey3 Got it, thanks for clarifying. Merging |
akeeste
added a commit
to akeeste/MHKiT-Python
that referenced
this pull request
Sep 30, 2025
Discovered from a recent vessel survey that I misunderstood TDI's documentation on a couple of VMDAS parameters. The speed and direction parameters I thought it was pulling directly from the GPS it is calculating from the change in latitude/longitude over time. I renamed them and added the two variables that are actually directly from the GPS. Also discovered that VMDAS cannot take an RMC NMEA sentence, so the GPS timestamps are lacking a datestamp. Which is not helpful if your ADCP's clock is on local time and the GPS is always in UTC. So I added a code block that checks if the GPS UTC time rolled over from 23:59:59 to 00:00:00 and manually updated the day. --------- Co-authored-by: ssolson <[email protected]> Co-authored-by: akeeste <[email protected]>
Merged
akeeste
added a commit
that referenced
this pull request
Sep 30, 2025
v1.0.0 # MHKiT v1.0.0 ## New Features * Sound Exposure Level by @jmcvey3 in #388 * Add discharge function to MHKiT by @jmcvey3 in #385 ## Functionality enhancements * Fix for corrupted Nortek files by @jmcvey3 in #372 * Update integral length scale function by @jmcvey3 in #376 * Fix ever-changing RDI RiverPro depth bin ranges by @jmcvey3 in #378 * Allow clean functions to handle _avg variables by @jmcvey3 in #377 * IEC TS 62600 updates by @akeeste in #382 * MLER explanation updates/corrections by @rgcoe in #393 * Improve Nortek2 index file creator functions by @jmcvey3 in #397 * Read Sentinel V specific data packets by @jmcvey3 in #396 * Short list of VMDAS updates by @jmcvey3 in #405 * Allow user to specify universal Kolmogorov constant for TKE dissipation rate function by @jmcvey3 in #406 * Nortek Dual Profile Dataset Rotation by @jmcvey3 in #414 ## Source code improvements * Lint Tidal by @ssolson in #386 * Lint river module by @ssolson in #389 * Lint hindcast by @ssolson in #398 * Modernize Package Configuration by @ssolson in #400 * Configure specific warnings by @ssolson in #401 ## Bug fixes * Avoid failing to scan very large files by @jmcvey3 in #371 * Acoustics SPL bugfix by @jmcvey3 in #379 * DOLfYN/RDI: Set `fs` to NaN when typical calculation methods yield error (#408) by @simmsa in #409 ## Testing and Continuous Integration Updates * Fix Jupyter Notebook tests running Python 3.13 by @ssolson in #380 * CI Test Clean Up: Mock USGS, Acoustic Tolerances by @ssolson in #404 * Speed up tests with concurrency checks to prevent duplicate workflows on PRs from develop into main or from main into develop by @akeeste * Define MPLBACKEND to decrease intermittent matplotlib errors in tests by @akeeste ## Documentation and Examples * Add WEC-Sim power performance example by @akeeste in #395 * Update dolfyn function docstrings and associated notebooks by @jmcvey3 in #412 * Update examples by @akeeste in #417 * Update installation instructions in README.md by @akeeste * Adjust acoustics test tolerances by @akeeste in #420 **Full Changelog**: v0.9.0...v1.0.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Discovered from a recent vessel survey that I misunderstood TDI's documentation on a couple of VMDAS parameters. The speed and direction parameters I thought it was pulling directly from the GPS it is calculating from the change in latitude/longitude over time. I renamed them and added the two variables that are actually directly from the GPS.
Also discovered that VMDAS cannot take an RMC NMEA sentence, so the GPS timestamps are lacking a datestamp. Which is not helpful if your ADCP's clock is on local time and the GPS is always in UTC. So I added a code block that checks if the GPS UTC time rolled over from 23:59:59 to 00:00:00 and manually updated the day.