Revision history [back]

Always use the idf file from EnergyPlusPreProcess-0 if you are using the raw idf, because otherwise your potential EnergyPlus measures won't have been taken into account.

Otherwise, you would be better off querying the SQL file generated during simulation if you know how to.

As far as reporting for 3 days, hourly, either you run an annual simulation at hourly timestep and then you'll parse out the results for these 3 days only, or you can make use of the Output:Variable Schedule Name: put a one for these three days, and zero for the rest.

You'll have to use an OpenStudio Measure for this since you can't access the schedule name attribute in the OS App. Here's a short example of how to manipulate outputVariable in the OpenStudio SDK.

outputVariable = OpenStudio::Model::OutputVariable.new(variable_name, model)
outputVariable.setReportingFrequency(reporting_frequency)
# Key is optional, you could create three different variables where the key is the specific zone you want
outputVariable.setKeyValue(key)
outputVariable.setSchedule(reporting_schedule)

Always use the idf file from EnergyPlusPreProcess-0 if you are using the raw idf, because otherwise your potential EnergyPlus measures won't have been taken into account.

Otherwise, you would be better off querying the SQL file generated during simulation if you know how to.

As far as reporting for 3 days, hourly, either you run an annual simulation at hourly timestep and then you'll parse out the results for these 3 days only, or you can make use of the Output:Variable Schedule Name: put a one for these three days, and zero for the rest.

You'll have to use an OpenStudio Measure for this since you can't access the schedule name attribute in the OS App. Here's a short example of how to manipulate outputVariable in the OpenStudio SDK.

outputVariable = OpenStudio::Model::OutputVariable.new(variable_name, model)
outputVariable.setReportingFrequency(reporting_frequency)
# Key is optional, you could create three different variables where the key is the specific zone you want
outputVariable.setKeyValue(key)
outputVariable.setSchedule(reporting_schedule)

Always use the idf file from EnergyPlusPreProcess-0 if you are using the raw idf, because otherwise your potential EnergyPlus measures won't have been taken into account.

Otherwise, you would be better off querying the SQL file generated during simulation if you know how to.

As far as reporting for 3 days, hourly, either you run an annual simulation at hourly timestep and then you'll parse out the results for these 3 days only, or you can make use of the Output:Variable Schedule Name: put a one for these three days, and zero for the rest.

You'll have to use an OpenStudio Measure for this since you can't access the schedule name attribute in the OS App. Here's a short example of how to manipulate outputVariable in the OpenStudio SDK.

outputVariable = OpenStudio::Model::OutputVariable.new(variable_name, model)
outputVariable.setReportingFrequency(reporting_frequency)
# Key is optional, you could create three different variables where the key is the specific zone you want
outputVariable.setKeyValue(key)
outputVariable.setSchedule(reporting_schedule)

BCL measure to set up output variables from a CSV file

I also uploaded to a BCL a measure to setup output variables from a csv file here.

Basically you can add multiple keys in the same cell separated by comma, you can specify an existing schedule in your model or type "reporting_schedule_3_days_per_month" and it will create a schedule that reports one tuesday, one saturday and one sunday per month (I find that useless to not overload the SQL file when I need a lot of variables at Detailed timestep).