Skip to content

Record ghostly options on modified molecules and refuse to modify twice unless forced - #20

Merged
lohedges merged 2 commits into
develfrom
feature_modified_flag
Oct 26, 2026
Merged

lohedges merged 2 commits into
develfrom
feature_modified_flag

Conversation

@lohedges

Copy link
Copy Markdown
Contributor

Ghostly doesn't record that a system has been modified, so running it twice, e.g. by passing ghostly output to SOMD2 with ghost modifications enabled, silently applies the modifications again.

  • Each modified perturbable molecule now has a ghostly_options property holding a JSON list of the options used for each modification, in the order applied.
  • modify raises an error for a system that has already been modified, unless force=True (--force on the command line) is passed. Forced modifications are applied on top of the existing ones and appended to the options history.

@lohedges lohedges added the enhancement New feature or request label Oct 26, 2026
@lohedges
lohedges deployed to ghostly-build October 26, 2026 14:42 — with GitHub Actions Active
@lohedges
lohedges deployed to ghostly-build October 26, 2026 14:42 — with GitHub Actions Active
@lohedges
lohedges deployed to ghostly-build October 26, 2026 14:42 — with GitHub Actions Active
@lohedges
lohedges deployed to ghostly-build October 26, 2026 14:42 — with GitHub Actions Active
@lohedges
lohedges merged commit 9ab7e85 into devel Oct 26, 2026
4 checks passed
@lohedges
lohedges deleted the feature_modified_flag branch October 26, 2026 14:46

This branch was successfully deployed

1 active deployment
ghostly-build — 85f844d3 Deployed Oct 26, 2026 by lohedges via build (3.12, linux) #87
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant