Support lmp.in alongside control.inp in LAMMPS run scripts#75
Merged
Conversation
Copilot
AI
changed the title
Support both lmp.in and control.inp in LAMMPS scripts
Support lmp.in alongside control.inp in LAMMPS run scripts
Jun 12, 2026
Copilot created this pull request from a session on behalf of
jan-janssen
June 12, 2026 09:35
View session
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
LAMMPS run scripts were hardcoded to
control.inp. Scripts now detect which input file (lmp.inorcontrol.inp) is present in the working directory and invoke LAMMPS accordingly.Changes
lammps/bin/run_lammps_2024.02.07.sh/_mpi.sh— shell conditional selectslmp.inif present, else falls back tocontrol.inplammps/bin/run_lammps_2018.03.16.bat— Windowsif existequivalent logicmlip/bin/run_lammpsmlip_2020.12.24.sh/_mpi.sh— same shell conditionalBash pattern applied:
Batch pattern applied: