-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dual profile naming scheme and running (dolfyn.adp) cleaning functions #373
Comments
It was 'range'. I have added Might still be an idea to somehow catch this in the code somewhere. |
@willcoxe Apologies for the late reply. We don't have many test cases for dual-profiling instruments, hence there are more issues on that front. |
No rush at all. Renaming and swapping dimensions worked for me for the moment, even though it's not the most elegant solution. |
@willcoxe The cleaning functions should be fixed in the above PR. |
Hello,
I am using the dual profile option in dolfyn to read an ad2cp file and then attempting to perform some basic operations according to
the adcp example. For dual profiles sda and sdb, sda functions perfectly but because the names are appended with an _avg in sdb, the second profile, many of the operations do not run correctly, such as rotating the frame and/or cleaning data based on pressure & on correlation. Also in the second profile the dsb.attrs["cell_size"] is missing which leads to issues with some of the operations described in the example.
May of these work once the _avg is removed from the name and the time dimension is adjusted to dsb["time"] instead of dsb["time_avg"] (e.g.
dsb = dsb.swap_dims({'time_avg': 'time'})
) and I make sure to manually set dsb.attrs["cell_size"].One exception (there might be others), which I have not yet fully debugged is api.clean.remove_surface_interference(dsb).
I am guessing that others may run into this also when using dual profiles with Nortek instruments. I will continue to try to debug the problem and would appreciate any hints you might have.
The text was updated successfully, but these errors were encountered: