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

Followup from Multiple Airloops #6264

Closed
10 of 13 tasks
mjwitte opened this issue Aug 23, 2017 · 2 comments
Closed
10 of 13 tasks

Followup from Multiple Airloops #6264

mjwitte opened this issue Aug 23, 2017 · 2 comments
Labels
PriorityHigh This defect or feature has been declared high priority

Comments

@mjwitte
Copy link
Contributor

mjwitte commented Aug 23, 2017

Issue overview

Problems noted after merge of #6248.

  • 5ZoneAirCooledWithDOASAirLoop - OA table output shows zero mechanical ventilation - that's wrong.
  • Unit tests
  • DOATToUnitVentilator node connection warnings DOATToUnitVentilator node connection errors #6273
  • Deal with furnaces searching for any ADU/DirectAir to find out the ZoneSequenceCoolingNum etc. - happens in Furnaces and HVACMultiSpeedHeatPump
  • Review whether optimum start avail managers really works with multiple airloops in the sames zone - if more than one is opt start then it may be goofy - so, as it stands if any airloop serving a given zone goes into optimal start, the thermostat setting will changes for all equipment serving that zone. That's true even with one airloop and other zone equipment.
  • Optimal start could be refactored to loop over the zones on the airloop instead of all zones for every decision
  • Sort out NoHeatToReturnAir node by node instead of zone by zone
  • Sort out zone loads in SystemReports::ReportSystemEnergyUse
  • Sort out unbalanced exhaust warnings - currently by zone, not by airloop in ZoneEquipmentManager::SimZoneEquipment
  • Sort out peak system load in OutputReportTabular::WriteComponentLoadSummaryTables

Details

Some additional details for this issue (if relevant):

  • Platform (Operating system, version)
  • Version of EnergyPlus (if using an intermediate build, include SHA)
  • Unmethours link or helpdesk ticket number

Checklist

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

  • Defect file added (list location of defect file here)
  • Ticket added to Pivotal for defect (development team task)
  • Pull request created (the pull request will have additional tasks related to reviewing changes that fix this defect)
@mjwitte mjwitte added the PriorityHigh This defect or feature has been declared high priority label Aug 23, 2017
@Myoldmopar
Copy link
Member

@mjwitte
Copy link
Contributor Author

mjwitte commented Sep 29, 2017

Closed via #6272

@mjwitte mjwitte closed this as completed Sep 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PriorityHigh This defect or feature has been declared high priority
Projects
None yet
Development

No branches or pull requests

2 participants