You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When things calm down, it'd be good to investigate this.
Detailed Description
We get the same info in measure_attributes.json, results.json and data_point_out.json...
measure_attributes.json is flushed after each apply measure Step (ModelMeasures, EnergyPlusMeasures, ReportingMeasures), then at the end of ReportingMeasures it's done once again and results.json is spat out too
Do we really need the data_point_out.json in addition to this?
Seems like we could just run the output of results.json/data_point_out.json at the end of the workflow run instead
Possible Implementation
Standardize on a single file.
The text was updated successfully, but these errors were encountered:
Enhancement Request
Context: #5028 (review)
When things calm down, it'd be good to investigate this.
Detailed Description
measure_attributes.json
,results.json
anddata_point_out.json
...measure_attributes.json
is flushed after each apply measure Step (ModelMeasures
,EnergyPlusMeasures
,ReportingMeasures
), then at the end ofReportingMeasures
it's done once again andresults.json
is spat out toodata_point_out.json
in addition to this?results.json
/data_point_out.json
at the end of the workflow run insteadPossible Implementation
Standardize on a single file.
The text was updated successfully, but these errors were encountered: