We need to make a file checker that, during the initial file parsing (.raw or .01a t -> netCDF), checks to see is certain acoustic parameters change. If anyone of these parameters change in the middle of a .raw or .01a file, writing to the netCDF should stop, the netCFD should be saved, and a new netCDF should be opened and written to.
Power
Pulse duration
Sample unit (ping rate)
Receiver bandwidth
Sound speed
Start/Stop of a file
Also- File naming. From The SONAR-netCDF4 convention for sonar data, Version 1.0.
"SONAR-netCDF4 files should always end with a “.nc” suffix to indicate that they are
a netCDF file. It is recommended that the filename should sort alphanumerically into
chronological order (e.g. date and time of the first ping in the file; thus: YYYYMMDDHHMMSS.
nc). This facilitates file management and use in analysis systems."
We need to make a file checker that, during the initial file parsing (.raw or .01a t -> netCDF), checks to see is certain acoustic parameters change. If anyone of these parameters change in the middle of a .raw or .01a file, writing to the netCDF should stop, the netCFD should be saved, and a new netCDF should be opened and written to.
Also- File naming. From The SONAR-netCDF4 convention for sonar data, Version 1.0. "SONAR-netCDF4 files should always end with a “.nc” suffix to indicate that they are a netCDF file. It is recommended that the filename should sort alphanumerically into chronological order (e.g. date and time of the first ping in the file; thus: YYYYMMDDHHMMSS. nc). This facilitates file management and use in analysis systems."