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
Provide alternative results file output types (to the default .csv files) for the ERI workflow.
When using the current ERI workflow (driven by a command line ruby script), only .csv (results) file outputs are provided. This issue requests the output file options to be extended to mimic those available to users who use the "HPXMLtoOpenStudio" workflow.
Perhaps an additional command line argument could be added (similar to --debug, etc.) to allow the ERI workflow user to set the output file type. A single output file type should (as requested) be applied to all output files.
This feature aligns (2) significant HPXML based OS workflow output options with one another, making it easier for users who develop post processing methods/capabilities using non-csv file formats to apply these post processing methods to ERI based workflows.
The text was updated successfully, but these errors were encountered:
@chrisbalbach Thanks for the suggestion. In OS-HPXML, we have an --output-format TYPE commandline argument, where TYPE can be csv, json, msgpack, etc., which results in all output products (annual or timeseries) to be in that format. If we added the same capability to OS-ERI, would that suffice?
New Feature Request:
Provide alternative results file output types (to the default .csv files) for the ERI workflow.
When using the current ERI workflow (driven by a command line ruby script), only .csv (results) file outputs are provided. This issue requests the output file options to be extended to mimic those available to users who use the "HPXMLtoOpenStudio" workflow.
Perhaps an additional command line argument could be added (similar to --debug, etc.) to allow the ERI workflow user to set the output file type. A single output file type should (as requested) be applied to all output files.
This feature aligns (2) significant HPXML based OS workflow output options with one another, making it easier for users who develop post processing methods/capabilities using non-csv file formats to apply these post processing methods to ERI based workflows.
The text was updated successfully, but these errors were encountered: