From discussion with @Sohambutala:
Some functions in the subpackage consolidate such as add_location and add_splitbeam_angle have inconsistent support for whether or not non-in-memory Sv or EchoData datasets are allowed as inputs. In a workflow sense it is much better to allow stored netcdf or zarr files that contains these datasets, so we should add the support uniformly for functions in the consolidate.
Some specific notes:
add_splitbeam_angle currently accepts in-memory or stored Sv datasets, but not for EchoData
add_location currently does not accept stored Sv or EchoData datasets
From discussion with @Sohambutala: Some functions in the subpackage
consolidatesuch asadd_locationandadd_splitbeam_anglehave inconsistent support for whether or not non-in-memorySvorEchoDatadatasets are allowed as inputs. In a workflow sense it is much better to allow stored netcdf or zarr files that contains these datasets, so we should add the support uniformly for functions in theconsolidate.Some specific notes:
add_splitbeam_anglecurrently accepts in-memory or storedSvdatasets, but not forEchoDataadd_locationcurrently does not accept storedSvorEchoDatadatasets