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
A Collection can specify the variables that will be updated using the Collection.update() method. This prevents zcollection having to guess the updated variables by launching the callback over the first partition. This is very useful if the callback needs heavy auxiliary data that can only be loaded on a dask worker.
A View cannot use the same 'variables' and cannot bypass this variables inference step. It would be a great for View.update() to have the same behavior as the Collection
The text was updated successfully, but these errors were encountered:
In addition, the current view.update() needs to have the updated variables in the selected variables. This can cause a significant supplementary memory usage in case we work with delayed=False.
Hopefully, adding the 'variables' parameter will remove the need to put the updated variables in the 'selected_variables' parameters
A Collection can specify the variables that will be updated using the Collection.update() method. This prevents zcollection having to guess the updated variables by launching the callback over the first partition. This is very useful if the callback needs heavy auxiliary data that can only be loaded on a dask worker.
A View cannot use the same 'variables' and cannot bypass this variables inference step. It would be a great for View.update() to have the same behavior as the Collection
The text was updated successfully, but these errors were encountered: