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

Vasp_cmd of ibrun not handled properly #257

Open
jamesgil54 opened this issue May 26, 2023 · 0 comments
Open

Vasp_cmd of ibrun not handled properly #257

jamesgil54 opened this issue May 26, 2023 · 0 comments

Comments

@jamesgil54
Copy link

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

<Example code generating error>

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>
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

1 participant