Discussions and preparations are ramping up to get the E4S module in good shape for PVC in Sunspot/Aurora and some feedback from teams working on the testbed would be useful to have in this process. Some basic info on how you are using (or not) the E4S module is helpful here.

1. If your application/workflow uses a Software Technology (ST) product packaged as part of E4S, then...

*) What E4S ST products does your work depend on?

*) Are you using the E4S module in JLSE (likely in work on Arcticus)?

*) If you are not using the E4S module, then why not? For example, “Using kokkos modules provided by Tim built against latest SDK”.

*) Are there other variants or options for the packages required for your work not currently provided in E4S?

2. Some feedback on which E4S Products should initially be supported on Sunspot/Aurora would be helpful. Please let us know if something critical is missing from the following *draft* list. Other ST products will certainly be supported, but we want to identify a prioritized list to ensure teams are not initially blocked waiting on something.

Data & Viz: ADIOS, Darshan, HDF5, PnetCDF, UnifyFS, VTK-m

Math Libraries: BLAS/MAGMA, Ginkgo, hypre, kokkos-kernels, PETSc/TAO, ScaLAPACK/SLATE, STRUMPACK, SUNDIALS, SuperLU, Trilinos, FFT/heFFTe

PMR: Kokkos, Legion, RAJA, Umpire, MPICH

Tools: HPCToolkit, PAPI, TAU

Any feedback here is appreciated. Feel free to reply directly to me.

chris

============

$ module load e4s

$ module avail