Skip to content

AmberParams warning #102

@lohedges

Description

@lohedges

When loading a somd1 system via a perturbation file, the end states need to be extracted and re-merged in order to apply ghostly modifications. This process can trigger an annoying Sire warning due to an incompatibility in the AmberParams layout:

────────────────────────────────────────────────────────────────── WARNING ──────────────────────────────────────────────────────────────────
Could not convert the old property at key parameters with type SireMM::AmberParams to match the new, edited molecule. This property has been
deleted.
Error was SireError::incomplete_code: Cannot make compatible if atom order has changed!

Since this property isn't needed for somd2, it can safely be deleted prior to extracting the end states.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcressetRelated to work with Cresset

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions