Closed adowling2 closed 6 days ago
Please assign this issue to @jialuw96 and @hglynch
Pyomo.DoE Version 2 (Some other problems for discussion and enhancements, each one should be a small PR):
eval
;getattr
(Need string name)ComponentUID
as in https://github.com/IDAES/idaes-pse/blob/274e58bef55f2f969f0df97cbb1fb7d99342388e/idaes/apps/uncertainty_propagation/sens.py#L296 (Need string name)find_component
(Need handle to Var
)UnindexedComponent_Set
and add_component
. Is this a good way? Note with @blnicho from IDAES meeting
Update documentation:
@blnicho @jsiirola Is Monday, Feb. 6 a reasonable cut-off date for minor PRs, e.g., updates to Pyomo.DoE documentation, before the next Pyomo release?
My thought is this gives the dev call on Feb. 7 to wrangle outstanding reviews and merge.
@adowling2 yes Feb. 6 is fine for a cut-off date.
@blnicho @jsiirola FYI, @jialuw96 and I are working on using blocks in Pyomo.DoE in https://github.com/jialuw96/pyomo/pull/15 which is a PR from one branch in @jialuw96's fork into a second branch on her fork. Once this is ready for review from the Pyomo team, we'll open PR into pyomo/main.
Pyomo.DoE version 3+:
calculate_FIM
, which I temporarily name as result_analysis
nowfigure_drawing
is not intuitive. https://github.com/Pyomo/pyomo/pull/2794#discussion_r1197140478Pyomo.DoE version 3+:
scenario.py
https://github.com/Pyomo/pyomo/pull/2794#discussion_r1200780723compare
and compute
https://github.com/Pyomo/pyomo/pull/2794#discussion_r1196803473@adowling2 @blnicho Any objections to closing this in favor of the new issue I made today (#3345)?
The purpose of this meta issue is to track our development plans for Pyomo.DoE.
Immediate (November/December 2022):
Pyomo.DoE Version 2 (start review in March 2023):
Enum
, see https://github.com/Pyomo/pyomo/pull/2294#discussion_r1024665131t
, see https://github.com/Pyomo/pyomo/pull/2294#discussion_r1025732006, https://github.com/Pyomo/pyomo/pull/2294#discussion_r1025464771)Pyomo.DoE Version 3+: