Skip to main content

ASE2SPRKKR

ASE2SPRKKR package provide an interface that allow use of the SPR-KKR package to electronic structure calculation within Atomic Simulation Environment (abbreviated as ASE) ---Python tool that integrates the various tools for electronic structure calculation.

Installation of the package using package managers

The simplest way how to install and use the package is to install them using package managers: either pip

pip install ase2sprkkr

or conda

conda install -c ase2sprkkr ase2sprkkr

I reccomend to install beta version: there can be some bugs, but mostly it has more bugs repaired than introduced, moreover, you can enjoy new properties. The beta versions are available only through pip:

pip install --pre ase2sprkkr

To use bleading edge sources (the newest features, but you risk to encounter bugs), you can install the packages from github:

pip install git+https://github.com/ase2sprkkr/ase2sprkkr.git@develop

Further notes

In some systems, the pip utility for python3 is called pip3. It may be possible, that pip is installed, but it is not in PATH. In such case, the pip utility can be runned using python -m pip or python3 -m pip3.

If pip is not installed, you can install it using the linux distribution package manager, e.g. in Debian/Ubuntu

apt install pip3

or

zypper install pip

For the conda installation instructions, see the Anaconda documentation https://docs.anaconda.com/anaconda/install/linux/ however, for the users unexperienced with conda, the (simpler) pip way is recommended.

Install the packages from GIT (and/or source codes)

If you do not want to use public package managers as pip or conda, or you want to contribute to development, you can use GIT to obtain the package sources.

Requirements

  • Python >= 3.8
  • SPR-KKR (not checked by the installer)
  • Python packages: see the the pypoject.toml file
  • Git (to obtain the sources)

Obtaining the package using GIT

git clone https://github.com/ase2sprkkr/ase2sprkkr.git
git checkout release

The first line fetches the code of the package. The second one checks out the stable (production) version of the code.

If you want to obtain the current version of the (earlier-downloaded) code, run

git fetch
git checkout release

Alternatively, you can checkout master branch

git checkout master

to obtain a newer (not thorougly tested yet) version or develop`

git checkout develop

to obtain the bleeding edge version (feel free to try it, test it and report the bugs).

Using the package (without installing the pip/conda packages)

You can install the package from the obtained sources using

pip install .

Or, if you want to develop ase2sprkkr, it is better idea to do an [editable]{.title-ref} installation, where the package will see the changes made.

pip install --no-build-isolation --editable .

You can add --no-deps switch for a faster rebuild.

The known issues of the editable build

1. Unfortunatelly, pip is not able to install the build requirements. So if they are not installed, the previous command will fail. You can either install the dependencies manually, copying them out from pyproject.toml:

pip install scikit-build cmake ninja cython

or (which will be usefull if I add a build requirement and forgot to update this help) run the following snippet to install all the build-dependencies mentioned in pyproject.toml:

pip install tomllib
pip install --no-build-isolation $(python -c "import tomllib; print(' '.join(tomllib.load(open('pyproject.toml','rb'))['build-system']['requires']))")

2. The limitation of the editable install is, that it won't see newly created files automatically: you need run the command above again to make it notice it.

3. If the build process fail, try to remove the build directory created by the previous build (if it exists). Mostly, it happens if the --no-build-isolation switch is ommited.

Documentation of the package

The documentation is published online at https://ase2sprkkr.github.io/ase2sprkkr/

If you are using Git cloned sources, you can run

open docs/index.html

to see the (offline version of the) documentation. The documentation contains parts, that are generated from the docstrings in the source code. You can regenerate these by

make docs

Sphinx and sphinx-toolbox python packages (installable e.g. using pip) and pandoc (for generating README.md) are needed for the build.

However, the official build of Sphinx miss some attributes when it is used to build the documentation. So, till the pullrequest that corrects the Sphinx behavior will be merged into Sphinx, please use the following fork for building the documentation. https://github.com/lokik/sphinx.git

How to contribute or to report a bug

Please feel free to make a pull-request or post an issue at: https://github.com/ase2sprkkr/ase2sprkkr

Metadata

Release files for ase2sprkkr 3.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ase2sprkkr 3.6.0
File Size Uploaded Provenance Actions
ase2sprkkr-3.6.0.tar.gz 35.2 MB With provenance Details for ase2sprkkr-3.6.0.tar.gz

Release files / ase2sprkkr-3.6.0.tar.gz

Download URL ase2sprkkr-3.6.0.tar.gz
Size 35.2 MB
Tags Source
SHA-256 checksum
How to use checksums
e492a5d96a013910aee576af7a76a7db0afddb9717da423f0b21ecae62072ca5
BLAKE2b-256 checksum
How to use checksums
970554d952ea27295bcbfb184bc77def312c9c0f6509f7c5f4210e19173bfbfc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

Security for ase2sprkkr 3.6.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 1 file in this release has been uploaded with provenance metadata.

Attestation for ase2sprkkr-3.6.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

3.6.0 This release

1 release file Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page