How to Install and Uninstall adios_1_13_1-gnu-openmpi3-hpc Package on openSUSE Leap
Last updated: November 23,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "adios_1_13_1-gnu-openmpi3-hpc" package
Please follow the guidelines below to install adios_1_13_1-gnu-openmpi3-hpc on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
adios_1_13_1-gnu-openmpi3-hpc
Copied
2. Uninstall "adios_1_13_1-gnu-openmpi3-hpc" package
Please follow the step by step instructions below to uninstall adios_1_13_1-gnu-openmpi3-hpc on openSUSE Leap:
$
sudo zypper remove
adios_1_13_1-gnu-openmpi3-hpc
Copied
3. Information about the adios_1_13_1-gnu-openmpi3-hpc package on openSUSE Leap
Information for package adios_1_13_1-gnu-openmpi3-hpc:
------------------------------------------------------
Repository : Main Repository
Name : adios_1_13_1-gnu-openmpi3-hpc
Version : 1.13.1-10.17
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 6,6 MiB
Installed : No
Status : not installed
Source package : adios_1_13_1-gnu-openmpi3-hpc-1.13.1-10.17.src
Summary : The Adaptable IO System (ADIOS)
Description :
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.
------------------------------------------------------
Repository : Main Repository
Name : adios_1_13_1-gnu-openmpi3-hpc
Version : 1.13.1-10.17
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 6,6 MiB
Installed : No
Status : not installed
Source package : adios_1_13_1-gnu-openmpi3-hpc-1.13.1-10.17.src
Summary : The Adaptable IO System (ADIOS)
Description :
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.