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/reference/process.md
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -290,9 +290,6 @@ The following options are available for all process outputs:
290
290
291
291
### accelerator
292
292
293
-
:::{versionadded} 19.09.0-edge
294
-
:::
295
-
296
293
The `accelerator` directive allows you to request hardware accelerators (e.g. GPUs) for the task execution. For example:
297
294
298
295
```nextflow
@@ -313,17 +310,23 @@ This directive is only used by certain executors. Refer to the {ref}`executor-pa
313
310
:::
314
311
315
312
:::{note}
316
-
Additional options may be required to fully enable the use of accelerators. When using containers with GPUs, you must pass the GPU drivers through to the container. For Docker, this requires the option `--gpus all` in the docker run command. For Apptainer/Singularity, this requires the option `--nv`. The specific implementation details depend on the accelerator and container type being used.
313
+
Additional options may be required to fully enable the use of accelerators. When using containers with GPUs, you must pass the GPU drivers through to the container. For Docker, this requires the option `--gpus all` in the `docker run` command. For Apptainer/Singularity, this requires the option `--nv`. The specific implementation details depend on the accelerator and container type being used.
317
314
:::
318
315
319
-
:::{note}
320
-
The accelerator `type` option depends on the target execution platform. Refer to the platform-specific documentation for details on the available accelerators:
: Specifying this directive with a number (e.g. `accelerator 4`) is equivalent to the `request` option (e.g. `accelerator request: 4`).
324
321
325
-
The accelerator `type` option is not supported for AWS Batch. You can control the accelerator type indirectly through the allowed instance types in your Compute Environment. See the [AWS Batch FAQs](https://aws.amazon.com/batch/faqs/?#GPU_Scheduling_) for more information.
326
-
:::
322
+
`type: String`
323
+
: The accelerator type.
324
+
: The meaning of this option depends on the target execution platform. Refer to the platform-specific documentation for details on the available accelerators:
: This option is not supported for AWS Batch. You can control the accelerator type indirectly through the allowed instance types in your Compute Environment. See the [AWS Batch FAQs](https://aws.amazon.com/batch/faqs/?#GPU_Scheduling_) for more information.
0 commit comments