Proc_params for communicating arbitrary object between process and process model#162
Proc_params for communicating arbitrary object between process and process model#162bamsumit merged 9 commits intolava-nc:mainfrom
Conversation
…dataloader. Signed-off-by: bamsumit <[email protected]>
Signed-off-by: bamsumit <[email protected]>
mathisrichter
left a comment
There was a problem hiding this comment.
Looks good overall! :)
Biggest concern: Should this PR be split in two to separate the addition of the proc_params and the addition of the dataloader? @mgkwill, what do you think?
Otherwise, I marked a bunch of minor things and suggested refactoring to reduce code duplication.
Signed-off-by: bamsumit <[email protected]>
Signed-off-by: bamsumit <[email protected]>
ashishrao7
left a comment
There was a problem hiding this comment.
I have not yet gone through the design decisions but I can confirm that with this PR one can communicate arbitrary objects between process and process model. I was successfully able to use this behavior in my setup
awintel
left a comment
There was a problem hiding this comment.
Looks good overall.
Suggest to clean up the signatures of init and do proper initialization in AbstractProcess and AbstractProcModel.
|
Don't forget to also close #164 when this gets pushed. |
…t's derivatives. Fixed all the broken code in the current repo because of it. Signed-off-by: bamsumit <[email protected]>
It's already linked to this PR. |
awintel
left a comment
There was a problem hiding this comment.
Looks good. But could you also update the AbstractProcess docstring (as requested by Ashish, so people know they can set proc_params in their init method?
Ideally this should also be documented in the ProcModel docstring but this one is currently outdated already.
Signed-off-by: bamsumit <[email protected]>
Implemented proc_params in process model constructor and used it for dataloader processes.
Signed-off-by: bamsumit [email protected]
Issue Number:
Objective of pull request:
Pull request checklist
Your PR fulfills the following requirements:
pyb) passes locallypyb -E unit) or (python -m unittest) passes locallyPull request type
Please check your PR type:
What is the current behavior?
What is the new behavior?
HostCPUto indicate the process model must run on Host CPU.Does this introduce a breaking change?
The execution may halt if you have overloaded the process model constructor without
proc_paramsargument. The intended way to overload isSupplemental information