bnwkeys
commented
6 years ago Usage:
- run testAzfpUnpack which imports azfpUnpack. Edit filepaths inside testAzfpUnpack as necessary and check import dependencies on your environment.
Issues:
- (minor) echograms are being plotted on the wrong axes
- (major) unpacked AZFP data is not being saved
- will require debugging script to interrupt before plotting routine and write out data
- unpacked AZFP data needs to be packed into netCDF format
- (major) refactor code, get rid of object-oriented paradigm
- this is literally MacGyvered together from object-oriented code
- to properly create a standalone utility: ~ break script during file read routines ~ extract necessary config information, metadata, and parsing instructions ~ replicate only parsing routine in a new script and copy in static configs and meta
- (major) rev-engineer matlab scripts to check for compatibility
- test current script against other sample data
- check for flexibility of code to handle all use cases reading all AZFP data ~ make sensor/config agnostic ~ validate against vendor code (matlab)
This is a commit of the first successful attempt at reading AZFP. The data is not being plotted correctly but I'm pretty confident it is being extracted. Right now it does not spit out or save the unpacked data, it only unpacks it and attempts to plot which it writes out as a PNG then exits.