Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Writing the year information in the output energyplus .csv file

asked 2020-01-02 09:47:45 -0500

looooic's avatar

updated 2020-01-03 09:08:58 -0500

Is it possible to write the year of the simulation in the output .csv energyplus file ? In my case, in the .csv output file, i only have the month/day and the hour. I would like to know if we can also write the year ? The year is indicated in the .epw file. Thanks,

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2020-01-02 11:27:11 -0500

updated 2020-01-02 11:29:57 -0500

Assuming that you're using the ReadVarsESO postprocessing program to write out the CSV file, I don't think so. At present the best way to access the year of the simulation is through the use of the SQLite output, which does include the year.

Also, just a minor correction: the year in the EPW is not the year of the simulation. The year of simulation is determined from what's in your RunPeriod object. TMY EPW files have non-consecutive years in them because of how those are made, so that's not used to determine the year that E+ simulates.

edit flag offensive delete link more


Thanks for your answer, actually we are running eplus on server every 4 hours by updating weather forecast file from a database that we convert in epw automatically. As well, we modify the idf automatically to to update the date of the simulation. After we want to update a database with the simulated values to plot it in a dynamic dashboard. With the new year I just realize the importance of the year in the results. ReadVarsEso, sounds to work only with windows is it ? Working with the .csv file, sounds that the simple way is to add the year in post-processing is it ?


looooic's avatar looooic  ( 2020-01-03 04:59:25 -0500 )edit

No, ReadVarsESO works on all the supported platforms and is the way that EnergyPlus converts ESO data into CSV. The ESO timestamp for most time series will not include the year, which is the limiting factor. If you are using OpenStudio (just as an example), CSV outputs can be generated from the SQL, which has the year available. Adding the year after the fact is certainly possible, but if the year is important I'd advise making sure that the simulation year is what you think it is.The easiest way to do that is directly set it in your RunPeriod (and leave the start day of the week blank).

Jason DeGraw's avatar Jason DeGraw  ( 2020-01-03 10:53:34 -0500 )edit

Thank you for your reply. Sure we modify the Run period when we modify the ".idf". Thank you for the tips to let the start day week blank.

looooic's avatar looooic  ( 2020-01-06 04:56:27 -0500 )edit

answered 2023-08-02 09:53:00 -0500

Degux's avatar

What if I let EnergyPlus create the csv file directly via "OutputControl:Files"? EnergyPlus doesn't use ReadVarsESO in this case - but then the resulting csv file is limited to one year and it's not instantly clear wheter it's the first simulation year or the last.

This seems like a very unnecessary limitation. Is there a workaround?

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Training Workshops


Question Tools


Asked: 2020-01-02 09:47:45 -0500

Seen: 257 times

Last updated: Jan 02 '20