Data

Tools

Indexes

Applications

Experiments

Open Source Science

spack

https://github.com/openbraininstitute/spack

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • ○
    CITATION.cff file
  • ✓
    codemeta.json file
    Found codemeta.json file
  • ✓
    .zenodo.json file
    Found .zenodo.json file
  • ○
    DOI references
  • ○
    Academic publication links
  • ○
    Academic email domains
  • ○
    Institutional organization owner
  • ○
    JOSS paper metadata
  • ○
    Scientific vocabulary similarity
    Low similarity (13.6%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

Basic Info
  • Host: GitHub
  • Owner: openbraininstitute
  • License: other
  • Language: Python
  • Default Branch: develop
  • Size: 210 MB
Statistics
  • Stars: 0
  • Watchers: 0
  • Forks: 0
  • Open Issues: 1
  • Releases: 0
Created over 1 year ago · Last pushed 10 months ago
Metadata Files
Readme Changelog Contributing License Code of conduct Citation Codeowners Security

README.md

The BlueBrain Spack Deployment

Official documentation below.

The concepts of our deployment are described in Deployment Concepts, and deployment duties in Deployment Workflows.

For some common issues, please see the FAQ. Further documentation:

Old documentation about BlueBrain5 (BB5):

Spack Spack

Official upstream documentation [![Unit Tests](https://github.com/spack/spack/workflows/linux%20tests/badge.svg)](https://github.com/spack/spack/actions) [![Bootstrapping](https://github.com/spack/spack/actions/workflows/bootstrap.yml/badge.svg)](https://github.com/spack/spack/actions/workflows/bootstrap.yml) [![codecov](https://codecov.io/gh/spack/spack/branch/develop/graph/badge.svg)](https://codecov.io/gh/spack/spack) [![Containers](https://github.com/spack/spack/actions/workflows/build-containers.yml/badge.svg)](https://github.com/spack/spack/actions/workflows/build-containers.yml) [![Read the Docs](https://readthedocs.org/projects/spack/badge/?version=latest)](https://spack.readthedocs.io) [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black) [![Slack](https://slack.spack.io/badge.svg)](https://slack.spack.io) [![Matrix](https://img.shields.io/matrix/spack-space%3Amatrix.org?label=Matrix)](https://matrix.to/#/#spack-space:matrix.org) Spack is a multi-platform package manager that builds and installs multiple versions and configurations of software. It works on Linux, macOS, and many supercomputers. Spack is non-destructive: installing a new version of a package does not break existing installations, so many configurations of the same package can coexist. Spack offers a simple "spec" syntax that allows users to specify versions and configuration options. Package files are written in pure Python, and specs allow package authors to write a single script for many different builds of the same package. With Spack, you can build your software *all* the ways you want to. See the [Feature Overview](https://spack.readthedocs.io/en/latest/features.html) for examples and highlights. To install spack and your first package, make sure you have Python. Then: $ git clone -c feature.manyFiles=true https://github.com/spack/spack.git $ cd spack/bin $ ./spack install zlib Documentation ---------------- [**Full documentation**](https://spack.readthedocs.io/) is available, or run `spack help` or `spack help --all`. For a cheat sheet on Spack syntax, run `spack help --spec`. Tutorial ---------------- We maintain a [**hands-on tutorial**](https://spack.readthedocs.io/en/latest/tutorial.html). It covers basic to advanced usage, packaging, developer features, and large HPC deployments. You can do all of the exercises on your own laptop using a Docker container. Feel free to use these materials to teach users at your organization about Spack. Community ------------------------ Spack is an open source project. Questions, discussion, and contributions are welcome. Contributions can be anything from new packages to bugfixes, documentation, or even new core features. Resources: * **Slack workspace**: [spackpm.slack.com](https://spackpm.slack.com). To get an invitation, visit [slack.spack.io](https://slack.spack.io). * **Matrix space**: [#spack-space:matrix.org](https://matrix.to/#/#spack-space:matrix.org): [bridged](https://github.com/matrix-org/matrix-appservice-slack#matrix-appservice-slack) to Slack. * [**Github Discussions**](https://github.com/spack/spack/discussions): not just for discussions, but also Q&A. * **Mailing list**: [groups.google.com/d/forum/spack](https://groups.google.com/d/forum/spack) * **Twitter**: [@spackpm](https://twitter.com/spackpm). Be sure to `@mention` us! Contributing ------------------------ Contributing to Spack is relatively easy. Just send us a [pull request](https://help.github.com/articles/using-pull-requests/). When you send your request, make ``develop`` the destination branch on the [Spack repository](https://github.com/spack/spack). Your PR must pass Spack's unit tests and documentation tests, and must be [PEP 8](https://www.python.org/dev/peps/pep-0008/) compliant. We enforce these guidelines with our CI process. To run these tests locally, and for helpful tips on git, see our [Contribution Guide](https://spack.readthedocs.io/en/latest/contribution_guide.html). Spack's `develop` branch has the latest contributions. Pull requests should target `develop`, and users who want the latest package versions, features, etc. can use `develop`. Releases -------- For multi-user site deployments or other use cases that need very stable software installations, we recommend using Spack's [stable releases](https://github.com/spack/spack/releases). Each Spack release series also has a corresponding branch, e.g. `releases/v0.14` has `0.14.x` versions of Spack, and `releases/v0.13` has `0.13.x` versions. We backport important bug fixes to these branches but we do not advance the package versions or make other changes that would change the way Spack concretizes dependencies within a release branch. So, you can base your Spack deployment on a release branch and `git pull` to get fixes, without the package churn that comes with `develop`. The latest release is always available with the `releases/latest` tag. See the [docs on releases](https://spack.readthedocs.io/en/latest/developer_guide.html#releases) for more details. Code of Conduct ------------------------ Please note that Spack has a [**Code of Conduct**](.github/CODE_OF_CONDUCT.md). By participating in the Spack community, you agree to abide by its rules. Authors ---------------- Many thanks go to Spack's [contributors](https://github.com/spack/spack/graphs/contributors). Spack was created by Todd Gamblin, tgamblin@llnl.gov. ### Citing Spack If you are referencing Spack in a publication, please cite the following paper: * Todd Gamblin, Matthew P. LeGendre, Michael R. Collette, Gregory L. Lee, Adam Moody, Bronis R. de Supinski, and W. Scott Futral. [**The Spack Package Manager: Bringing Order to HPC Software Chaos**](https://www.computer.org/csdl/proceedings/sc/2015/3723/00/2807623.pdf). In *Supercomputing 2015 (SC15)*, Austin, Texas, November 15-20 2015. LLNL-CONF-669890. On GitHub, you can copy this citation in APA or BibTeX format via the "Cite this repository" button. Or, see the comments in `CITATION.cff` for the raw BibTeX. License ---------------- Spack is distributed under the terms of both the MIT license and the Apache License (Version 2.0). Users may choose either license, at their option. All new contributions must be made under both the MIT and Apache-2.0 licenses. See [LICENSE-MIT](https://github.com/spack/spack/blob/develop/LICENSE-MIT), [LICENSE-APACHE](https://github.com/spack/spack/blob/develop/LICENSE-APACHE), [COPYRIGHT](https://github.com/spack/spack/blob/develop/COPYRIGHT), and [NOTICE](https://github.com/spack/spack/blob/develop/NOTICE) for details. SPDX-License-Identifier: (Apache-2.0 OR MIT) LLNL-CODE-811652

Owner

  • Name: Open Brain Institute
  • Login: openbraininstitute
  • Kind: organization

GitHub Events

Total
  • Delete event: 14
  • Issue comment event: 47
  • Member event: 2
  • Push event: 59
  • Pull request review comment event: 15
  • Pull request review event: 31
  • Pull request event: 36
  • Create event: 220
Last Year
  • Delete event: 14
  • Issue comment event: 47
  • Member event: 2
  • Push event: 59
  • Pull request review comment event: 15
  • Pull request review event: 31
  • Pull request event: 36
  • Create event: 220

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 2
  • Total pull requests: 18
  • Average time to close issues: about 3 hours
  • Average time to close pull requests: 4 days
  • Total issue authors: 1
  • Total pull request authors: 4
  • Average comments per issue: 0.0
  • Average comments per pull request: 1.17
  • Merged pull requests: 12
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 2
  • Pull requests: 18
  • Average time to close issues: about 3 hours
  • Average time to close pull requests: 4 days
  • Issue authors: 1
  • Pull request authors: 4
  • Average comments per issue: 0.0
  • Average comments per pull request: 1.17
  • Merged pull requests: 12
  • Bot issues: 0
  • Bot pull requests: 0
View more stats
Top Authors
Issue Authors
  • cattabiani (1)
Pull Request Authors
  • cattabiani (11)
  • WeinaJi (3)
  • heerener (2)
  • jplanasc (2)
Top Labels
Issue Labels
Pull Request Labels

Dependencies

.github/workflows/audit.yaml actions
  • actions/checkout b4ffde65f46336ab88eb53be808477a3936bae11 composite
  • actions/setup-python 65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236 composite
  • codecov/codecov-action eaaf4bedf32dbdc6b720b63067d99c4d77d6047d composite
.github/workflows/bootstrap.yml actions
  • actions/checkout b4ffde65f46336ab88eb53be808477a3936bae11 composite
  • actions/setup-python 65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236 composite
.github/workflows/build-containers.yml actions
  • actions/checkout b4ffde65f46336ab88eb53be808477a3936bae11 composite
  • actions/upload-artifact a8a3f3ad30e3422c9c7b888a15615d19a852ae32 composite
  • docker/build-push-action 0565240e2d4ab88bba5387d719585280857ece09 composite
  • docker/login-action 343f7c4344506bcbf9b4de18042ae17996df046d composite
  • docker/metadata-action 96383f45573cb7f253c731d3b3ab81c87ef81934 composite
  • docker/setup-buildx-action f95db51fddba0c2d1ec667646a06c2ce06100226 composite
  • docker/setup-qemu-action 68827325e0b33c7199eb31dd4e31fbe9023e06e3 composite
.github/workflows/ci.yaml actions
  • actions/checkout b4ffde65f46336ab88eb53be808477a3936bae11 composite
  • dorny/paths-filter 4512585405083f25c027a35db413c2b3b9006d50 composite
.github/workflows/generate_spack_yaml_containerize.sh actions
.github/workflows/nightly-win-builds.yml actions
  • actions/checkout b4ffde65f46336ab88eb53be808477a3936bae11 composite
  • actions/setup-python 65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236 composite
.github/workflows/unit_tests.yaml actions
  • actions/checkout b4ffde65f46336ab88eb53be808477a3936bae11 composite
  • actions/setup-python 65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236 composite
  • codecov/codecov-action eaaf4bedf32dbdc6b720b63067d99c4d77d6047d composite
.github/workflows/valid-style.yml actions
  • actions/checkout b4ffde65f46336ab88eb53be808477a3936bae11 composite
  • actions/setup-python 65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236 composite
.github/workflows/validate-commit-message.yaml actions
  • actions/checkout v3 composite
  • actions/setup-python v4 composite
  • thollander/actions-comment-pull-request v2 composite
.github/workflows/windows_python.yml actions
  • actions/checkout b4ffde65f46336ab88eb53be808477a3936bae11 composite
  • actions/setup-python 65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236 composite
  • codecov/codecov-action eaaf4bedf32dbdc6b720b63067d99c4d77d6047d composite
docker/Dockerfile docker
  • ubuntu 18.04 build
share/spack/docker/package-index/Dockerfile docker
  • nginx mainline-alpine build
  • ubuntu 18.04 build
share/spack/docs/docker/module-file-tutorial/Dockerfile docker
  • ubuntu 16.04 build
share/spack/templates/container/Dockerfile docker
  • {{ latest build
.github/workflows/style/requirements.txt pypi
  • black ==23.10.1
  • clingo ==5.6.2
  • flake8 ==6.1.0
  • isort ==5.12.0
  • mypy ==1.6.1
  • types-six ==1.16.21.9
  • vermin ==1.5.2
bluebrain/notifications/requirements.txt pypi
  • click *
  • requests *
lib/spack/docs/requirements.txt pypi
  • black ==23.10.1
  • docutils ==0.18.1
  • flake8 ==6.1.0
  • isort ==5.12.0
  • mypy ==1.6.1
  • pygments ==2.16.1
  • pytest ==7.4.3
  • python-levenshtein ==0.23.0
  • sphinx ==7.2.6
  • sphinx-rtd-theme ==1.3.0
  • sphinx_design ==0.5.0
  • sphinxcontrib-programoutput ==0.17
  • urllib3 ==2.0.7
pyproject.toml pypi
  • clingo *
  • setuptools *