-
Notifications
You must be signed in to change notification settings - Fork 7
Simpler Workflow instantiation #158
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #158 +/- ##
==========================================
- Coverage 77.43% 77.39% -0.05%
==========================================
Files 62 62
Lines 5062 5110 +48
==========================================
+ Hits 3920 3955 +35
- Misses 1142 1155 +13
Continue to review full report at Codecov.
|
Hello @elinscott! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2022-07-14 08:24:15 UTC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not fully understand this story of fromparent
, but as usual I guess it will become more clear next time that I will have to implement something. Thanks Edward!
This closed #90 (but that issue was not tagged at the time) |
Workflow instantiation
Makes the creation of
Workflow
objects more flexible by acceptingkwargs
that can be workflow/calculator/plotting parameters e.g.whereas previously this would have to be
Closes #145
Changes to running subworkflows
This PR also introduces the
@classmethod
fromparent
to theWorkflow
class and deprecatedWorkflow.wf_kwargs
andWorkflow.run_subworkflow()
. Previously to create and run a subworkflow one had to do something likebut instead now we do
which is cleaner and more pythonic
Documentation
Added the docstrings of the
Workflow
class to the docs module usingautodoc
andnumpydoc
. This starts to address (but does not fully resolve) #147