Starting VASP 6.4.1 there are huge changes to the `INPOS` subroutine which basically breaks the current vasp-interactive workflow. #47 There are quite a few TODOs though - [ ] Detect whether `POSITIONS AND LATTICE: read from stdin` are got from raw out (--> 6.4.1+) or `POSITIONS: read from stdin` - [ ] Modify method to send POSCAR format to stdin - [ ] What about extra lines from VASP output? - [ ] Use more flexible isif=2 or isif=3 switch (i.e. let VaspInteractive calculator deside if lattice change is acceptable)
Starting VASP 6.4.1 there are huge changes to the
INPOSsubroutine which basically breaks the current vasp-interactive workflow. #47There are quite a few TODOs though
POSITIONS AND LATTICE: read from stdinare got from raw out (--> 6.4.1+) orPOSITIONS: read from stdin