Documentation |
|---|
PyARPES
PyARPES simplifies the analysis and collection of angle-resolved photoemission spectroscopy (ARPES) and emphasizes
modern, best practices for data science
support for a standard library of ARPES analysis tools mirroring those available in Igor Pro
interactive and extensible analysis tools
It supports a variety of data formats from synchrotron and laser-ARPES sources including ARPES at the Advanced Light Source (ALS), the data produced by Scienta Omicron GmbH’s “SES Wrapper”, data and experiment files from Igor Pro, NeXuS files, and others.
To learn more about installing and using PyARPES in your analysis or data collection application, visit the documentation site.
PyARPES is currently developed by Conrad Stansbury of the Lanzara Group at the University of California, Berkeley.
Installation
PyARPES can be installed from source, or using either pip or conda into a Python 3.6 or 3.7 environment. conda is preferred as a package manager in order to facilitate installing the libraries for reading HDF and NetCDF files.
Pip installation
pip install arpes
Conda installation
PyARPES is distributed through the arpes Anaconda channel, but includes dependencies through conda-forge. Please make sure not to put conda-forge above the main channel priority, as this can cause issues with installing BLAS. A minimal install looks like
conda config --append channels conda-forge conda install -c arpes -c conda-forge arpes
Local installation from source
If you want to modify the source for PyARPES as you use it, you might prefer a local installation from source. Details can be found on the documentation site.
Suggested steps
Clone or duplicate the folder structure in the repository arpes-analysis-scaffold, skipping the example folder and data if you like
Install and configure standard tools like Jupyter or Jupyter Lab. Notes on installing and configuring Jupyter based installations can be found in jupyter.md
Explore the documentation and example notebooks at the documentation site.
Contact
Questions, difficulties, and suggestions can be directed to Conrad Stansbury (chstan@berkeley.edu) or added to the repository as an issue. In the case of trouble, also check the FAQ.
Copyright © 2018-2019 by Conrad Stansbury, all rights reserved.
1 maintainer
Metadata
1 maintainer
Release files for arpes 3.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| arpes-3.0.1.tar.gz | 28.6 MB | Without provenance | Details for arpes-3.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| arpes-3.0.1-py3-none-any.whl | Python 3 | none | any | Details for arpes-3.0.1-py3-none-any.whl |
Total release size: 36.1 MB
Release files / arpes-3.0.1.tar.gz
| Download URL | arpes-3.0.1.tar.gz |
|---|---|
| Size | 28.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a19af44494c4ae89197c22d505ec12ae384e29bcf04c60192cb1115d5ad208fc
|
|
BLAKE2b-256 checksum How to use checksums |
2fe523eadf9f8c352342dca17576bee9bdbe216ceb239186ffa3d36e86f16839
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Release files / arpes-3.0.1-py3-none-any.whl
| Download URL | arpes-3.0.1-py3-none-any.whl |
|---|---|
| Size | 7.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
12b1e0609da12c021656804bac860635ff7a9fa19f6248b12d74d6686d147950
|
|
BLAKE2b-256 checksum How to use checksums |
662e408d6a9be1f387371f68dd66ef85893bd8f5e8b7d3da3152619be3eeee31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Security for arpes 3.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.
