Skip to main content

pyiron_lammps

Pipeline codecov Binder

The pyiron_lammps packages provides primarily two functions. A write_lammps_structure() function to write an ase.atoms.Atoms structure to an LAMMPS data file and a parse_lammps_output_files() function to parse the log.lammps, dump.out and dump.h5 files from the LAMMPS thermo and dump commands.

Installation

The pyiron_lammps package is distributed via both pypi:

pip install pyiron-lammps

and conda-forge:

conda install -c conda-forge pyiron_lammps

Write LAMMPS structure

The write_lammps_structure() function is designed to write an ase.atoms.Atoms structure to an LAMMPS data file:

from pyiron_lammps import write_lammps_structure

write_lammps_structure(
    structure,
    potential_elements,
    units="metal",
    file_name="lammps.data",
    working_directory=None,
)

The structure parameter refers to the ase.atoms.Atoms structure and the potential_elements refers to the list of elements implemented in the specific interatomic potential. For example the NiAlH_jea.eam.alloy potential implements the elements Ni, Al and H, so when writing a structure for a simulation with this potential the potential_elements=["Ni", "Al", "H"]. It is important to maintain the order of the elements as LAMMPS internally references the elements based on their index, starting from one. The units parameter refers to the LAMMPS internal units to convert the ase.atoms.Atoms object which is defined in Angstrom to the length scale of the LAMMPS simulation. Finally, file_name parameter and the current working directory working_directory parameter are designed to select the location where the LAMMPS structure should be written. With the default parameters the LAMMPS structure is written in the lammps.data file in the current directory.

Parse LAMMPS output

In addition to writing the LAMMPS input structure pyiron_lammps also provide the parse_lammps_output_files() function to parse the LAMMPS output files, namely the log.lammps, dump.out and dump.h5 files:

from pyiron_lammps import parse_lammps_output_files

parse_lammps_output_files(
    working_directory,
    structure,
    potential_elements,
    units="metal",
    dump_h5_file_name="dump.h5",
    dump_out_file_name="dump.out",
    log_lammps_file_name="log.lammps",
)

In analogy to the write_lammps_structure() function the working_directory parameter refers to the directory which contains the output files. The structure parameter reefers to the ase.atoms.Atoms object which should be used as template to parse the structure from the dump files. This structure is again required as LAMMPS internally references elements only by an index, so the template structure is required to map the elements from the interatomic potential back to the elements of the ase.atoms.Atoms object. In the same way the potential_elements refers to the list of elements implemented in the specific interatomic potential. The units parameter refers to the LAMMPS internal units to convert the ase.atoms.Atoms object which is defined in Angstrom to the length scale of the LAMMPS simulation. Finally, the parameters dump_h5_file_name, dump_out_file_name and log_lammps_file_name refer to the output file names.

For the dump.out file the following LAMMPS dump command should be added to the LAMMPS input file:

dump 1 all custom 100 dump.out id type xsu ysu zsu fx fy fz vx vy vz
dump_modify 1 sort id format line "%d %d %20.15g %20.15g %20.15g %20.15g %20.15g %20.15g %20.15g %20.15g %20.15g"

For the log.lammps file the following LAMMPS thermo command should be added to the LAMMPS input file:

thermo_style custom step temp pe etotal pxx pxy pxz pyy pyz pzz vol
thermo_modify format float %20.15g
thermo 100

Usage

Currently, the pyiron_lammps parser is primarily used in the pyiron_atomistics package and its successor the atomistics package to provide a simple LAMMPS parser. It only depends on ase, numpy, pandas and scipy and has an optional dependency on h5py to parse the LAMMPS h5md format.

Metadata

Release files for pyiron-lammps 0.5.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pyiron-lammps 0.5.4
File Size Uploaded
pyiron_lammps-0.5.4.tar.gz 29.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pyiron-lammps 0.5.4
File Interpreter ABI Platform
pyiron_lammps-0.5.4-py3-none-any.whl Python 3 none any Details

Total release size: 65.7 kB

Release files / pyiron_lammps-0.5.4.tar.gz

Download URL pyiron_lammps-0.5.4.tar.gz
Size 29.8 kB
Tags Source
SHA-256 checksum
How to use checksums
4c687fead1734eb6bca16278da2628bf8b626b320d9e1d61b1cd039afb86e9fd
BLAKE2b-256 checksum
How to use checksums
7456bc8fdc1a0dcba9f35259024081f792122468c65567ee95e7fd8cdcb8fd12
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 26, 2026.

Transparency log

Release files / pyiron_lammps-0.5.4-py3-none-any.whl

Download URL pyiron_lammps-0.5.4-py3-none-any.whl
Size 35.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0fced1fe3d7ad905bdd4907f70fa3f88f2c89c80de62d3587dd978a07af9e85b
BLAKE2b-256 checksum
How to use checksums
549b12b2e06bcff11d88f224d35c002805340cb712453decdfc8c81d08a96e9f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 26, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.5.4 This release

2 release files

0.5.3

2 release files

0.5.2

2 release files

0.5.1

2 release files

0.5.0

2 release files

0.4.10

2 release files

0.4.9

2 release files

0.4.8

2 release files

0.4.7

2 release files

0.4.6

2 release files

0.4.5

2 release files

0.4.4

2 release files

0.4.3

2 release files

0.4.2

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.2.14

2 release files

0.2.13

2 release files

0.2.11

2 release files

0.2.10

2 release files

0.2.9

2 release files

0.2.8

2 release files

0.2.7

2 release files

0.2.6

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page