search

SECOORA / GUTILS

🌊 🚤 Python utilities for reading, merging, and post processing Teledyne Webb Slocum Glider data
MIT License
7 stars 11 forks source link

Allow users to speficy a CAC file if metadata is not contained in the binary files #1

Closed kwilcox closed 7 years ago

kwilcox commented 7 years ago

For practical purposes, this sensor list is very rarely included in each file due to it's large size relative to the actual sensor data (as an example, the file binary file I'm working with is 78680 bytes and the ascii header takes up 78481 bytes). The operator can choose to either 1) Include it in every file, 2) include it in no files if there is already a copy of the sensor list on shore, 3) Include it in just the first file of the mission.

For our real-time operations, we generate this file (called a cache or cac file) on shore and then set up the glider to NEVER include it in the data files.

Once the files are on shore, the dbd2asc executable takes one or more binary data files and, using the sensor list either contained in the file or the location specified via dbd2asc -c /PATH/TO/SENSORLILST.cac, converts the binary data to ascii. As far as I can tell, GUTILS provides no option to specify an external cac file. My guess is that the vast majority of users who would potentially use this repo will also NOT transmit this sensor list in every binary data file, but can't say for sure.

kwilcox commented 7 years ago

Moving away from the python binary reader solved this