Config trainer is overwritten to "forces" or "energy"

[hannahlawrence]

I wrote a custom trainer (modifying the forces_trainer.py file) and registered it under a new name, then passed it in to my config. However, this processing line overwrites whatever the true trainer name was in the config to "forces" or "energy", based on the task. The code still uses the correct trainer, but this is slightly confusing behavior from a logging perspective, such looking at wandb logs to verify which trainer was actually used in a given run. Thanks!

[mshuaibii]

Thanks for flagging! I'll make sure to address these changes in the new OCP trainer #520.

[github-actions]

This issue has been marked as stale because it has been open for 30 days with no activity.

[mshuaibii]

We've now removed all "forces/energy" trainer definition. Everything is now ocp and supportive of any arbitrary property defined.