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 Scene object has a method called compute that goes along with the Scene.load method's compute keyword argument. This method generates any composites that were requested by the user, but aren't currently in the Scene. This is needed when compute=False is passed to Scene.load.
The dask library also uses a .compute method on dask arrays (and xarrays backed by dask arrays). I propose that the Scene.compute method and the associated keyword should be renamed to something else to avoid confusion. Especially since we may want to include a compute method on the Scene in the future that computes all datasets in the Scene.
Possible method names and keyword argument names (please contribute):
generate_composites/generate
composite / composite
The text was updated successfully, but these errors were encountered:
Problem description
The
Scene
object has a method calledcompute
that goes along with theScene.load
method'scompute
keyword argument. This method generates any composites that were requested by the user, but aren't currently in the Scene. This is needed whencompute=False
is passed toScene.load
.The dask library also uses a
.compute
method on dask arrays (and xarrays backed by dask arrays). I propose that theScene.compute
method and the associated keyword should be renamed to something else to avoid confusion. Especially since we may want to include a compute method on the Scene in the future that computes all datasets in the Scene.Possible method names and keyword argument names (please contribute):
generate_composites
/generate
composite
/composite
The text was updated successfully, but these errors were encountered: