Skip to content
Draft
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions src/pylammpsmpi/wrapper/concurrent.py
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,7 @@ def start(self, argument_lst):

def shutdown(self):
if self._job is not None:
self._job.finalize()
self._job.close()
Comment on lines +41 to 42
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should not the order be the other way around? First calling close() and then finalize(), at least this is how it is done in the LAMMPS examples: https://github.com/lammps/lammps/blob/develop/examples/mliap/mliap_pytorch_ACE.py

Copy link
Member

@jan-janssen jan-janssen Jan 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still even after this change the tests do not pass #412 . It seems to me that this option is only required for specific LAMMPS models, primarily the https://docs.lammps.org/pair_mliap.html models, still I do not find any explanation in the documentation, rather the finalize() call seems to be only used in examples which use mliap models.

self._job = None

Expand Down
Loading