-
Notifications
You must be signed in to change notification settings - Fork 189
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/suggestions on documentation page about workflows #1927
Comments
sphuber
added
type/task
good first issue
Issues that should be relatively easy to fix also for beginning contributors
topic/workflows
topic/code-structure
priority/nice-to-have
labels
Dec 3, 2018
3 tasks
unkcpz
removed
the
good first issue
Issues that should be relatively easy to fix also for beginning contributors
label
Nov 11, 2021
Thanks Jason. I don't use AiiDA any more now, so I'm not sure that my input would be valuable. But I do appreciate your following up. EDIT: Also the link above does not work any more... |
Thanks Marco! To me, the problem you mentioned is now nicely documented thanks to their efforts on documentation ;-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a few questions / suggestions about this page of the documentation that discusses workflows.
Can the
ctx
member of a WorkChain be equivalently accessed as a dictionary (self.ctx['key']
) and with the dot notation (self.ctx.key
)? This seems implied but is not made explicit.The use of the
agglomerate
argument is not super clear to me, especially in the case ofexposed_outputs()
. They name of the argument itself also doesn't seem very intuitive. Maybe I just need to make use of the feature in order to understand its necessity.To better understand the last complex example, I took the liberty of making a graph: feel free to use it (or not). Note however that, in order to make the graph clearer, I had to slightly change the
ChildWorkChain
so that it creates new outputs, rather than simply passing the inputs along:57665.pdf
The text was updated successfully, but these errors were encountered: