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.

Sign up for GitHub

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

Jump to bottom

Unitary system as both zone equipment and airloop equipment in the same file fails in v8.8 #6405

Closed
1 of 3 tasks
mjwitte opened this issue Nov 29, 2017 · 1 comment
Closed
1 of 3 tasks

Unitary system as both zone equipment and airloop equipment in the same file fails in v8.8 #6405

mjwitte opened this issue Nov 29, 2017 · 1 comment
Labels
PriorityHigh This defect or feature has been declared high priority

Comments

@mjwitte
Copy link
Contributor

mjwitte commented Nov 29, 2017 •
edited
Loading

Issue overview

Multiple airloop changes in #6248 required some rearranging of HVACUnitarySystem::GetUnitarySystemInputData to separate the input processing for unitary system as zone equipment and air loop equipment. This solved some issues with internal test files, but some files fail.

Details

Some additional details for this issue (if relevant):

  • Platform (Operating system, version)
  • Version of EnergyPlus 8.9.0 d8a479a
  • e-mail on 2017-11-28 from @rraustad

Checklist

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

  • Defect file added EnergyPlusDevSupport\DefectFiles
  • 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 mentioned this issue Nov 29, 2017
Merged
20 tasks
@mjwitte mjwitte added the PriorityHigh This defect or feature has been declared high priority label Nov 29, 2017
@rraustad
Copy link
Contributor

rraustad commented Dec 1, 2017

Closed via #6406.

@rraustad rraustad closed this as completed Dec 1, 2017
@kbenne kbenne mentioned this issue Mar 6, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
PriorityHigh This defect or feature has been declared high priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mjwitte @rraustad