search

Arthlol / bpswg

Automatically exported from code.google.com/p/bpswg
0 stars 0 forks source link

Separate ScenarioResult (as child class of Scenario), instead of overloading Scenario #60

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I think overloading the Scenario/Scenario Parameters to capture scenario 
results adds unnecessary complexity (and may cause confusion). I propose we 
capture scenario results in a ScenarioResult class (table), as child (children, 
as instances) of Scenario (similar to how the parameters are defined/captured 
in ScenarioParameter class). The added advantage is that we could customize 
that class with attributes that are specific to results (rather than trying to 
re-use parameter type of attributes in a contrived way).

Original issue reported on code.google.com by razvan.r...@wwhc.us on 23 Feb 2012 at 2:27

GoogleCodeExporter commented 9 years ago

Original comment by razvan.r...@wwhc.us on 23 Feb 2012 at 2:34

GoogleCodeExporter commented 9 years ago 
Consensus to maintain schema as-is. If this concern will re-surface once we 
have more simulation results data, a new Issue will be re-open at that time.

Original comment by razvan.r...@wwhc.us on 8 Mar 2012 at 4:47