Until now, things have been designed for PET, whose features don't have a predefined rotational behavior. However, equivariant models are being added into metatrain (MACE and PhACE), whose features have a well defined rotational behavior.
When running an AtomisticModel with the consistency check turned on, the equivariant features cause an error because this possibility is not yet contemplated.
We should somehow make AtomisticModel aware that features can be equivariant. The difficulty in doing this (as I understand) is what to do with interfaces to other codes that for now also don't support these equivariant features.