CrysPy is a crystallographic python library for polarized neutron diffraction data analysis. The package allows the data treatment both for powders and single-crystal samples. Nuclear and (commensurate) magnetic structures refinement can be also perfomed based on the unpolarized neutron diffraction and X-ray diffraction data.
Features
CrysPy allows one to analyse the local magnetic anisotropy by the susceptibility approach and the spin/magnetization densities reconstruction by maximume entropy procedure based on polarized neutron diffraction experiments;
Core CIF dictionary of the IUCr is used to cover the requirements of archiving and exchanging the data and derived magnetic and structural results;
The library is written in Python. It can be used in Jupyter notebooks under the main platforms Windows, MacOSX and Linux or as a standalone application with a simple graphical user interface “CrysPy Editor”.
For more information please visit the site cryspy.fr.
Try CrysPy in a Web Browser before installing it on your PC.
Copyright and License
MIT License
Copyright (c) 2018-2026 Iurii Kibalin https://github.com/ikibalin/cryspy
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
1 maintainer
Metadata
1 maintainer
Release files for cryspy 0.14.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 | |
|---|---|---|---|---|
| cryspy-0.14.1.tar.gz | 1.4 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cryspy-0.14.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.1 MB
Release files / cryspy-0.14.1.tar.gz
| Download URL | cryspy-0.14.1.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4bf72f688cfd8fa16454abfceb7cc3ddb259fa34b29c03cebb8844e74281f2cf
|
|
BLAKE2b-256 checksum How to use checksums |
5b790b5d1006fb780101b69b1e675b81b873c92bbc03ab5529672a5b1018c5af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / cryspy-0.14.1-py3-none-any.whl
| Download URL | cryspy-0.14.1-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1981d4609f7eb1fcc4fe934a3d532d8c0f2b2ec8102b09a256cade745e3d05ce
|
|
BLAKE2b-256 checksum How to use checksums |
c65789df07f4a9a8a3fda7117928c5e28bb19e051208dc3ff301027f154b2ea4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for cryspy 0.14.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.
