Skip to content
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

Add addition output files types to workflow beyond .csv #679

Closed
chrisbalbach opened this issue Jul 13, 2023 · 2 comments · Fixed by #681
Closed

Add addition output files types to workflow beyond .csv #679

chrisbalbach opened this issue Jul 13, 2023 · 2 comments · Fixed by #681

Comments

@chrisbalbach
Copy link

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.

@shorowit
Copy link
Collaborator

@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?

@chrisbalbach
Copy link
Author

Yes - @shorowit - that is exactly what is desired.

@shorowit shorowit mentioned this issue Jul 19, 2023
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants