MANTA Release Notes
V9.6.9
- Added zero-time start to index-time manager in Raven-X. Several attempts resulted in various issues. Raven-X handles both duty cycle and continuous datasets, indexing need to generate the same result. Brief explanation on duty cycle and continuous indexing (Issue #90).
Two types of issues resulted:
- Wrong indexing (Issue #91)
- Data Loss.
Indexing errors usually happen around hour, day or gap boundaries. Hour and day boundaries are the transition from one time period to the next, however gap boundaries are generally caused by time-gaps between file time-stamps. Some audio formats, such as NAVY and Seismic Community, store timestamps as digital values which help to guarantee accurate values. The ACTUAL sample rate is also saved, often this is not a whole number, but consists of a small fraction due to drift etc. Using a fixed sample-rate and time stamps in the filename, contributes to gaps between audio files and Raven-X treats these as a short duty cycle event Raven-X treats these as a short duty cycle event (Issue #89).
Raven-X concatenates the sounds from file to file and should have a continuous stream. Due to factors previously explained, gaps form and raven-x detects and handles and the spaces (Issue #88), but in many cases, a time period will be divided into smaller intervals, where the gap is only 1-2 seconds. This forms a disruption in the minute long time slices, and a new feature was added to MANTA that merges the two sub-intervals into a single interval with the appropriate time span.
New testing is introduced to help find issues, v9.6.9
- test methods were created to "speed test" time indexing
- naming methodology if errors are found in the future (Issue #100)
successfully ran many large datasets Dataset Examples (Issue #101) and introduced a coverage test
however type-2 (data loss) likely resulting from indexing into out of bound memory.