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
Copy file name to clipboardExpand all lines: docs/user/basics/wflow_decorators.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,20 +80,16 @@ A `#!Python @subflow` in quacc is any workflow that returns a list of job output
80
80
81
81
=== "Jobflow"
82
82
83
-
Take a moment to read the Jobflow documentation's [Quick Start](https://materialsproject.github.io/jobflow/tutorials/1-quickstart.html) to get a sense of how Jobflow works. Namely, you should understand the `Job` and `Flow` definitions, which describe individual compute tasks and workflows, respectively.
83
+
Take a moment to read the Jobflow documentation's [Quick Start](https://materialsproject.github.io/jobflow/tutorials/1-quickstart.html) to get a sense of how Jobflow works. Namely, you should understand the concept of a `#!Python @job` and a `#!Python @flow`, which describe individual compute tasks and workflows, respectively.
84
84
85
85
<center>
86
86
87
-
| Quacc | Jobflow |
88
-
| ------------------- | --------------- |
89
-
| `#!Python @job` | `#!Python @job` |
90
-
| `#!Python @flow` | N/A |
91
-
| `#!Python @subflow` | N/A |
87
+
| Quacc | Jobflow |
88
+
| ------------------- | ---------------- |
89
+
| `#!Python @job` | `#!Python @job` |
90
+
| `#!Python @flow` | `#!Python @flow` |
91
+
| `#!Python @subflow` | `#!Python @job` |
92
92
93
93
</center>
94
94
95
-
!!! Warning
96
-
97
-
Due to the difference in how Jobflow handles workflows compared to other supported workflow engines, any quacc recipes that have been pre-defined with a `#!Python @flow` or `#!Python @subflow` decorator (i.e. have `_flow` in the name) cannot be run directly with Jobflow.
98
-
99
95
The quacc descriptors are drop-in replacements for the specified workflow engine analogue, which we will use for the remainder of the tutorials. Based on the value for the `WORKFLOW_ENGINE` global variable in your [quacc settings](../settings/settings.md), the appropriate decorator will be automatically selected. If the `WORKFLOW_ENGINE` setting is set to `None` (i.e. `quacc set WORKFLOW_ENGINE None`), the decorators will have no effect on the underlying function.
Copy file name to clipboardExpand all lines: docs/user/basics/wflow_overview.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,10 +87,6 @@ Everyone's computing needs are different, so we ensured that quacc is interopera
87
87
88
88
[Jobflow](https://github.com/materialsproject/jobflow) is developed and maintained by the Materials Project team at Lawrence Berkeley National Laboratory and serves as a seamless interface to [FireWorks](https://github.com/materialsproject/fireworks) or [Jobflow Remote](https://github.com/Matgenix/jobflow-remote) for dispatching and monitoring compute jobs.
89
89
90
-
!!! Warning
91
-
92
-
Jobflow is not yet compatible with the `#!Python @flow` or `#!Python @subflow` decorators used in many quacc recipes and so should only be used if necessary. See [this issue](https://github.com/Quantum-Accelerators/quacc/issues/1061) to track the progress of this enhancement.
Copy file name to clipboardExpand all lines: docs/user/wflow_engine/wflow_engines1.md
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -266,6 +266,20 @@ graph LR
266
266
267
267
=== "Jobflow"
268
268
269
-
!!! Warning
269
+
```python
270
+
import jobflow as jf
271
+
from ase.build import bulk
272
+
from quacc.recipes.emt.slabs import bulk_to_slabs_flow
273
+
274
+
# Define the Atoms object
275
+
atoms = bulk("Cu")
270
276
271
-
Due to the difference in how Jobflow handles workflows (particularly dynamic ones) compared to other supported workflow engines, any quacc recipes that have been pre-defined with a `#!Python @flow` decorator (i.e. have `_flow` in the name) cannot be run directly with Jobflow. Rather, a Jobflow-specific `Flow` needs to be constructed by the user.
Due to the difference in how Jobflow handles workflows (particularly dynamic ones) compared to other supported workflow engines, any quacc recipes that have been pre-defined with a `#!Python @flow` decorator (i.e. have `_flow` in the name) cannot be run directly with Jobflow. Rather, a Jobflow-specific `Flow` needs to be constructed by the user.
0 commit comments