Missing Variables in CSV Output Despite Being Present in ESO File

asked 2024-07-29 05:16:28 -0500

902 ●7 ●8

updated 2024-07-29 05:36:31 -0500

Hello everyone,

I am encountering an issue with the output variables in EnergyPlus. Specifically, when I export the data to a CSV file for plotting, I notice that some of the 48 variables I requested are missing from the CSV. However, upon checking the ESO file, I see that all the requested variables are generated.

Has anyone else experienced this problem, and if so, what solutions or workarounds have you found?

Any help would be greatly appreciated!

edit retag flag offensive close merge delete

Comments

Do you have more than 255 of them?

Julien Marrec ( 2024-07-29 05:32:53 -0500 )edit

Only 48 output variables.

Zakaria ( 2024-07-29 05:35:31 -0500 )edit

could you share your IDF (or a reduced version) that exhibits the issue?

Julien Marrec ( 2024-07-30 05:50:20 -0500 )edit

1

Is this the result of using ReadVarsESO (typically when using EP-Launch or with command line --readvars option)? Or did you use the OutputControl:Files option of YES for CSV files?

JasonGlazer ( 2024-08-01 12:35:43 -0500 )edit

Hi @Julien Marrec,

I've defined 48 output variables in EnergyPlus, including Node Temperature and Heat Flux. As a result, the number of output variables generated in the CSV file exceeds 255.

Is there a way to manage or address this issue?

Thanks

Zakaria ( 2024-08-08 05:03:31 -0500 )edit

add a comment

3

answered 2024-08-08 05:56:20 -0500

JasonGlazer

6815 ●25 ●12 http://www.gard.com/

Check your .err file

Jim Dirkes' advice to check your .err file to make sure you spelled all the output variables correctly is probably the best first step. If you have already done that, it may be a setting in the software that processes the ESO file into the CSV file that is used by EP-Launch or with the EnergyPlus command line. The software that converts the ESO to CSV is called ReadVarsESO. Read below for options depending on what you do.

EP-Launch

If you are using EP-Launch to simulate the file you can enable more than 255 columns by doing the following. First, select the Options menu item under the View Menu.

image description

Then under "Miscellaneous" select "Allow More Than 250 Columns"

image description

The next time you run the simulation you should have as many columns as you want.

Batch File

If you are using the RunEPlus.bat file the %maxcol% parameter needs to be set to "nolimit"

EnergyPlus Command Line

If you are running EnergyPlus using the command line, using the "-r" or "--readvars" option, it should already be producing more than 255 columns.

OutputControl:Files

If you are using in your IDF file, the OutputControl:Files option with the first field for CSV as yes, then it should already be producing more than 255 columns (remember don't use the "-r" or "--readvars" command line option if you do this). Unless you are also showing yes in the third field that controls creating the ESO file, you are probably not using OutputControl:Files.

edit flag offensive delete link

Comments

@JasonGlazer, I reviewed the .err file and confirmed that the output variables are spelled correctly. If there had been a misspelling, they wouldn’t have been generated in the .eso file.

I also followed your advice and increased the column limit to more than 250, which resolved the issue.

Thank you all for your assistance.

Zakaria ( 2024-08-08 07:32:45 -0500 )edit

add a comment

1

answered 2024-07-30 05:12:06 -0500

Jim Dirkes
3494 ●27 ●16

When some, but not all, variables show up in the .csv file, it's normally a spelling or syntax error. The .err file will normally indicate (as a warning) which variables cannot be found / produced.