Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include impact of AirTerminal:SingleDuct:Mixer in ZoneHVAC coil sizing #6788

Conversation

rraustad
Copy link
Contributor

@rraustad rraustad commented Jun 19, 2018

Pull request overview

Zone equipment does not include impacts of DOAS system (i.e., when zone equipment uses AirTerminal:SingleDuct:Mixer) on coil inlet conditions during sizing. This corrects Issue #6712. Cooling coil sizing now includes the impact of the DOAS air stream, either conditioned or unconditioned, on the mixed inlet condition of the zone equipment's cooling coil. This change will typically allow smaller cooling coil sizes.

Zone models included in this update:

  • ZoneHVAC:FourPipeFanCoil
  • ZoneHVAC:WaterToAirHeatPump
  • ZoneHVAC:PackagedTerminalAirConditioner
  • ZoneHVAC:PackagedTerminalHeatPump
  • ZoneHVAC:TerminalUnit:VariableRefrigerantFlow
  • ZoneHVAC:UnitVentilator
  • AirLoopHVAC:UnitarySystem

Work Checklist

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

  • Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
  • At least one of the following appropriate labels must be added to this PR to be consumed into the changelog:
    • Defect: This pull request repairs a github defect issue. The github issue should be referenced in the PR description
    • Refactoring: This pull request includes code changes that don't change the functionality of the program, just perform refactoring
    • NewFeature: This pull request includes code to add a new feature to EnergyPlus
    • Performance: This pull request includes code changes that are directed at improving the runtime performance of EnergyPlus
    • DoNoPublish: This pull request includes changes that shouldn't be included in the changelog

Review Checklist

This will not be exhaustively relevant to every PR.

  • Code style (parentheses padding, variable names)
  • Functional code review (it has to work!)
  • If defect, results of running current develop vs this branch should exhibit the fix
  • CI status: all green or justified
  • Performance: CI Linux results include performance check -- verify this
  • Unit Test(s)
  • C++ checks:
    • Argument types
    • If any virtual classes, ensure virtual destructor included, other things
  • Documentation changes in place
  • Changed docs build successfully

@@ -3577,6 +3609,102 @@ namespace ReportSizingManager {
}
}

void setHeatingOAFracAndInletTempForZoneEq(Real64 &OutAirFrac, Real64 &CoilInTemp, Real64 &DesMassFlow)
Copy link
Contributor Author

@rraustad rraustad Jun 19, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anyone want to comment on these new functions? Too busy? Break out OutAirFrac, CoilInTemp and CoilInHumRat to individual functions? If change to individual functions change to Real64 instead of void ? etc.

@rraustad
Copy link
Contributor Author

Interesting. Won't build on the CI but builds at work and home on 64 bit Windows 7 and 8.

EXPECT_NEAR(WaterCoil(CoilNum).InletAirTemp, -1.99999, 0.0001); // a mixture of zone air (20 C) and 10% OA (-20 C) = 16 C
EXPECT_NEAR(WaterCoil(CoilNum).DesTotWaterCoilLoad, 3908.2603, 0.0001);
EXPECT_NEAR(WaterCoil(CoilNum).UACoil, 94.9905, 0.0001);
EXPECT_NEAR(WaterCoil(CoilNum).OutletAirTemp, 30.2984, 0.0001); // reasonable delta T above inlet air temp
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made this change just to get it to pass. Have already corrected these so that the results are identical to before.

ZoneEqSizing(CurZoneEqNum).OAVolFlow = FanCoil(FanCoilNum).OutAirVolFlow;
if (FanCoil(FanCoilNum).ATMixerExists) {
SingleDuct::setATMixerSizingProperties(FanCoil(FanCoilNum).ATMixerIndex, ControlledZoneNum, CurZoneEqNum);
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This function will be used in each zone equipment type to set up ATMixer inlet conditions.

// CoilInTemp = (1.0 - OutAirFrac) * FinalZoneSizing(CurZoneEqNum).ZoneTempAtHeatPeak +
// OutAirFrac * FinalZoneSizing(CurZoneEqNum).OutTempAtHeatPeak;
// this will change above CoilInTemp equation to use ZoneRetTempAtHeatPeak which accounts for lights to return fraction
CoilInTemp = setHeatCoilInletTempForZoneEqSizing(setOAFracForZoneEqSizing(DesMassFlow));
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The coil inlet condition is now a function call which replaces many duplicate code blocks.

ZoneEqSizing(curZoneEqNum).ATMixerHeatPriHumRat = SysSizInput(sysSizIndex).HeatSupHumRat;
}
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is the ATMixer function that sets up inlet conditions the same for all equipment.

coilInTemp = (1.0 - outAirFrac) * DataSizing::FinalZoneSizing(DataSizing::CurZoneEqNum).ZoneRetTempAtCoolPeak +
outAirFrac * DataSizing::ZoneEqSizing(DataSizing::CurZoneEqNum).ATMixerCoolPriDryBulb;
} else if (DataSizing::ZoneEqSizing(DataSizing::CurZoneEqNum).OAVolFlow > 0.0) { // adjust for raw OA mixed inlet temp
coilInTemp = (1.0 - outAirFrac) * DataSizing::FinalZoneSizing(DataSizing::CurZoneEqNum).ZoneTempAtCoolPeak +
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably use ZoneRetTempAtCoolPeak as setHeatCoilInletTempForZoneEqSizing does.

@rraustad
Copy link
Contributor Author

@mjwitte @Myoldmopar @EnergyArchmage this is the method used to update fan coil units to include ATMixer impact on coil sizing. This method will be ported to all other zone equipment types so if there is a comment on chosen method now is the time to comment.

@rraustad rraustad self-assigned this Jun 20, 2018
@rraustad rraustad added Defect Includes code to repair a defect in EnergyPlus PriorityHigh This defect or feature has been declared high priority labels Jun 20, 2018
@rraustad
Copy link
Contributor Author

Here's some results for the DOAToFanCoilInlet example file. Sizing apparently thinks the OA is zero for the fan coil. Sizing also doesn't know there is an ATMixer attached.

Sizing:Zone,
  SPACE1-1,                !- Zone or ZoneList Name
  SZ DSOA SPACE1-1,        !- Design Specification Outdoor Air Object Name

DesignSpecification:OutdoorAir,
  SZ DSOA SPACE1-1,        !- Name
  flow/person,             !- Outdoor Air Method
  0.00944,                 !- Outdoor Air Flow per Person {m3/s-person}
  0.0,                     !- Outdoor Air Flow per Zone Floor Area {m3/s-m2}
  0.0;                     !- Outdoor Air Flow per Zone {m3/s}

ZoneHVAC:FourPipeFanCoil,
  SPACE1-1 Fan Coil,       !- Name
  FanAvailSched,           !- Availability Schedule Name
  ConstantFanVariableFlow, !- Capacity Control Method
  autosize,                !- Maximum Supply Air Flow Rate {m3/s}
  ,                        !- Low Speed Supply Air Flow Ratio
  ,                        !- Medium Speed Supply Air Flow Ratio
  0,                       !- Maximum Outdoor Air Flow Rate {m3/s}
  ,                        !- Outdoor Air Schedule Name
  SPACE1-1 Fan Coil Inlet, !- Air Inlet Node Name
  SPACE1-1 Supply Inlet,   !- Air Outlet Node Name
  ,                        !- Outdoor Air Mixer Object Type
  ,                        !- Outdoor Air Mixer Name

AirTerminal:SingleDuct:Mixer,
  SPACE1-1 DOAS Air Terminal,  !- Name
  ZoneHVAC:FourPipeFanCoil,!- ZoneHVAC Unit Object Type
  SPACE1-1 Fan Coil,       !- ZoneHVAC Unit Object Name
  SPACE1-1 Fan Coil Inlet, !- Mixer Outlet Node Name
  SPACE1-1 Air Terminal Mixer Primary Inlet,  !- Mixer Primary Air Inlet Node Name
  SPACE1-1 Air Terminal Mixer Secondary Inlet,  !- Mixer Secondary Air Inlet Node Name
  InletSide;               !- Mixer Connection Type

So when the ATMixer impact on mixed air conditions is considered, the inlet conditions to the coil are actually lower than is shown in the current develop branch. So coil sizing is now impacted for inlet ATMixers. Basically lower cooling and higher heating coil sizes.

doatofancoilinlet

@rraustad
Copy link
Contributor Author

There are diff's showing in UnitVentilator when I only added the new ATMixer function call to fan coils. This is because I changed the return temp from ZoneTempAtHeatPeak to ZoneRetTempAtHeatPeak to account for lighting heat to return. Not sure if that makes sense now but will think more about it. Reverting this for now to get to minimal, and explainable, diff's before moving on.

@@ -6015,6 +6015,26 @@ namespace SingleDuct {
}
}

void setATMixerSizingProperties(int const &inletATMixerIndex, int const &controlledZoneNum, int const &curZoneEqNum)
{
ZoneEqSizing(curZoneEqNum).ATMixerVolFlow = SingleDuct::SysATMixer(inletATMixerIndex).DesignPrimaryAirVolRate;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe I should move this air vol flow down into if (SizingDesRunThisAirSys) so that all are set or none are set?

@rraustad
Copy link
Contributor Author

Perfect, now only the 7 fan coil example files have diff's. I'll worry about that subtle change to the coil inlet temp calc later. I can now move on and make the simple change to all other zone equipment. Should be easy sailing now. This code snippet should be all that is needed in other zone equipment sizing routines (before any child equipment are called).

if (FanCoil(FanCoilNum).ATMixerExists) {
    SingleDuct::setATMixerSizingProperties(FanCoil(FanCoilNum).ATMixerIndex, ControlledZoneNum, CurZoneEqNum);
}

@rraustad
Copy link
Contributor Author

Just figuring out which zone temp to use for zone equipment. The only difference I see is:

if (ReturnNode > 0) {
    RetTemp = Node(ReturnNode).Temp;
} else {
    RetTemp = Node(ZoneNode).Temp;
}

CalcZoneSizing(CurOverallSimDay, ControlledZoneNum).HeatZoneRetTemp = RetTemp;
CalcZoneSizing(CurOverallSimDay, ControlledZoneNum).CoolZoneRetTemp = RetTemp;

So why would zone equipment ever use return temp to size the coils? Zone equipment draws air from the zone and any heat gain to return should be met by the air loop. And when there is no air loop these are the same value. I am now thinking this was just a mistake during equipment model development and it propagated through to some/all zone equipment models. There is going to be diffs during sizing consolidation, probably for zone equipment that serve the same zone as an air loop, but I wonder if I want to tackle that here or in a different issue. Leaning towards saving this for the existing sizing consolidation issue #6172.

…irTerminalSingleDuctMixer' of https://github.com/NREL/EnergyPlus into #6712-Zone-Coil-Autosizing-does-not-include-impact-of-AirTerminalSingleDuctMixer
@rraustad rraustad changed the title First pass at including ATMixer in fan coil sizing Include impact of AirTerminal:SingleDuct:Mixer in ZoneHVAC coil sizing Jun 21, 2018
@rraustad
Copy link
Contributor Author

@Myoldmopar @mjwitte this should now be complete. I will review CI diffs and try to post more comparisons.

@rraustad
Copy link
Contributor Author

Seeing non-DOAS diffs with fan coils I am switching back to ZoneRetTemp on the else to see if that fixes non-DOAS files. Also flipped priority on CoolingCapacitySizing to honor ATMixer over anything else.

@mjwitte
Copy link
Contributor

mjwitte commented Sep 13, 2018

Regarding the new warnings, 7 files now have warnings. Good to exercise the warnings here, but now we need to correct those test files so the warnings go away.

In DOAToUnitarySystem, the warnings are happening twice per zone.

In OutdoorAirUnit and OutdoorAirUnitwithAirloopHVAC (and maybe others), the desiccant regen coil capacity has changed - it shouldn't.

Minor - the warnings seem a bit verbose.

   ** Warning ** AirTerminal:SingleDuct:Mixer: SPACE1-1 DOAS AIR TERMINAL
   **   ~~~   **  Sizing:Zone object sets input Account for Dedicated Outdoor Air System = Yes.
   **   ~~~   **  This inlet side Air Terminal Mixer will also adjust coil sizing and may result in inappropriately sized coils.
   **   ~~~   **  Set Account for Dedicated Outdoor Air System = No in Sizing:Zone object for zone = SPACE1-1

   ** Warning ** AirTerminal:SingleDuct:Mixer: SPACE4-1 DOAS AIR TERMINAL
   **   ~~~   **  Sizing:Zone object sets input Account for Dedicated Outdoor Air System = No.
   **   ~~~   **  This supply side Air Terminal Mixer will not adjust coil sizing and may result in inappropriately sized coils.
   **   ~~~   **  Set Account for Dedicated Outdoor Air System = Yes in Sizing:Zone object for zone = SPACE4-1

Suggest

   ** Warning ** AirTerminal:SingleDuct:Mixer: SPACE1-1 DOAS AIR TERMINAL
   **   ~~~   **  Inlet side Air Terminal Mixer automatically adjusts zone equipment coil sizing.
   **   ~~~   **  Set Account for Dedicated Outdoor Air System = No in Sizing:Zone object for zone = SPACE1-1.

   ** Warning ** AirTerminal:SingleDuct:Mixer: SPACE4-1 DOAS AIR TERMINAL
   **   ~~~   **  Supply side Air Terminal Mixer does not adjust zone equipment coil sizing and may result in inappropriately sized coils.
   **   ~~~   **  Set Account for Dedicated Outdoor Air System = Yes in Sizing:Zone object for zone = SPACE4-1.

@mjwitte
Copy link
Contributor

mjwitte commented Sep 13, 2018

DOAToPTAC - Current results show the heating coil sensible capacity is now the same as total (that was broken before), but the coil inlet temp is the OA temp? And cooling coil inlet conditions are nearly the same as outdoor also? In the component sizing summary design cooling and heating flow rates for the PTAC 1-1 are both 0.22, and the ATMixer flow rate is 0.0572, so it seems like the coil entering conditions should be closer to zone conditions than outdoor. But the coil sizing details show the heating coil design flow rate at 0.572? Similar questions for other systems.

@rraustad
Copy link
Contributor Author

Looking at OutdoorAirUnit at the moment. The heating coil is sizing differently because I added the new function call in heating coils thinking it would reduce code. What is happening is that the desiccant heating coil previously sized using DesHeatCoilInTemp and now it sizes using ZoneTempAtHeatPeak, which is of course wrong. The OAUnit sizing function doesn't set ZoneEqSizing::OAVolFlow (it does now). The problem I see here is that zone sizing does not know what type of equipment there is or how many. In this case there is only the OutdoorAirUnit. But what if there were the OAUnit and a PTAC with no OA, then the PTAC would be using -17C to size the heating coil? I've seen this before with the OA unit. My change corrects the heating coil size but there is still this other lurking issue. Now on to other things you noticed.

ZoneHVAC:EquipmentConnections,
  SPACE1-1,                !- Zone Name
  Zone1Equipment,          !- Zone Conditioning Equipment List Name
  Zone1Inlets,             !- Zone Air Inlet Node or NodeList Name
  Zone1Exhausts,           !- Zone Air Exhaust Node or NodeList Name
  Zone 1 Node,             !- Zone Air Node Name
  Zone 1 Outlet Node;      !- Zone Return Air Node or NodeList Name

ZoneHVAC:EquipmentList,
  Zone1Equipment,          !- Name
  SequentialLoad,          !- Load Distribution Scheme
  ZoneHVAC:OutdoorAirUnit, !- Zone Equipment 1 Object Type
  Zone1OutAir,             !- Zone Equipment 1 Name
  1,                       !- Zone Equipment 1 Cooling Sequence
  1;                       !- Zone Equipment 1 Heating or No-Load Sequence

Sizing:Zone,
  SPACE1-1,                !- Zone or ZoneList Name
  SZ DSOA SPACE1-1,        !- Design Specification Outdoor Air Object Name

DesignSpecification:OutdoorAir,
  SZ DSOA SPACE1-1,        !- Name
  Flow/Zone,               !- Outdoor Air Method
  0,                       !- Outdoor Air Flow per Person {m3/s-person}
  0.0,                     !- Outdoor Air Flow per Zone Floor Area {m3/s-m2}
  0.42;                    !- Outdoor Air Flow per Zone {m3/s}

desiccantheatingcoilsizing

@rraustad
Copy link
Contributor Author

For DOAToPTAC, when capacity is sized, where CoilInTemp is also set and used to calculate capacity, the capacity gets reported but the coil conditions do not. So at the bottom of request sizing where capacity is reported, when it jumps over the setCoilCoolingCapacity, that function sets coil inlet temp as the ATMixer primary air temp. Since there are no coils in the ATMixer, the supply air temp = OA temp. I have fixed this over in #5763 (New Feature - Include fan heat in coil sizing). I've got a lot of kettles on the fire. Maybe a followup issue to make sure these are corrected after all PR's are merged? Or merge in those changes here to get these results correct?

coilselectionsizingissue

@rraustad
Copy link
Contributor Author

I've fixed the duplicate warnings and desiccant heating coil sizing issues. Just need to push those changes.

@mjwitte
Copy link
Contributor

mjwitte commented Sep 13, 2018

Would it be better to review and merge the fan heat PR before this to set a new baseline for comparison?

@rraustad
Copy link
Contributor Author

Good idea. That would fix this last issue when merged into this branch.

@mjwitte
Copy link
Contributor

mjwitte commented Sep 14, 2018

@rraustad Please resolve the conflict here and merge up today if you can.

…-Zone-Coil-Autosizing-does-not-include-impact-of-AirTerminalSingleDuctMixer
@rraustad
Copy link
Contributor Author

Need to verify this comment when results are available:

DOAToPTAC - Current results show the heating coil sensible capacity is now the same as total (that was broken before), but the coil inlet temp is the OA temp? And cooling coil inlet conditions are nearly the same as outdoor also? In the component sizing summary design cooling and heating flow rates for the PTAC 1-1 are both 0.22, and the ATMixer flow rate is 0.0572, so it seems like the coil entering conditions should be closer to zone conditions than outdoor. But the coil sizing details show the heating coil design flow rate at 0.572? Similar questions for other systems.

@mjwitte
Copy link
Contributor

mjwitte commented Sep 14, 2018

Just to be clear, the "0.572" should be "0.0572" - equal to the OA flow.

@rraustad
Copy link
Contributor Author

So if PTAC flow = OA flow then coil inlet temp = OA temp.

@mjwitte
Copy link
Contributor

mjwitte commented Sep 14, 2018

Yes, but the question here is that the reported design cooling and heating flow rates for the PTAC 1-1 are both 0.22, so why is it sizing the heating coil for only 0.0572?

@rraustad
Copy link
Contributor Author

Looking at this now, DOAToPTAC. I see that SPACE1-1 PTAC air flow is sized larger than before. This is a little surprising since I only expect coil entering/exiting conditions (and capacity) to change. So comment here if you wish as I look at what is happening.

 ! <Component Sizing Information>, Component Type, Component Name, Input Field Description, Value
- Component Sizing Information, ZoneHVAC:PackagedTerminalAirConditioner, SPACE1-1 PTAC, Design Size Cooling Supply Air Flow Rate [m3/s], 0.22088
- Component Sizing Information, ZoneHVAC:PackagedTerminalAirConditioner, SPACE1-1 PTAC, Design Size Heating Supply Air Flow Rate [m3/s], 0.22088
+ Component Sizing Information, ZoneHVAC:PackagedTerminalAirConditioner, SPACE1-1 PTAC, Design Size Cooling Supply Air Flow Rate [m3/s], 0.26879
+ Component Sizing Information, ZoneHVAC:PackagedTerminalAirConditioner, SPACE1-1 PTAC, Design Size Heating Supply Air Flow Rate [m3/s], 0.26879
  Component Sizing Information, ZoneHVAC:PackagedTerminalAirConditioner, SPACE1-1 PTAC, User-Specified No Load Supply Air Flow Rate [m3/s], 0.00000
- Component Sizing Information, Fan:OnOff, SPACE1-1 SUPPLY FAN, Design Size Maximum Flow Rate [m3/s], 0.22088
- Component Sizing Information, Coil:Cooling:DX:SingleSpeed, SPACE1-1 PTAC CCOIL, Design Size Rated Air Flow Rate [m3/s], 0.22088
- Component Sizing Information, Coil:Cooling:DX:SingleSpeed, SPACE1-1 PTAC CCOIL, Design Size Gross Rated Total Cooling Capacity [W], 5469.07698
- Component Sizing Information, Coil:Cooling:DX:SingleSpeed, SPACE1-1 PTAC CCOIL, Design Size Gross Rated Sensible Heat Ratio, 0.69880
+ Component Sizing Information, Fan:OnOff, SPACE1-1 SUPPLY FAN, Design Size Maximum Flow Rate [m3/s], 0.26879
+ Component Sizing Information, Coil:Cooling:DX:SingleSpeed, SPACE1-1 PTAC CCOIL, Design Size Rated Air Flow Rate [m3/s], 0.26879
+ Component Sizing Information, Coil:Cooling:DX:SingleSpeed, SPACE1-1 PTAC CCOIL, Design Size Gross Rated Total Cooling Capacity [W], 5858.00167
+ Component Sizing Information, Coil:Cooling:DX:SingleSpeed, SPACE1-1 PTAC CCOIL, Design Size Gross Rated Sensible Heat Ratio, 0.74025
 ! <DX Cooling Coil Standard Rating Information>, Component Type, Component Name, Standard Rating (Net) Cooling Capacity {W}, Standard Rated Net COP {W/W}, EER {Btu/W-h}, SEER {Btu/W-h}, IEER {Btu/W-h}
- DX Cooling Coil Standard Rating Information, Coil:Cooling:DX:SingleSpeed, SPACE1-1 PTAC CCOIL, 5297.4, 2.66, 9.07, 9.63, 9.51
+ DX Cooling Coil Standard Rating Information, Coil:Cooling:DX:SingleSpeed, SPACE1-1 PTAC CCOIL, 5649.2, 2.61, 8.92, 9.47, 9.28
  Component Sizing Information, Coil:Heating:Fuel, SPACE1-1 HEATING COIL, Design Size Nominal Capacity [W], 2899.74027

@rraustad
Copy link
Contributor Author

rraustad commented Sep 15, 2018

So it's sizing the heating coil based on the zone heating air flow rate (DesHeatMassFlow). This should probably size using the PTAC flow rate? But it's a fuel heating coil, you've told me many times that this type of coil shouldn't size the same as the DX. Shouldn't fix this here.

ZoneHVAC:PackagedTerminalAirConditioner,
  SPACE1-1 PTAC,           !- Name
  Coil:Heating:Fuel,       !- Heating Coil Object Type
  SPACE1-1 Heating Coil,   !- Heating Coil Name

heatcoilsizing

@rraustad
Copy link
Contributor Author

Bear in mind I could set any of these, HeatingCapacity, DataCoolCap or DataFlowUsedForSizing, But we have decided to size the heating coil based on the zone load when that coil wasn't DX.

            } else if (SizingType == HeatingCapacitySizing) {
                if (ZoneEqSizing(CurZoneEqNum).HeatingCapacity) {
                    NominalCapacityDes = ZoneEqSizing(CurZoneEqNum).DesHeatingLoad;
                    if (DataFlowUsedForSizing > 0.0) {
                        DesVolFlow = DataFlowUsedForSizing;
                    }
                } else if (DataCoolCoilCap > 0.0 && DataFlowUsedForSizing > 0.0) {
                    NominalCapacityDes = DataCoolCoilCap;
                    DesVolFlow = DataFlowUsedForSizing;
                } else if (FinalZoneSizing(CurZoneEqNum).DesHeatMassFlow >= SmallMassFlow) {
                    if (DataFlowUsedForSizing > 0.0) {
                        DesVolFlow = DataFlowUsedForSizing;
                    }

@mjwitte
Copy link
Contributor

mjwitte commented Sep 16, 2018

Regarding the PTAC heating coil sizing, I recall there have been some fixes to this over time. I'm going to move that file to Chicago and see if it can hold setpoint for a year. That checks out OK, very similar loads not met before and after this. However, for zones 4 and 5, the heating coils are signficantly smaller now than current develop. Running a design day zone 5 is ok, but zone 4 is maxing out the heating coil. So, PTAC may still need some work.

Here's some zips with results. I haven't looked at the other system types this closely.
6712-ATMixerSizing-After.zip
6712-ATMixerSizing-Before.zip

Reviewing the err diffs.
PackagedTerminalHeatPumpVSAS and PackagedTerminalAirConditionerVSAS have new warnings:

+   ** Warning ** ZoneHVAC:PackagedTerminalHeatPump - air flow rate = 0.2148646 in fan object is less than the MSHP system air flow rate when cooling is required (0.2725907).
+   **   ~~~   **  The MSHP system flow rate when cooling is required is reset to the fan flow rate and the simulation continues.
+   **   ~~~   **  Occurs in ZoneHVAC:PackagedTerminalHeatPump = ZONE2PTAC

DOAToFanCoilSupply and DOAToWaterToAirHPSupply

+   ** Warning ** AirTerminal:SingleDuct:Mixer: SPACE5-1 DOAS AIR TERMINAL
+   **   ~~~   **  Supply side Air Terminal Mixer does not adjust zone equipment coil sizing and may result in inappropriately sized coils.
+   **   ~~~   **  Set Account for Dedicated Outdoor Air System = Yes in Sizing:Zone object for zone = SPACE5-1

These should get cleaned up, but I'm not going to hold this up for that. You can throw in a separate little PR for that if there aren't any other changes to do here.

@mjwitte
Copy link
Contributor

mjwitte commented Sep 16, 2018

Probably should have some doc changes, too for this to explain the sizing difference for inletside vs supplyside, in the mixer object and in the Sizing:Zone DOAS fields.

@mjwitte
Copy link
Contributor

mjwitte commented Sep 17, 2018

But zone 4 is a supply side mixer, it maxes out the heating coil on the winter design day before this changes as well. Oh, I see, the DOAS inputs in Sizing:Zone don't work for Chicago, because it's an unconditioned DOAS. So, these example files could use a little more tweaking. Merging this.

@mjwitte
Copy link
Contributor

mjwitte commented Sep 17, 2018

But it would still be good to add some notes in the I/O Ref about when an what sizing does with ATMixers now.

@mjwitte mjwitte merged commit 40434b6 into develop Sep 17, 2018
@mjwitte mjwitte deleted the #6712-Zone-Coil-Autosizing-does-not-include-impact-of-AirTerminalSingleDuctMixer branch September 17, 2018 00:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Defect Includes code to repair a defect in EnergyPlus PriorityHigh This defect or feature has been declared high priority
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants