It seems that in the results table, EnergyPlus only defaults to outputting information for the heating design day or peak heating day. Why isn't it reporting information for July 21st as well as January 21st/is this something I can rectify?
In this case I'm running just for sizing days and am using Ideal Air Loads.
It looks to me as if you had no cooling energy transfer and the reported time is the first time step simulated. I would not expect the program to report July 21 if there was no cooling, since there was also no cooling Jan and this month was simulated first (I'm guessing). Then for July, 0 is not greater than 0, so the time stamp did not get updated. You could try switching the order of your design days and see if July 21 shows up in the table. But it's still 0 so what does the time stamp really mean?
Thanks @rraustad. I've attached an output (from the same run). Again, this was just run for my heating and cooling design days. If I'm understanding your response correctly - based on this output, I should expect to see cooling energy usage/demand for July 21 in the table I had originally uploaded. Correct?
Is there some other reason that only the first timestep is making it into that results table?
If the cooling energy transfer is really 0, then it should still be 0. From your plot it looks to be greater than 0. Look in the mtd file and search for "Cooling:EnergyTransfer" to see what this meter represents. Then look to those meters to see why the output is 0 (or if not send me your input file).
According to the mtd file, "Cooling[Heating]:EnergyTransfer" represents the sum of the "Zone Air System Sensible Cooling[Heating]Energy" for all zones. I'm not exactly sure of how to get from here to determining why the output is 0 though. What is best why to send you an idf? On a possibly unrelated note, if you look at the table I had added, it seems that the results from my first zone (0601) got mixed in with these last two whole-building meters. When I look at the structure of the mtd file, it makes sense that this is happening but I'm confused as to why it would be structured this way
Peak only happens once, either on the Heating Design Day or the Cooling Design day. It seems like you are not cooling the Space in the screenshot you sent. You can try looking at that variable in Dview.
That seems illogical to me. "Peak" can only occur on one of the two days (heating or cooling), but can occur during any hour of that day? You would think it would report the highest value recorded over the simulation, for each variable, and then apply the appropriate timestamp for both the day and hour.
Thanks for the downvote. It's expected that peak cooling happens during the summer design day and peak heating during the winter design day.
As it was pointed in the other answer, it seems like you don't have a cooling load therefore the "peak cooling" happens at the first timestep. It will not report anything on July 21 because nothing is happening. A load is not the same as a gain. Go check your thermostat settings.
Asked: 2018-11-21 10:45:49 -0600
Seen: 661 times
Last updated: Nov 30 '18
As an update: When I request that the simulation just run for the cooling design day, the values for peak cooling energy transfer are reported. And the value for Cooling:DistrictCooling matches the value shown in the plot that I have posted (above) from my original run.
So, this is definitely not an issue of there being no cooling load, it is simply a reporting issue that seems to exclude cooling design day peaks in favor of heating design day peaks for some reason. It'd be great to find a way around this - though doing separate runs for heating and cooling isn't the worst thing...