CSV export from OpenStudio

[macumber]

We have had several requests for timeseries CSV output from OpenStudio similar to ReadVarsESO. However, I am unsure about the best implementation.

We could do this with a reporting measure with a boolean checkbox to report each variable or meter, would that be acceptable? Should we separate output into multiple CSV files, one for each reporting frequency?

Another option is to add CSV output from ResultsViewer. This could allow more control of outputs but is less automated.

[macumber]

We will likely not add this feature to ResultsViewer which leaves a measure implementation. I would think that the scope of reporting a variable for all keys is appropriate. If we need a second measure to report a variable for particular keys we can do that as well. We should implement this as an html measure which shows the data in tabular form with a link to download the raw CSV. We do not need to use ReadVarsESO directly.

[MatthewSteen]

+1

[jmarrec]

+1

[shorowit]

If/when OpenStudio switches from ResultsViewer to DView, this can be closed as DView has a right-click menu option to 'Save data to CSV'.

[jmarrec]

Switch to DView is live. This can be closed

[macumber]

@MatthewSteen do you agree with closing this now that DView is included?

[MatthewSteen]

Yes, sounds good.

[aaron-boranian]

Migrated from UserVoice

[Maharshi-Pathak]

how can I run the readvarESO or equivalent to convert this .eso file to csv if I am running the command line interface on linux based systems? Is it already possible in the OSW?

[jmarrec]

@Maharshi-Pathak Use the OutputControlFiles object

m = Model.new
o = m.getOutputControlFiles()
o.setOutputCSV(true)

E+ doc: https://bigladdersoftware.com/epx/docs/22-2/input-output-reference/input-for-output.html#outputcontrolfiles

[Maharshi-Pathak]

Amazing. Thanks @jmarrec

[govertsenk]

I turned @Maharshi-Pathak's question and @jmarrec's answer into a measure for others to use. Posted on my GitHub here.