-
Notifications
You must be signed in to change notification settings - Fork 0
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
Parameter definition #14
Comments
Depends on #16 |
So far we've used parameters par=True/False and queue=[] Requirements for entities. In brackets is how I have been doing this so far.
Is the current way good enough? |
Thing to consider is how to define and determine the order in which the values are put to queue. This could be done for example by defining that
(key,value)=get(queue)
|
I made it now so that the instances return their IOS (can be disabled with a flag because at least my testbench doesn't have IOs). Other data (e.g. calculated gain) is returned as a dictionary. run_parallel() saves this dictionary's value key pairs as parameters for each instance So, the code needed in the instances is
|
Hmm. self.IO.Members is a dict already, but ok So the assumption is that what is returned is a dictionary? OK What is important is then what expected to happen in parent. I propose the following The parent loops through the returned dictioany as (again peseudocode)
|
Let's leave this open. First step would be to convert these to properties at thsdk, so they do not need to be repeated in every entity. |
Define the parameters that must be defined within an entity in order to enable parallel runs from the parent.
The text was updated successfully, but these errors were encountered: