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

Implement geomeTRIC option --converge maxiter #311

Open
amcisaac opened this issue Jan 7, 2025 · 3 comments
Open

Implement geomeTRIC option --converge maxiter #311

amcisaac opened this issue Jan 7, 2025 · 3 comments
Assignees

Comments

@amcisaac
Copy link

amcisaac commented Jan 7, 2025

We'd like to use the GeomeTRIC option --converge maxiter (as documented here), which allows the program to exit gracefully after hitting the maximum number of iterations, but it's not currently supported in QCSubmit. We will open a PR to implement it as one of the options for convergence_set in GeometricProcedure.

@amcisaac amcisaac self-assigned this Jan 7, 2025
@amcisaac
Copy link
Author

amcisaac commented Jan 7, 2025

This is currently blocked by the fact that --converge maxiter is (as far as I can tell) not implemented in a release version of GeomeTRIC, documented in this issue

@j-wags
Copy link
Member

j-wags commented Jan 7, 2025

Copying an email I sent earlier to complete the records here:

We'd be happy to have a PR for this and run it on our stack/compute, but I wonder if we can avoid basically testing in prod when we submit to QCArchive (this has led to problems in the past... like I wouldn't put it past QCF to silently fail to pass the keyword to geometric or something weird like that). So could you

  1. add a test to the PR with a super short opt of a tiny mol, or that exports the task to the MolSSI QC ecosystem and ensures that the correct keyword is set in the real dataset
  2. Manually run 5 or 10 of these step-limited opts on a QCFractal server locally to ensure that they have the desired behavior

I just checked and @amcisaac's still in the developers group on GitHub, so feel free to work directly in a branch of QCSubmit and use the PR to run CI. Once this is merged we can make a stable release for the provenance and any qca-dataset-submission stuff that needs the new version.

@amcisaac
Copy link
Author

amcisaac commented Jan 7, 2025

Thanks for copying that, I should have included it! We will absolutely include tests both locally and in the CI.

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