Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs/update links to videos #1138

Merged
merged 2 commits into from
Oct 19, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/platforms/frontier.rst
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,8 @@ See :doc:`advanced installation<../advanced_installation>` for other installatio
Example
-------

Note that a video demonstration_ of this example is also available.

To run the :doc:`forces_gpu<../tutorials/forces_gpu_tutorial>` tutorial on Frontier.

To obtain the example you can git clone libEnsemble - although only
Expand Down Expand Up @@ -72,3 +74,4 @@ To see GPU usage, ssh into the node you are on in another window and run::
.. _Frontier: https://docs.olcf.ornl.gov/systems/frontier_user_guide.html
.. _Slurm: https://slurm.schedmd.com/
.. _python_on_frontier: https://www.olcf.ornl.gov/wp-content/uploads/2-16-23_python_on_frontier.pdf
.. _demonstration: https://youtu.be/H2fmbZ6DnVc
9 changes: 2 additions & 7 deletions docs/tutorials/forces_gpu_tutorial.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,7 @@ In the first example, each worker will be using one GPU. The code will assign th
GPUs available to each worker, using the appropriate method. This works on systems
using **Nvidia**, **AMD**, and **Intel** GPUs without modifying the scripts.

Videos demonstrate running this example on Perlmutter_, Spock_, and Polaris_.
*The first two videos are from an earlier release - you no longer need to change
particle count or modify the `forces.c` file).*. Also, on Polaris, it is no
longer necessary to change the MPI runner.
A video demonstrates running this example on Frontier_.

Simulation function
-------------------
Expand Down Expand Up @@ -308,9 +305,7 @@ where ``SLURM_EXACT`` is set to help prevent resource conflicts on each node.
.. _forces_gpu: https://github.com/Libensemble/libensemble/blob/develop/libensemble/tests/scaling_tests/forces/forces_gpu
.. _forces.c: https://github.com/Libensemble/libensemble/blob/develop/libensemble/tests/scaling_tests/forces/forces_app/forces.c
.. _build_forces.sh: https://github.com/Libensemble/libensemble/blob/develop/libensemble/tests/scaling_tests/forces/forces_app/build_forces.sh
.. _Perlmutter: https://www.youtube.com/watch?v=Av8ctYph7-Y
.. _Spock: https://www.youtube.com/watch?v=XHXcslDORjU
.. _Polaris: https://youtu.be/Ff0dYYLQzoU
.. _Frontier: https://youtu.be/H2fmbZ6DnVc
.. _run_libe_forces.py: https://github.com/Libensemble/libensemble/blob/develop/libensemble/tests/scaling_tests/forces/forces_gpu/run_libe_forces.py
.. _forces_gpu_var_resources: https://github.com/Libensemble/libensemble/blob/develop/libensemble/tests/scaling_tests/forces/forces_gpu_var_resources/run_libe_forces.py
.. _forces_multi_app: https://github.com/Libensemble/libensemble/blob/develop/libensemble/tests/scaling_tests/forces/forces_multi_app/run_libe_forces.py