You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I met with the NRS hydrophone team to confirm the standard for time metadata management. The situation is basically as follows: NRS data files are all exactly the same duration (4 hours), which is an attribute shared with our MARS data (10 minutes). However, there are real 6-7 second gaps between NRS files, in contrast to the false gaps or overlaps of 1 second cause by jitter in the seconds field of MARS data file names (caused by a glitch in Lucy software). The bottom line is that we should use the file start times in the NRS flac file names, and not attempt to fill gaps between files by nudging file start times like we do for MARS. pbp-json-gen currently puts NRS in the same category as MARS and tries to correct jitter. We want to change the logic to not do this. It should handle NRS time like it handles SoundTrap time.
The text was updated successfully, but these errors were encountered:
I met with the NRS hydrophone team to confirm the standard for time metadata management. The situation is basically as follows: NRS data files are all exactly the same duration (4 hours), which is an attribute shared with our MARS data (10 minutes). However, there are real 6-7 second gaps between NRS files, in contrast to the false gaps or overlaps of 1 second cause by jitter in the seconds field of MARS data file names (caused by a glitch in Lucy software). The bottom line is that we should use the file start times in the NRS flac file names, and not attempt to fill gaps between files by nudging file start times like we do for MARS. pbp-json-gen currently puts NRS in the same category as MARS and tries to correct jitter. We want to change the logic to not do this. It should handle NRS time like it handles SoundTrap time.
The text was updated successfully, but these errors were encountered: