zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
4,478 Commits 246 Branches 186 Tags 666 MiB
Python 97.3%
Shell 2.1%
C 0.2%
3aaa077c9f
Go to file
Axel Huebl 3aaa077c9f
libSplash: Add Spack Package 
Adds a package for
[libSplash](https://github.com/ComputationalRadiationPhysics/libSplash),
a high-level library around serial and parallel HDF5 for regular
grids and particle data sets.

```
libSplash aims at developing a HDF5-based I/O library for HPC
simulations. It is created as an easy-to-use frontend for the
standard HDF5 library with support for MPI processes in a cluster
environment. While the standard HDF5 library provides detailed
low-level control, libSplash simplifies tasks commonly found in
large-scale HPC simulations, such as iter- ative computations
and MPI distributed processes.
```

libSplash is a dependency for [PIConGPU](http://picongpu.hzdr.de),
an open-source, many-core, fully-relativistic particle-in-cell
code and further software developed at
[Helmholz-Zentrum Dresden - Rossendorf](https://www.hzdr.de).

libSplash builds in two versions, one without MPI writing
domain-decomposed posix-style HDF5 files per process and one
(default) with MPI and MPI-I/O ("parallel HDF5") support
aggregating into a single file per MPI communicator.

libSplash is used in conjunction with
[openPMD](http://openPMD.org), see also
[github.com/openPMD/](https://github.com/openPMD/).
2016-08-30 12:42:39 +02:00
bin Change spack --profile sort key for 2.6 compatibility. (#1656) 2016-08-29 09:56:54 -07:00
etc/spack/defaults Add "default" configuration scope. 2016-07-19 17:10:17 -07:00
lib/spack Move all documentation generation into conf.py 2016-08-30 00:47:04 -07:00
share/spack Run flake8 checks on new untracked files (#1510) 2016-08-28 19:35:09 -07:00
var/spack libSplash: Add Spack Package 2016-08-30 12:42:39 +02:00
.coveragerc Move args to .coveragerc 2016-05-10 00:51:08 -07:00
.flake8 Make Spack core PEP8 compliant. 2016-08-10 16:33:37 -07:00
.gitignore Add a ProviderIndex cache. 2016-08-08 21:04:23 -07:00
.mailmap Update mailmap 2016-02-03 11:47:48 -07:00
.travis.yml qa : fixes #1370 (no flake8 on python 2.6, coveralls only python 2.7) 2016-07-30 18:49:23 +02:00
LICENSE Correct LLNL LGPL license template for clarity. 2016-05-11 21:22:25 -07:00
README.md and the missing word is... (#1628) 2016-08-25 02:46:12 -07:00

README.md

image

Build Status Coverage Status

Spack is a package management tool designed to support multiple versions and configurations of software on a wide variety of platforms and environments. It was designed for large supercomputing centers, where many users and application teams share common installations of software on clusters with exotic architectures, using libraries that do not have a standard ABI. Spack is non-destructive: installing a new version does not break existing installations, so many configurations can coexist on the same system.

Most importantly, Spack is simple. It offers a simple spec syntax so that users can specify versions and configuration options concisely. Spack is also simple for package authors: package files are written in pure Python, and specs allow package authors to write a single build script for many different builds of the same package.

See the Feature Overview for examples and highlights.

To install spack and install your first package:

$ git clone https://github.com/llnl/spack.git
$ cd spack/bin
$ ./spack install libelf

Documentation

Full documentation for Spack is the first place to look.

See also:

Get Involved!

Spack is an open source project. Questions, discussion, and contributions are welcome. Contributions can be anything from new packages to bugfixes, or even new core features.

Mailing list

If you are interested in contributing to spack, the first step is to join the mailing list. We're using a Google Group for this, and you can join it here:

Contributions

Contributing to Spack is relatively easy. Just send us a pull request. When you send your request, make develop the destination branch on the Spack repository.

Before you send a PR, your code should pass the following checks:

  • Your contribution will need to pass the spack test command. Run this before submitting your PR.

  • Also run the share/spack/qa/run-flake8 script to check for PEP8 compliance. To encourage contributions and readability by a broad audience, Spack uses the PEP8 coding standard with a few exceptions.

We enforce these guidelines with Travis CI.

Spack uses a rough approximation of the Git Flow branching model. The develop branch contains the latest contributions, and master is always tagged and points to the latest stable release.

Authors

Many thanks go to Spack's contributors.

Spack was originally written by Todd Gamblin, tgamblin@llnl.gov.

Citing Spack

If you are referencing Spack in a publication, please cite the following paper:

Release

Spack is released under an LGPL license. For more details see the LICENSE file.

LLNL-CODE-647188