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

Add pseudopotentials for the common workflows #186

Open
giovannipizzi opened this issue Apr 29, 2021 · 3 comments
Open

Add pseudopotentials for the common workflows #186

giovannipizzi opened this issue Apr 29, 2021 · 3 comments
Assignees

Comments

@giovannipizzi
Copy link
Contributor

At least for siesta, abinit, and Quantum ESPRESSO. Check this comment and the other messages in the same thread, as well as the supplementary of the paper.

@ltalirz
Copy link
Member

ltalirz commented Aug 2, 2021

I think the pseudopotentials should be added in the relevant roles (and some roles already do this, e.g. siesta and QE).
Maybe add a checklist here of which ones are still missing?

@giovannipizzi
Copy link
Contributor Author

Yes. I think the 'best' pseudos from the common-workflow protocols should be pre-installed.
@bosonie could you please prepare a simple bullet-point list of pseudos to install (and with which command) so @chrisjsewell can setup the various roles? I guess it's just a matter of summarising the SI of the paper here as bullet points (the info is probably also in the other issue linked above, but it has become very long so it's hard to find this information).

@bosonie
Copy link

bosonie commented Aug 12, 2021

Sorry for the late replay. The commands to run are:

  • aiida-pseudo install pseudo-dojo -v 1.0 -f jthxml
  • aiida-pseudo install sssp -p efficiency
  • aiida-pseudo install sssp -p precision
  • verdi data psml uploadfamily /usr/local/share/siesta/psml-files-qm/nc-sr-04_pbe_standard/ nc-sr-04_pbe_standard_psml "pseudos from PseudoDojo"

However this is for version 0.1.0 of aiida-common-workflows. The required pseudos (and the associated command) will surely change in the next release, therefore I would wait a bit before implementing this.

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

4 participants