SEAMM Thermal Conductivity Plug-in
A SEAMM plug-in for Thermal Conductivity
Free software: BSD-3-Clause
Documentation: https://molssi-seamm.github.io/thermal_conductivity_step/index.html
Code: https://github.com/molssi-seamm/thermal_conductivity_step
Features
Please edit this section!
Acknowledgements
This package was created with the molssi-seamm/cookiecutter-seamm-plugin tool, which is based on the excellent Cookiecutter.
Developed by the Molecular Sciences Software Institute (MolSSI), which receives funding from the National Science Foundation under award CHE-2136142.
History
- 2026.10.15 – Bugfix: crash with coarse sampling; unreliable fits
The Green–Kubo fit failed when the heat flux was sampled less often than every 0.4 ps. It no longer fails.
The Green–Kubo fit could accept a second exponential with a negative amplitude, or one too slow to level off within the data, and give a value far from the plateau of the integral. Such fits are now rejected in favour of a single exponential. The error of a two-exponential fit, which could be enormous when the two time constants were nearly equal, now accounts for their correlation.
The errors were from the fits to the curves averaged over the runs, which treat their strongly correlated points as independent: the Green-Kubo and Helfand-moment errors were far too small (e.g. +/- 0.0004 W/m/K where the runs differed by 0.03), and the Helfand-derivative errors too large. The error of each value is now the standard error of the values fitted to each run, and the 95% interval is twice that.
With a single run the Helfand-moment fits failed and printed 1.00; they now give the slope. With a single run there is no spread between runs to estimate errors from, so none are printed.
The slope of the Helfand moments (“Helfand Derivative”) was shifted by one sample, and its errors were in the wrong units. Both are corrected.
The analysis now uses the shared seamm_md_analysis library, also used by the Diffusivity step, instead of its own copy. The Helfand moments are computed much faster (by FFT): for a million samples, 0.4 s instead of about 2 minutes.
Thermal conductivities from the LAMMPS Heat Flux sub-step need lammps-step 2026.10.15 or later: earlier versions computed the heat flux wrongly.
The step no longer needs pandas or statsmodels, and its tests run with uv in CI using the package’s declared dependencies.
2026.3.1 – Internal: switching from deprecated library pkg_resources to importlib
- 2024.6.3 – Bugfix: handling of options for subflowchart
Fixed a bug where the options for the subflowchart were not being parsed correctly.
2024.3.22 – Updated for new scheme for running background tasks.
- 2024.1.5 – Bugfix: Thermal conductivity
If the Helfand moments fit in the thermal conductivity step failed it stopped the entire job. This is fixed, as well as some of the underlying causes for convergence issues.
2023.5.29 – Converged with general approach for trajectory analysis
- 2023.5.6 – Bugfix
Fixed an error handling Nan’s and Inf’s that caused a crash
Added the predictions from the derivatives of the Helfand moments to the output to give a better feel for the quality of the results.
- 2023.5.5 – Improved analysis
Considerable improvements to the analysis, results now seem solid
Fixed issues with fitting the linear portion of the Helfand moments
Added plot of the slope from the Helfand moments, which is similar to the Green-Kubo integral.
Cleaned up both the output and graphs.
- 2023.4.24 – Initial working version
Initial tests seem to work but needs more thorough testing.
Needs documentation!
- 2023.4.18 (2023-04-18)
Plug-in created using the SEAMM plug-in cookiecutter.
Metadata
Release files for thermal-conductivity-step 2026.10.15
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 |
|---|---|---|---|---|
| thermal_conductivity_step-2026.10.15.tar.gz | 313.5 kB | Without provenance | Details for thermal_conductivity_step-2026.10.15.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| thermal_conductivity_step-2026.10.15-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for thermal_conductivity_step-2026.10.15-py2.py3-none-any.whl |
Total release size: 336.9 kB
Release files / thermal_conductivity_step-2026.10.15.tar.gz
| Download URL | thermal_conductivity_step-2026.10.15.tar.gz |
|---|---|
| Size | 313.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b03e08f094ed6206b890b88fd1bc7ba09615f7c3033989a70f9b67a37eb6d65b
|
|
BLAKE2b-256 checksum How to use checksums |
34c1c7a29eee0254d6b28c6f1544fb6d787b148360a6ea91f67619d270247bdd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / thermal_conductivity_step-2026.10.15-py2.py3-none-any.whl
| Download URL | thermal_conductivity_step-2026.10.15-py2.py3-none-any.whl |
|---|---|
| Size | 23.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
38c673920c4c3ac252e99eb1c29118e153932a673842cadde34d82caa6cc4789
|
|
BLAKE2b-256 checksum How to use checksums |
a4cbdf9c1280ab1af1d02a1f9f52bcf2dd5231f7996d447b8ee93a4e92717f97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for thermal-conductivity-step 2026.10.15
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.