Currently the process inside VaspInteractive is a Popen subprocess on the same OS. It is possible to separate VaspInteractive with the host system, consider the following situations:
Vasp subprocess is maintained inside a kubernetes pod / docker container, isolated from the current python process.
The vasp subprocess is running on a remote server via ssh
This can be beneficial if the optimizer is also computation demanding (e.g ML training) since VaspInteractive occupies 100% cpu time. instead of stdio, named file io should be used in this case
Currently the process inside VaspInteractive is a Popen subprocess on the same OS. It is possible to separate VaspInteractive with the host system, consider the following situations:
This can be beneficial if the optimizer is also computation demanding (e.g ML training) since VaspInteractive occupies 100% cpu time. instead of stdio, named file io should be used in this case