SUSE Package Hub 15 SP2 one-click install Install adios_1_13_1-gnu-openmpi2-hpc NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP2-Backports-Pool Package Hub 15 SP2 Dummy repo - this will fail adios_1_13_1-gnu-openmpi2-hpc The Adaptable IO System (ADIOS) The Adaptable IO System (ADIOS) provides a way for scientists to describe the data in their code that may need to be written, read, or processed outside of the running simulation. By providing an external to the code XML file describing the various elements, their types, and how one wishes to process them for a particular run, the routines in the host code (either FORTRAN or C) can transparently change how they process the data. SUSE Package Hub 15 SP2 one-click install Install adios_1_13_1-gnu-openmpi2-hpc NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP2-Backports-Pool Package Hub 15 SP2 Dummy repo - this will fail adios_1_13_1-gnu-openmpi2-hpc The Adaptable IO System (ADIOS) The Adaptable IO System (ADIOS) provides a way for scientists to describe the data in their code that may need to be written, read, or processed outside of the running simulation. By providing an external to the code XML file describing the various elements, their types, and how one wishes to process them for a particular run, the routines in the host code (either FORTRAN or C) can transparently change how they process the data. SUSE Package Hub 15 SP3 one-click install Install adios_1_13_1-gnu-openmpi2-hpc NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP3-Backports-Pool Package Hub 15 SP3 Dummy repo - this will fail adios_1_13_1-gnu-openmpi2-hpc The Adaptable IO System (ADIOS) The Adaptable IO System (ADIOS) provides a way for scientists to describe the data in their code that may need to be written, read, or processed outside of the running simulation. By providing an external to the code XML file describing the various elements, their types, and how one wishes to process them for a particular run, the routines in the host code (either FORTRAN or C) can transparently change how they process the data. SUSE Package Hub 15 SP3 one-click install Install adios_1_13_1-gnu-openmpi2-hpc NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-15-SP3-Backports-Pool Package Hub 15 SP3 Dummy repo - this will fail adios_1_13_1-gnu-openmpi2-hpc The Adaptable IO System (ADIOS) The Adaptable IO System (ADIOS) provides a way for scientists to describe the data in their code that may need to be written, read, or processed outside of the running simulation. By providing an external to the code XML file describing the various elements, their types, and how one wishes to process them for a particular run, the routines in the host code (either FORTRAN or C) can transparently change how they process the data.