You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reporting bugs/issues, please supply the following information. If this
is a feature request, please simply state the requested feature.
System: TACC Stampede2 HPC (SLURM)
Custodian version: 2023.3.10
Python version: 3.9.16
OS version: 7 (Core)
Summary
the vasp_cmd parameter for VASP atomate workflows in SLURM systems cannot properly handle the output syntax, vasp_std > my_vasp.out, which is frequently used to run vasp manually (ie without atomate) on SLURM systems. The command "ibrun vasp_std>my_vasp.out is translated to:
“vasp_cmd”: [
“ibrun”,
“vasp_std>my_vasp.out”
],## Example code
This prevents vasp from running. I report this issue also at the Materials Science Community Discourse here
<Examplecodegeneratingerror>
See MP community discourse post linked above!
<Error message>
Suggested solution (if known)
<If you have a suggestion on how to solve the issue, you may write it here.>
Files
<If input files are needed for the error, please copy and paste them here.>
<contents of file 1>
The text was updated successfully, but these errors were encountered:
When reporting bugs/issues, please supply the following information. If this
is a feature request, please simply state the requested feature.
System: TACC Stampede2 HPC (SLURM)
Summary
the vasp_cmd parameter for VASP atomate workflows in SLURM systems cannot properly handle the output syntax, vasp_std > my_vasp.out, which is frequently used to run vasp manually (ie without atomate) on SLURM systems. The command "ibrun vasp_std>my_vasp.out is translated to:
This prevents vasp from running. I report this issue also at the Materials Science Community Discourse here
See MP community discourse post linked above!
Suggested solution (if known)
Files
<If input files are needed for the error, please copy and paste them here.>
The text was updated successfully, but these errors were encountered: