-
Notifications
You must be signed in to change notification settings - Fork 878
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
VASP Input Sets: Investigate LMAXTAU #2325
Comments
Notifying @rkingsbury too as likely relevant for SCAN input sets. |
Just to clarify for my own notes too: This is really only relevant if |
Thanks @mkhorton ; if you change the SCAN sets just please make sure to check if any validation rules in the validation builder need to change (I don't think they do). |
The fix for this can ultimately be adapted from the relevant part in the Atomate2 PR: materialsproject/atomate2#362 |
Apparently there is plenty of ambiguity about this... https://www.vasp.at/forum/viewtopic.php?p=23038. I would lean towards closing this issue as a result. If Kresse says it's fine, then I'm inclined to believe him. |
We removed the the -----------------------------------------------------------------------------
| _ ____ _ _ _____ _ |
| | | | _ \ | | | | / ____| | | |
| | | | |_) | | | | | | | __ | | |
| |_| | _ < | | | | | | |_ | |_| |
| _ | |_) | | |__| | | |__| | _ |
| (_) |____/ \____/ \_____| (_) |
| |
| internal error in: asa.F at line: 479 |
| |
| internal error in YLM3LOOKUP: L or LP > LMAXCG |
| L, LP, LMAXCG 7 1 6 |
| |
| If you are not a developer, you should not encounter this problem. |
| Please submit a bug report. |
| |
----------------------------------------------------------------------------- |
@janosh: Let's close this as being not needed. |
Thanks @arosen93:
via https://www.vasp.at/wiki/index.php/LMAXTAU
Will likely add appropriate logic to appropriate VASP input sets.
The text was updated successfully, but these errors were encountered: