-
Notifications
You must be signed in to change notification settings - Fork 72
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
DFT run complete in 0s #421
Comments
Thanks for reporting. Could you please post the input script? I will try to reproduce. |
I apologize if this is a stupid way to upload our scripts; GitHub appears not to support File 1:
|
Thank you for sending your files! GitHub makes it difficult to attach files, so I think copy/pasting is the only way to do it. I believe I've root caused the issue. The
But they're not actually get computed here, because I have a fix for this in #423. If the build passes, I will merge into master, and you should be good to go. |
OK, the fix is now merged into master. Can you please give it a try and let me know how it goes? |
Thank you for the quick fix! @mohan-s1 has tested that things are working great. We had a Slurm issue and the job got canceled after ~100 vasp + lmp runs. We'll confirm again if the job runs to completion. |
Completed successfully. Thanks again! |
Awesome, glad to hear it's working! Thanks for reporting the bug. |
A user is testing 1.4.2 (commit cb57c6b on Sep 30, 2024) using the same compilers, vasp, input files, and Slurm script as 1.3.3 (official release). The calculation runs fine in 1.3.3 but not for the newer version. Specifically, the first DFT call completes immediately without generating any output files:
which causes the subsequent command to fail:
Since we have not modified the VASP installation we don't think the DFT run failure is due to VASP. Do you know what could be causing this behavior (e.g. changes to the input file syntax)?
The text was updated successfully, but these errors were encountered: