How to Install and Uninstall adios_1_13_1-gnu-openmpi4-hpc Package on openSuSE Tumbleweed
Last updated: November 27,2024
1. Install "adios_1_13_1-gnu-openmpi4-hpc" package
This is a short guide on how to install adios_1_13_1-gnu-openmpi4-hpc on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
adios_1_13_1-gnu-openmpi4-hpc
Copied
2. Uninstall "adios_1_13_1-gnu-openmpi4-hpc" package
This guide let you learn how to uninstall adios_1_13_1-gnu-openmpi4-hpc on openSuSE Tumbleweed:
$
sudo zypper remove
adios_1_13_1-gnu-openmpi4-hpc
Copied
3. Information about the adios_1_13_1-gnu-openmpi4-hpc package on openSuSE Tumbleweed
Information for package adios_1_13_1-gnu-openmpi4-hpc:
------------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : adios_1_13_1-gnu-openmpi4-hpc
Version : 1.13.1-7.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 3.4 MiB
Installed : No
Status : not installed
Source package : adios_1_13_1-gnu-openmpi4-hpc-1.13.1-7.1.src
Upstream URL : https://www.olcf.ornl.gov/center-projects/adios/
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 : openSUSE-Tumbleweed-Oss
Name : adios_1_13_1-gnu-openmpi4-hpc
Version : 1.13.1-7.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 3.4 MiB
Installed : No
Status : not installed
Source package : adios_1_13_1-gnu-openmpi4-hpc-1.13.1-7.1.src
Upstream URL : https://www.olcf.ornl.gov/center-projects/adios/
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.