bonnema's profile - activity

Have you looked at the .edd file?

See docs

This seemed to work for me: osm_path = openstudio.path('tmp.osm') vt = openstudio.osversion.VersionTranslator() new_osm

This seemed to work for me: osm_path = openstudio.path('tmp.osm') vt = openstudio.osversion.VersionTranslator() new_osm

You can change the setpoint manager, or try to actuate the schedule/curve fields within the setpoint manager that you're

You need to find an actuator within this section. You cannot just actuate anything you want. There must be a predefined

What about using a scheduled setpoint manager and then actuating the schedule?

I think you need to add a .get(). Your second attempt seems correct, just add .get(). It's returning an optional without

I think you need to add a .get(). Your second attempt seems correct, just add .get(). It's returning an optional.

See example files here. This sums the outdoor dry-bulb temperature for every timestep.

See attached example files here. This example sums the outdoor dry-bulb temperature for every timestep.

In regards to the doc suggestion; first, I see what you're saying, but in traditional EMS you do not use output variable

I would suggest using Output:Variables whenever possible. Output:Meters can give inconsistent results depending on the m

I think this is expected behavior. I am pretty sure the cumulative reporting happens only when the simulation completes.

I am not sure I totally understand your question, but the IDF version updater .xls and .md files (C:\EnergyPlusV9-5-0\Pr

See here?

You could try: Convert a TMY EPW to CSV, replace the solar columns with custom data, then convert back to EPW. Use the

You could try: Convert a TMY EPW to CSV, replace the solar columns with custom data, then convert back to EPW. Use the

Gotcha. I think you can use the python code you originally referenced to download all the stat files (example url: https

Gotcha. I think you can use the python code you originally referenced to download all the stat files (example url: https

v3 of EnergyPlus?

See Section 4.3 of https://www.nrel.gov/docs/fy10osti/47867.pdf.

I agree that schedule values of zero would always result in zero people. Based on the documentation any value is allowed

A more universal solution may be to "sense" the value of the number of people schedule name, then actuate the number of

A more universal solution may be to "sense" the value of the number of people schedule name, then actuate the number of

Can you share the IDF?

It sounds like you have a model with very little internal mass. You can add internal mass objects directly to model item

I have a feeling the value of number of people schedule name is still multiplied by the number of people after it is act

You could indirectly control the capacity with these actuators. Controlling the mass flow rate and supply temperature/hu

First read this. Summarily, a user can add an object to the IDF to get all possible outputs for that IDF. So, adding som

Can you please provide a little more detail? Are the refrigerated cases stand-alone or is it a multiplex rack system? I

You could use EP-Launch to run groups of files or use the EnergyPlus command line interface.

I was not able to completely follow your code, but I did try to write a simpler program that set the outdoor air conditi

It might be helpful to know the weather data source(s). For example, if using data from http://climate.onebuilding.org/,

Also check out Chapter 10 of the EnergyPlus Engineering Reference for more autosizing information.

The docs state that this field is currently only applicable when sizing plant loops using the sizing option called Coinc

You want the "Do Zone Sizing" field in the SimulationControl object set to 'Yes' if you have Sizing:Zone objects in the

What "calling point" are you using? Like on_begin_timestep_before_predictor, on_begin_new_environment, etc.?

Got it. Some options I see include: Use the stat file. David gave an example regular expression. Probably easiest if t

Using the stat file might be the best option. Can you provide mode detail? Where are the EPW files from? Are they specif

Is the Run Simulation for Sizing Periods field in the SimulationControl object set to No? Setting that to No may fix the