@macumber seemed to have good luck posting the ZoneMixing design doc on here so I'd like to join the action and ask some questions about availability managers. Is this a good pattern or are we abusing the system? Should it be tagged meta?

We are working on more support for availability mangers in OpenStudio. Here is the design document. I would appreciate comments.

Questions I am trying to work through...

Are these the right managers to support?

AvailabilityManager:Scheduled <-- Already supported
AvailabilityManager:NightCycle <-- Already supported
AvailabilityManager:HybridVentilation
AvailabilityManager:OptimumStart
AvailabilityManager:DifferentialThermostat
AvailabilityManager:NightVentilation

Do we need to support layering multiple managers like energyplus allows? I'm leaning one manager at a time. It gets a little confusing when you stack them up. I'm inclined to promote EMS if your logic gets so complicated that you need to stack managers.

Does the proposed API feel comfortable?

@macumber seemed to have good luck posting the ZoneMixing design doc on here so I'd like to join the action and ask some questions about availability managers. Is this a good pattern or are we abusing the system? Should it be tagged meta?

We are working on more support for availability mangers in OpenStudio. Here is the design document. I would appreciate comments.

Questions I am trying to work through...

Are these the right managers to support?

AvailabilityManager:Scheduled <-- Already supported
AvailabilityManager:NightCycle <-- Already supported
AvailabilityManager:HybridVentilation
AvailabilityManager:OptimumStart
AvailabilityManager:DifferentialThermostat
AvailabilityManager:NightVentilation

Do we need to support layering laying multiple managers like energyplus allows? I'm leaning one manager at a time. It gets a little confusing when you stack them up. I'm inclined to promote EMS if your logic gets so complicated that you need to stack managers.

Does the proposed API feel comfortable?

@macumber seemed to have good luck posting the ZoneMixing design doc on here so I'd like to join the action and ask some questions about availability managers. Is this a good pattern or are we abusing the system? Should it be tagged meta?

We are working on more support for availability mangers in OpenStudio. Here is the design document. I would appreciate comments.

Questions I am trying to work through...

Are these the right managers to support?

AvailabilityManager:Scheduled <-- Already supported
supported AvailabilityManager:NightCycle <-- Already supported
AvailabilityManager:HybridVentilation
AvailabilityManager:OptimumStart
AvailabilityManager:DifferentialThermostat
AvailabilityManager:NightVentilation
supported AvailabilityManager:HybridVentilation AvailabilityManager:OptimumStart AvailabilityManager:DifferentialThermostat AvailabilityManager:NightVentilation

Do we need to support laying multiple managers like energyplus allows? I'm leaning one manager at a time. It gets a little confusing when you stack them up. I'm inclined to promote EMS if your logic gets so complicated that you need to stack managers.

Does the proposed API feel comfortable?