From c7dd41a49410f612fd5d0556ca9f1ae8ad026474 Mon Sep 17 00:00:00 2001 From: "Andrew S. Rosen" Date: Wed, 13 Dec 2023 21:23:19 -0800 Subject: [PATCH] Update wflow_syntax.md --- docs/user/basics/wflow_syntax.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user/basics/wflow_syntax.md b/docs/user/basics/wflow_syntax.md index 3d8d57fcda..529348a95c 100644 --- a/docs/user/basics/wflow_syntax.md +++ b/docs/user/basics/wflow_syntax.md @@ -38,7 +38,7 @@ To help enable interoperability between workflow engines, quacc offers a unified === "Dask" - Take a moment to read the Dask Delayed documentation [overview page](https://docs.dask.org/en/stable/delayed.html) to get a sense of how the Dask decorators works and the Dask Distributed [quickstart page](https://distributed.dask.org/en/stable/quickstart.html) to understand how to submit tasks to a Dask cluster. Namely, you should understand the `@delayed` decorator and how to interface with the `Client`. + Take a moment to read the Dask Delayed documentation [overview page](https://docs.dask.org/en/stable/delayed.html) to get a sense of how the Dask decorators works and the Dask Distributed [quickstart page](https://distributed.dask.org/en/stable/quickstart.html) to understand how to submit tasks to a Dask cluster. Namely, you should understand the `#!Python @delayed` decorator and how to interface with the `Client`.
@@ -238,7 +238,7 @@ graph LR 3. This returns a `Delayed` object. A reference is returned. - 4. There are multiple ways to resolve a `Delayed` object. Here, `#!Python client.compute(delayed)` will return a `Future` object, which can be resolved with `.result()`. The `.result()` call will block until the workflow is complete and return the result. As an alternative, you could also use `#!Python delayed.compute()` to dispatch and resolve the `Delayed` object in one command. Similarly, you could use `dask.compute(delayed)[0]`, where the `[0]` indexing is needed because `#!Python dask.compute()` alwaays returns a tuple. + 4. There are multiple ways to resolve a `Delayed` object. Here, `#!Python client.compute(delayed)` will return a `Future` object, which can be resolved with `.result()`. The `.result()` call will block until the workflow is complete and return the result. As an alternative, you could also use `#!Python delayed.compute()` to dispatch and resolve the `Delayed` object in one command. Similarly, you could use `#!Python dask.compute(delayed)[0]`, where the `[0]` indexing is needed because `#!Python dask.compute()` alwaays returns a tuple. === "Redun"