This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| technical:recipes:vasp-6-darwin [2021-02-16 09:53] – [Versions] anita | technical:recipes:vasp-6-darwin [2021-02-16 10:00] (current) – [Runtime environment] anita |
|---|
| ==== Checking the definition file ==== | ==== Checking the definition file ==== |
| |
| The package definition file can be syntax-checked: | The package definition file can be checked for proper syntax using the VALET command ''vpkg_check'': |
| <code bash> | <code bash> |
| [user@login00.darwin ~]$ vpkg_check "$VALET_PKG_DIR/vasp.vpkg_yaml" | [user@login00.darwin ~]$ vpkg_check "$VALET_PKG_DIR/vasp.vpkg_yaml" |
| ~/sw/vasp/6.1.0/bin/vasp_std | ~/sw/vasp/6.1.0/bin/vasp_std |
| </code> | </code> |
| The ''vasp_std'' command is used //without a leading path// which implies that the shell with check directories in the ''$PATH'' environment variable for an executable with that name. If a different version/variant of **vasp** is chosen, the command would still be ''vasp_std'' but the shell would find it at a different location. This abstraction (no full paths to executables) makes it easier to alter complex job scripts by simply changing which variant is added using ''vpkg_require''. | The ''vasp_std'' command is used //without a leading path// which implies that the shell will check directories in the ''$PATH'' environment variable for an executable with that name. If a different version/variant of **vasp** is chosen, the command would still be ''vasp_std'' but the shell would find it at a different location. This abstraction (no full paths to executables) makes it easier to alter complex job scripts by simply changing the variant of **vasp** added using ''vpkg_require''. |
| |
| |