We went through our profile .nc files and it seems that half the files captured the start/end of a profile - all the expected profiles are reflected, but every other .nc file generated has this structure with 25 sample points from the bottom and top of the profile, but is not a continuous dive. I have added the first few EBD/DBD files along with the resulting .nc files (one is a usable profile, one has the 25 samples) and the timeseries/gridfile. Any explanation for why this is happening and how to fix it? https://github.com/mackenziemeier86/Pyglider-Test-Data-and-Output-.git
@mackenziemeier86 there are arguments to slocum.binary_to_timeseries that set how profiles are determined. You probably have to play with these (profile_filt_time=20, profile_min_time=20)
We went through our profile .nc files and it seems that half the files captured the start/end of a profile - all the expected profiles are reflected, but every other .nc file generated has this structure with 25 sample points from the bottom and top of the profile, but is not a continuous dive. I have added the first few EBD/DBD files along with the resulting .nc files (one is a usable profile, one has the 25 samples) and the timeseries/gridfile. Any explanation for why this is happening and how to fix it? https://github.com/mackenziemeier86/Pyglider-Test-Data-and-Output-.git