-
Notifications
You must be signed in to change notification settings - Fork 96
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
FEATURE: GW workflow with VASP #800
Comments
Hi @yanghan234 and @mkhorton. Thanks again for planning to contribute this feature. I don't think anyone else is working on it, so please go ahead and submit a PR when you are ready. It might be best to submit a WIP PR as soon as you're ready so any issues can be flagged earlier. |
Actually, Tathagata Biswas (@tatha0003) who is a now postdoc at UCLouvain in my group is working on BSE/GW workflows with ABINIT. In the past, he contributed with VASP workflows based on atomate (https://github.com/cmdlab/pyGWBSE https://www.nature.com/articles/s41524-023-00976-y). We should definitely coordinate our efforts. We also had already another workflow in the past: https://journals.aps.org/prb/abstract/10.1103/PhysRevB.96.155207 |
Hi Gian-Marco and Tathagata, currently I'm working on implementing a GW workflow with VASP (almost done). It sounds like we're in a great place if you're focusing on GW in abinit at the moment. Also, I'm totally open to teaming up on the VASP GW workflow if you're interested. Let me know what you think! |
Hi Han, It would be great to team up for the development of these workflows. |
Hi all,
After discussion with @mkhorton and @utf, we are planning to add a GW workflow based on VASP. Please let us know if you think this is a good thing to do.
Also, we want to ensure our efforts are in harmony with the broader development plans. So, please let us know if other contributors are already working on this, to avoid any potential overlap.
Thank you!
Han.
The text was updated successfully, but these errors were encountered: