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
With large datasets the dfmt.get_Dataset_atdepths() function is very computationally expensive. Providing a subset of the dataset is possible, but the user should be aware of which layer variables should be passed on. This is inconvenient. In the below example only mesh2d_ucx and mesh2d_ucy are needed by the user, but many variables are required for the depth slicing:
Desired solution
Add a variables_toslice argument to dfmt.get_Dataset_atdepths(), in this case variables_toslice= ["mesh2d_ucx","mesh2d_ucy"]. If provided, this would overwrite the derived variables_toslice in the function. It is derived based on time/faces/layers dimensions, so when passing a 1D variable, it will also be sliced (eg bedlevel will also get several layers).
Alternative
It might be better to extract the layer data out of the dataset (like the .grid data is also kept separately). This would also likely solve things for d3d4, schism, rst and other formats.
The text was updated successfully, but these errors were encountered:
veenstrajelmer
changed the title
add varlist argument to dfmt.get_Dataset_atdepths()
add varlist argument to dfmt.get_Dataset_atdepths() or move layer vars in grid-like acessor
May 14, 2024
veenstrajelmer
changed the title
add varlist argument to dfmt.get_Dataset_atdepths() or move layer vars in grid-like acessor
add varlist argument to dfmt.get_Dataset_atdepths() or move layer vars to grid-like acessor
May 14, 2024
With large datasets the
dfmt.get_Dataset_atdepths()
function is very computationally expensive. Providing a subset of the dataset is possible, but the user should be aware of which layer variables should be passed on. This is inconvenient. In the below example onlymesh2d_ucx
andmesh2d_ucy
are needed by the user, but many variables are required for the depth slicing:Desired solution
Add a
variables_toslice
argument todfmt.get_Dataset_atdepths()
, in this casevariables_toslice= ["mesh2d_ucx","mesh2d_ucy"]
. If provided, this would overwrite the derivedvariables_toslice
in the function. It is derived based on time/faces/layers dimensions, so when passing a 1D variable, it will also be sliced (eg bedlevel will also get several layers).Alternative
It might be better to extract the layer data out of the dataset (like the
.grid
data is also kept separately). This would also likely solve things for d3d4, schism, rst and other formats.The text was updated successfully, but these errors were encountered: