You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The get_MVBS method should have options to average based on either ping number (current) or ping time (not implemented yet), like below:
# Average based on timeEchoData.get_MVBS(average_type='time', MVBS_time_bin=time) # time : timedelta# Average based on ping numbersEchoData.get_MVBS(average_type='ping', MVBS_ping_bin=ping_size) # ping_size : int
It should also accommodate averaging across the file boundaries when many consecutive files were collected in a mission. This requires using xarray.open_mfdataset. Most likely also need to look into efficiency issue re. chunking and invoking dask correctly.
The text was updated successfully, but these errors were encountered:
leewujung
changed the title
MVBS calculation improvement
Improving MVBS calculation based on either time or ping number
Oct 17, 2019
leewujung
added this to the
parallelization of basic processing functionalities milestone
Dec 10, 2019
leewujung
changed the title
Improving MVBS calculation based on either time or ping number
MVBS calculation based on either time or ping number
Dec 10, 2019
The
get_MVBS
method should have options to average based on either ping number (current) or ping time (not implemented yet), like below:It should also accommodate averaging across the file boundaries when many consecutive files were collected in a mission. This requires using
xarray.open_mfdataset
. Most likely also need to look into efficiency issue re. chunking and invokingdask
correctly.The text was updated successfully, but these errors were encountered: