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

Tracking provenance of Hubbard node #21

Closed
aim137 opened this issue Oct 9, 2021 · 2 comments
Closed

Tracking provenance of Hubbard node #21

aim137 opened this issue Oct 9, 2021 · 2 comments

Comments

@aim137
Copy link
Collaborator

aim137 commented Oct 9, 2021

I could not find a way to pass a hubbard node as input to SelfConsistentHubbardWorkChain in a way such that the provenance of those Hubbard parameters was tracked (as one would do with a structure node, for instance).

The use case I have in mind is running one SelfConsistentHubbardWorkChain with a given grid of q-points, and doing a final check with a finer q-grid (another instance of SelfConsistentHubbardWorkChain) to see whether the calculated value of U is well converged with respect to q-sampling. I used the following to pass the Hubbard parameters calculated by the first WC to the second one, however provenance wasn't tracked.

#node 9415 is the hubbard node, output of the first WC, as seen in `Verdi node show <WC_node>`:
Outputs      PK  Type
---------  ----  -------------
hubbard    9415  Dict
structure  9419  StructureData
 
#Loading the node and doing:
result_hubbard = load_node(9415)   
builder = SelfConsistentHubbardWorkChain.get_builder()
builder.structure = structure
builder.hubbard_u=Dict(dict={
  result_hubbard.get_dict()['sites'][0]['kind']:float(result_hubbard.get_dict()['sites'][0]['value']),
  result_hubbard.get_dict()['sites'][1]['kind']:float(result_hubbard.get_dict()['sites'][1]['value']),
  })

Feel free to close the issue if there is a way to do that and I just didn't find it.

@bastonero
Copy link
Collaborator

In the future version #32, which will use QuantumESPRESSO v7.1, this should be automatically addressed.

@bastonero
Copy link
Collaborator

Via introducing the HubbardStructureData, the link is automatically performed. Fixed in #32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants