Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Forcefield relaxmaker jobs fails due to BSONObj size exceeds 16MB for large structures #703

Closed
naik-aakash opened this issue Feb 6, 2024 · 4 comments

Comments

@naik-aakash
Copy link
Contributor

naik-aakash commented Feb 6, 2024

Describe the bug
Relax jobs using forcefields fails as the forcefield taskdoc stores all the ionic steps leading to cross the size limit

Steps to reproduce

1.Run relax jobs using mace forcefield with Fire optimizer for a cell containing more than 1000 atoms with a force requirement of 0.0001

Possible solution

  1. Modify the default interval arg of relax maker from 1 to 100 / larger number (this solution should potentially work as we tested using LBFGS optimizer of ase instead of default Fire optimzer, and same job then runs without any issue as LBFGS stores 100 steps at max)
  2. arg to allow users to skip storing ionic step data in taskdoc

Any thoughts on this or other ideas to tackle this issue are welcome.

@naik-aakash
Copy link
Contributor Author

Sorry found a way to set the number of steps we store.

@JaGeo
Copy link
Member

JaGeo commented Feb 6, 2024

Still, it might be worth solving this with a sensible default

@naik-aakash
Copy link
Contributor Author

Okay I reopen this issue then. 😅

@naik-aakash naik-aakash reopened this Feb 6, 2024
@naik-aakash naik-aakash changed the title BUG: Forcefield relaxmaker jobs fails due to BJSON size exceeds 16MB for large structures BUG: Forcefield relaxmaker jobs fails due to BSONObj size exceeds 16MB for large structures Feb 6, 2024
@utf
Copy link
Member

utf commented Feb 15, 2024

Thanks for raising this. I think this is a duplicate of #515, so I will close this issue and move the comments across.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants