Skip to content

Commit b08f537

Browse files
committed
remove device from docs wrt DragonRunPolicy
1 parent d6350e5 commit b08f537

File tree

1 file changed

+4
-19
lines changed

1 file changed

+4
-19
lines changed

doc/dragon.rst

Lines changed: 4 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -68,25 +68,10 @@ For more information on HPC launchers, visit the :ref:`Run Settings<run_settings
6868
Hardware Pinning
6969
================
7070

71-
Dragon also enables users to specify hardware constraints using ``DragonRunSettings``. For
72-
example, you may may configure the run settings to require that nodes executing the
73-
``Model`` support the `"gpu"` feature.
74-
75-
.. code-block:: python
76-
77-
# Because "dragon" was specified as the launcher during Experiment initialization,
78-
# create_run_settings will return a DragonRunSettings object
79-
rs = exp.create_run_settings(exe="mpi_app",
80-
exe_args=["--option", "value"],
81-
env_vars={"MYVAR": "VALUE"})
82-
83-
# Specify that the nodes features must include a GPU
84-
rs.set_feature("gpu")
85-
86-
For more fine-grained control, CPU and GPU affinity can be specified using the
87-
``DragonRunSettings`` object. The following example demonstrates how to specify
88-
CPU affinity and GPU affinities simultaneously. Note that affinities are passed
89-
as a list of device indices.
71+
Dragon also enables users to specify hardware constraints using ``DragonRunSettings``. CPU
72+
and GPU affinity can be specified using the ``DragonRunSettings`` object. The following
73+
example demonstrates how to specify CPU affinity and GPU affinities simultaneously. Note
74+
that affinities are passed as a list of device indices.
9075

9176
.. code-block:: python
9277

0 commit comments

Comments
 (0)