You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on reading the code, this appears to be broken, but I haven't produced a defect file to prove this.
The whole max/min people thing in ZoneEquipmentManager::SetUpZoneSizingArrays is broken if there is more than one People object in a zone and the schedules are not the same.
And ZoneMinOccupancy is wrong if there is more than one People object regardless of schedules, because it's multiplying repeatedly by the min schedule value.
Issue overview
Based on reading the code, this appears to be broken, but I haven't produced a defect file to prove this.
The whole max/min people thing in ZoneEquipmentManager::SetUpZoneSizingArrays is broken if there is more than one People object in a zone and the schedules are not the same.
And ZoneMinOccupancy is wrong if there is more than one People object regardless of schedules, because it's multiplying repeatedly by the min schedule value.
A code snippet to illustrate, from SetUpZoneSizingArrays.
Details
Some additional details for this issue (if relevant):
Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
The text was updated successfully, but these errors were encountered: