Thanks, @MichaelDonn . You won me over and, in the last couple of days, I actually found a way to implement this longest list logic in a way that makes the code much cleaner/read-able, which was actually my bigger concern since the increase in runtime is pretty negligible (you aren’t going to feel it until you get up to 1,000 zones or so). So I think I’ll use this longest list logic in a few components that apply properties to rooms:
- HB Window Opening
- HB Apply Load Values
- HB Apply Setpoint Values
- HB Apply Room Schedules
- HB Apply ProgramType
And I opened an issue about it:
But I plan to not touch the components that apply properties to surfaces like the “HB Make Adiabatic” or the “HB Apply Opaque Construction” since these components use a different interpretation of list logic (applying different properties to surfaces that face different orientations if a list is input). If people need the same capabilities with these components, they can use Data Trees.