akat022's profile - activity

Thank you very much, have tried this and now the sizing results are consistent!

I am running a co-simulation with Energyplus (v8.5) and Python using the PyEp package (https://pyep.readthedocs.io/en/latest/). The energyplus model is based of the DOE 'Large Office' archetype model (https://www.energy.gov/eere/buildings...).

I want to validate the performance of the co-simulation by comparing the results with the reference file run straight from energyplus. For this example, I am changing the following setpoints such that they follow the original schedule of the reference file:

• CLGSETP_SCH
• CW-Loop-Temp Sched
• BLD_LIGHT_SCH

Upon running both simulations and comparing results, I find that the results of the sizing are different, e.g. the component sizing results.

Based on this, I suspected that the sizing is being run differently in the co-simulation from the reference simulation. One reason I can see for this is that the zone temperature setpoints for the winter design day and summer design day in the schedules is missing (as the "Schedule:Compact" object needs to be deleted in place of the "ExternalInterface:Schedule" object). This point was actually also mentioned in the following unmethours post (although without a solution): https://unmethours.com/question/25753...

So my question is how the zone temperature setpoint (which is one of my manipulated/control variables) information for the design winter and summer days can be fed to the co-simulation?

I did find the following in the External Interfaces Application Guide (https://energyplus.net/sites/default/files/pdfs_v

Energyplus co-simulation - sizing results different I am running a co-simulation with Energyplus (v8.5) and Python using

I have bumped into this same problem wanting to implement a hot water TES but have been frustrated by the lack of the "U

I note that the "Plant Application Guide" Example System 2 covers only a TES for the chilled water loop. Do you know of

Thank you! Making the change to the name of the People object did the trick.

I am trying to implement thermostatic control of a zone based on PMV values (Fanger Comfort Criteria) using EMS in Energyplus. I add an EnergyManagementSystem:Sensor object as per the example in the InputOutput Reference documentation as follows (except the sensor is called "currentPMV" and I am trying to extract the value for the "Core_mid" zone):

EnergyManagementSystem:Sensor,
currentPMV,              !- Name
Core_mid,                !- Output:Variable or Output:Meter Index Key Name
Zone Thermal Comfort Fanger Model PMV;  !- Output:Variable or Output:Meter Name

I also define the Output:variable as follows:

Output:Variable,Core_mid,Zone Thermal Comfort Fanger Model PMV ,Timestep;

When I try to simulate, I obtain the following Severe error:

   ** Severe  ** Invalid Output:Variable or Output:Meter Index Key Name =CORE_MID
   **   ~~~   ** For Output:Variable or Output:Meter = ZONE THERMAL COMFORT FANGER MODEL PMV
   **   ~~~   ** Entered in EnergyManagementSystem:Sensor=CURRENTPMV
   **   ~~~   ** Unique Key Name not found.

I have checked that "Zone Thermal Comfort Fanger Model PMV" is listed in the .rdd file. I have also checked that "Core_mid" is a valid zone. I have tried changing the field to other zone names and obtain the same error. Does anyone know why "Core_mid" is not being recognized as a unique key name?

Any help is much appreciated.

Output variable unique Key name for EnergyManagementSystem:Sensor Hi all, I am trying to implement thermostatic control