Skip to content

Commit

Permalink
replace some 'Frontier' with 'Adastra' in adastra documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
lucafedeli88 committed Jul 17, 2023
1 parent c8ba20f commit bb11d73
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions Docs/source/install/hpc/adastra.rst
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Adastra login nodes).

.. important::

Now, and as the first step on future logins to Frontier, activate these environment settings:
Now, and as the first step on future logins to Adastra, activate these environment settings:

.. code-block:: bash
Expand Down Expand Up @@ -97,14 +97,14 @@ Use the following :ref:`cmake commands <building-cmake>` to compile:
cmake --build build_adastra -j 16 --target pip_install
**That's it!**
The WarpX application executables are now in ``$HOME/src/warpx/build_frontier/bin/`` and we installed the ``pywarpx`` Python module.
The WarpX application executables are now in ``$HOME/src/warpx/build_adastra/bin/`` and we installed the ``pywarpx`` Python module.

Now, you can :ref:`submit Adstra compute jobs <running-cpp-adastra>` for WarpX :ref:`Python (PICMI) scripts <usage-picmi>` (:ref:`example scripts <usage-examples>`).
Or, you can use the WarpX executables to submit Adastra jobs (:ref:`example inputs <usage-examples>`).
For executables, you can reference their location in your :ref:`job script <running-cpp-adastra>` .


.. _building-frontier-update:
.. _building-adastra-update:

Update WarpX & Dependencies
---------------------------
Expand Down

0 comments on commit bb11d73

Please sign in to comment.