One of the tasks of echoshader_flow.py is to assemble an MVBS dataset whose path is cached and accessed by the Panel app.
Currently it seems that there is some problem with grabbing the correct individual MVBS zarr files in assembling this combined MVBS dataset. As a results, even though the current datastore_shimada.yaml request for a 3 hour window, the actual MVBS dataset assembled in echodataflow/code/echodataflow/echodataflow-output/echoshader_flow/shimada/eshader.zarr only contains much less data, ~2 hrs 20 mins long only (see image below). I have checked the content of this eshader.zarr that it indeed contains only ~2 hrs 20 mins data.
Below is what is currently shown on the Panel app:
One of the tasks of
echoshader_flow.pyis to assemble an MVBS dataset whose path is cached and accessed by the Panel app.Currently it seems that there is some problem with grabbing the correct individual MVBS zarr files in assembling this combined MVBS dataset. As a results, even though the current
datastore_shimada.yamlrequest for a 3 hour window, the actual MVBS dataset assembled inechodataflow/code/echodataflow/echodataflow-output/echoshader_flow/shimada/eshader.zarronly contains much less data, ~2 hrs 20 mins long only (see image below). I have checked the content of thiseshader.zarrthat it indeed contains only ~2 hrs 20 mins data.Below is what is currently shown on the Panel app:
Below is what's in
datastore_shimada.yaml