scikit-nano is a python toolkit for generating nanostructure data and nanostructure analysis.
Its primary utility is generating nanostructure data (i.e. atomic coordinates) for the following nanostructure materials:
Graphene:
Single layer graphene
Bi-layer graphene with layers rotated relative to each other by any angle and different layer stacking arrangements
\(N\)-layer graphene
Nanotubes:
Single-walled nanotubes (SWNTs)
SWNT bundles
Multi-walled nanotubes (MWNTs)
MWNT bundles
It currently supports saving structure data in the following formats:
xyz
LAMMPS data
Secondary to its structure generating functions are its structure analysis tools including:
defect/vacancy structure analysis
nearest-neighbor analysis
…
I welcome feedback and contributions to development!
For documentation, see: scikit-nano documentation
Metadata
Release files for scikit-nano 0.2.17
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 | |
|---|---|---|---|---|
| scikit-nano-0.2.17.tar.gz | 2.9 MB | Without provenance | Details |
Release files / scikit-nano-0.2.17.tar.gz
| Download URL | scikit-nano-0.2.17.tar.gz |
|---|---|
| Size | 2.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6cd764384495afef32074b61c52ccbcf43ce935dceebdf18e4e19ad225776766
|
|
BLAKE2b-256 checksum How to use checksums |
26c7ab8d5acebf0c82bb3475ea8c0930dbd230d32a637b9890113c8915e64da3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for scikit-nano 0.2.17
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.