removing guides, references, and resource management for Summit, Spoc…

…k, Crusher, and Sunspot

docs/advanced_installation.rst

@@ -49,10 +49,6 @@ Further recommendations for selected HPC systems are given in the
 
             MPICC=mpiicc pip install mpi4py --no-binary mpi4py
 
-        On Summit, the following line is recommended (with gcc compilers)::
-
-            CC=mpicc MPICC=mpicc pip install mpi4py --no-binary mpi4py
-
     .. tab-item:: conda
 
         Install libEnsemble with Conda_ from the conda-forge channel::
@@ -116,12 +112,6 @@ Further recommendations for selected HPC systems are given in the
 
             spack info py-libensemble
 
-        On some platforms you may wish to run libEnsemble without ``mpi4py``,
-        using a serial PETSc build. This is often preferable if running on
-        the launch nodes of a three-tier system (e.g., Summit)::
-
-            spack install py-libensemble +scipy +mpmath +petsc4py ^py-petsc4py~mpi ^petsc~mpi~hdf5~hypre~superlu-dist
-
         The installation will create modules for libEnsemble and the dependent
         packages. These can be loaded by running::
 

docs/introduction_latex.rst

@@ -46,7 +46,6 @@
 .. _scipy.optimize: https://docs.scipy.org/doc/scipy/reference/optimize.html
 .. _setuptools: https://setuptools.pypa.io/en/latest/
 .. _Spack: https://spack.readthedocs.io/en/latest
-.. _Summit: https://www.olcf.ornl.gov/olcf-resources/compute-systems/summit/
 .. _Surmise: https://surmise.readthedocs.io/en/latest/index.html
 .. _SWIG: http://swig.org/
 .. _tarball: https://github.com/Libensemble/libensemble/releases/latest

docs/known_issues.rst

@@ -19,8 +19,6 @@ may occur when using libEnsemble.
 * Local comms mode (multiprocessing) may fail if MPI is initialized before
   forking processors. This is thought to be responsible for issues combining
   multiprocessing with PETSc on some platforms.
-* Remote detection of logical cores via ``LSB_HOSTS`` (e.g., Summit) returns the
-  number of physical cores as SMT info not available.
 * TCP mode does not support
   (1) more than one libEnsemble call in a given script or
   (2) the auto-resources option to the Executor.

docs/nitpicky

@@ -41,14 +41,11 @@ py:class collections.abc.Sequence
 # Internal paths that are verified importable but Sphinx can't find
 py:class libensemble.resources.platforms.Aurora
 py:class libensemble.resources.platforms.GenericROCm
-py:class libensemble.resources.platforms.Crusher
 py:class libensemble.resources.platforms.Frontier
 py:class libensemble.resources.platforms.Perlmutter
 py:class libensemble.resources.platforms.PerlmutterCPU
 py:class libensemble.resources.platforms.PerlmutterGPU
 py:class libensemble.resources.platforms.Polaris
-py:class libensemble.resources.platforms.Spock
-py:class libensemble.resources.platforms.Summit
 py:class libensemble.resources.platforms.Sunspot
 py:class libensemble.resources.rset_resources.RSetResources
 py:class libensemble.resources.env_resources.EnvResources

docs/platforms/example_scripts.rst

@@ -28,15 +28,3 @@ information about the respective systems and configuration.
     ..  literalinclude:: ../../examples/libE_submission_scripts/bebop_submit_slurm_distrib.sh
         :caption: /examples/libE_submission_scripts/bebop_submit_slurm_distrib.sh
         :language: bash
-
-.. dropdown:: Summit - On Launch Nodes with Multiprocessing
-
-    ..  literalinclude:: ../../examples/libE_submission_scripts/summit_submit_mproc.sh
-        :caption: /examples/libE_submission_scripts/summit_submit_mproc.sh
-        :language: bash
-
-.. dropdown:: Cobalt - Intermediate node with Multiprocessing
-
-    .. literalinclude:: ../../examples/libE_submission_scripts/cobalt_submit_mproc.sh
-        :caption: /examples/libE_submission_scripts/cobalt_submit_mproc.sh
-        :language: bash

docs/platforms/platforms_index.rst

@@ -80,26 +80,6 @@ per worker, and adding the manager onto the first node.
 HPC systems that only allow one application to be launched to a node at any one time,
 will not allow a distributed configuration.
 
-Systems with Launch/MOM Nodes
------------------------------
-
-Some large systems have a 3-tier node setup. That is, they have a separate set of launch nodes
-(known as MOM nodes on Cray Systems). User batch jobs or interactive sessions run on a launch node.
-Most such systems supply a special MPI runner that has some application-level scheduling
-capability (e.g., ``aprun``, ``jsrun``). MPI applications can only be submitted from these nodes. Examples
-of these systems include Summit and Sierra.
-
-There are two ways of running libEnsemble on these kinds of systems. The first, and simplest,
-is to run libEnsemble on the launch nodes. This is often sufficient if the worker's simulation
-or generation functions are not doing much work (other than launching applications). This approach
-is inherently centralized. The entire node allocation is available for the worker-launched
-tasks.
-
-However, running libEnsemble on the compute nodes is potentially more scalable and
-will better manage simulation and generation functions that contain considerable
-computational work or I/O. Therefore the second option is to use proxy task-execution
-services like Balsam_.
-
 Balsam - Externally Managed Applications
 ----------------------------------------
 
@@ -210,13 +190,11 @@ libEnsemble on specific HPC systems.
     :titlesonly:
 
     aurora
-    bebop
     frontier
-    improv
     perlmutter
     polaris
-    spock_crusher
-    summit
+    bebop
+    improv
     srun
     example_scripts