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

Questions about future plans #171

Open
Leo3701 opened this issue Nov 10, 2024 · 2 comments
Open

Questions about future plans #171

Leo3701 opened this issue Nov 10, 2024 · 2 comments

Comments

@Leo3701
Copy link

Leo3701 commented Nov 10, 2024

Hi everyone.
In the long term plans for py4vasp, it is possible to add functionality to help generate input files such as INCAR, KPOINTS...
It would be great to use only the python interface for pre- and post-processing of vasp calculations!

@martin-schlipf
Copy link
Collaborator

martin-schlipf commented Nov 10, 2024

Good that you bring it up. We are in discussions how to implement such a feature, perhaps you can add your perspective. There are two possible use cases for accessing input files. One is to set the input before a calculation is started, the other is inspecting the setup of a completed calculation. What kind of interface would you like for these two use cases? We considered

calculation.INCAR
calculation.input.INCAR
calculation.setup.INCAR

Would you prefer to have both use cases under the same interface or would you prefer two different ones?

@Leo3701
Copy link
Author

Leo3701 commented Nov 11, 2024

I think it's better to separate it so that one function can be used to control parameters such as INCAR, KPOINTS, etc., and for checking after the calculation is done another different function can be used.
I'm looking forward to being able to do my VASP calculations using only the python interface, and I think this will be especially helpful to many vasp users, both beginners and skilled ones!

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

2 participants