Solid-State-Physics Tools (ssptools)
Preamble
This package contains classes and scripts developed by the author for his work in solid state physics, mainly for working with the input and output of the Vienna Ab initio Simulation Package. These tools are very specific in their use. The primary purpose of having them on GitHub and the PyPI is to enable easier editing of scripts while working on multiple devices. However you may still find some scipts to be of use to you.
Scripts
2POS.py
Uses read and write from ase to convert a file containing a crystal structure to POSCAR or any other file-type acceptable to ase.
2POS.py <input-filename> <output-filename (optional)>
appendKPaths.py
Appends kpoints specified in a json file to KPOINTS input of vasp.
To perform electronic band structure calculations with vasp it is sometimes required to use a combined KPOINTS file that contains both
a $\Gamma$-centered grid and the bandpaths along which the dispersion should be calculated. The kpoints along the bandpaths will be appended
to an existing KPOINTS files which already contains the grid-points in multiples of the reciprocal lattice vectors as a list. So far
only "type": reciprocal is implemented. To get the list you can run vasp with a "normal" grid-KPOINTS and immediately abort it.
This will create IBZKPT, which contains the list. The json file
containing the bandpath-kpoints should be formulated like this:
{
"type": "reciprocal",
"straights": [
{
"endpoint": [0, 0, 0],
"npoints": 1,
"name": "$\Gamma$"
},
{
"endpoint": [0.333333, 0.333333, 0.],
"npoints": 40,
"name": "K"
},
{
"endpoint": [0.333333, 0.333333, 0.5],
"npoints": 40,
"name": "K"
}
]
}
The band path is given in straights. They are defined by an endpoint, its name and the number of points along it.
The startpoint of a straight is the endpoint of the previous straight in the list. Therefore the first straight must have "npoints": 1. "name"
is the label given to the xticks when plotted using plotBS.py.\
appendKPaths.py <QPOINTS.json> <KPOINTS>
compareEV.py
Compares the eigenvalues of all kpoints between two vasprun.xml files. Let n1 be the number of kpoints in the first file. The first n1 kpoints in the second file have to be exactly the same as those in the first.
compareEV.py <vasprun1.xml> <vasprun2.xml>
Be warned that the output is extremely lazy.
plotBS.py
Plots the bandstructure from vasprun.xml files that used KPOINTS files created with appendKPaths.py along the paths defined in the json file.
If you split your vasp calculation along different segments you can plot them in one graph by giving the files in the order which they appear in the
graph as command line arguments.
plotBS.py <vasprun1.xml> <QPOINTS1.json> <vasprun2.xml> <QPOINTS2.json> ...
Metadata
Release files for ssptools 0.4.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 | |
|---|---|---|---|---|
| ssptools-0.4.1.tar.gz | 9.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ssptools-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.9 kB
Release files / ssptools-0.4.1.tar.gz
| Download URL | ssptools-0.4.1.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b41ce499d0db70dad174360382a1ebe6f9207dbf48b2ca4a6f1d29fcbe8cc6d
|
|
BLAKE2b-256 checksum How to use checksums |
b92d525a38c85f95125e5f167b9c0fda59265757ed5c1dfb38191baf91bf7afa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.4
|
Release files / ssptools-0.4.1-py3-none-any.whl
| Download URL | ssptools-0.4.1-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a4ebfa9da361f147e8d231711f664bf09414d35b8a7eeed306831687ad63487d
|
|
BLAKE2b-256 checksum How to use checksums |
af166901d8b7be878d240f695401dabf393dbfebad20ed2edb03a4ffb1cfa3b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.4
|
Security for ssptools 0.4.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.