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
I have encountered this issue before, but I think I confused the diagnosis when I posted this issue. It appears that the default when creating a new OS model is that Do Zone Sizing Calculation and Do System Sizing Calculation is toggled off. Why is that? Without input from the users, I think by default these should be toggled on. For example, when I import spaces, create thermal zones and thermostats, and add an autosized Packaged Rooftop Air Conditioner and assign zones to the diffusers, these two remain toggled off. It then gives this error and the user has to diagnose the problem.
By default your model is empty. But we (the osapp) do initialize some of the singleton objects, one of which is the Simulation Control. Create a new model in the os app, save it as empty.osm, and looks inside you'll find this
So we report false, because that's what the getter gives us. And we do not want to hard-assign it to yes, because of the OS SDK EnergyPlus FT which tries to be smart about it, a behavior we want to retain.
Thank you @macumber.
I have encountered this issue before, but I think I confused the diagnosis when I posted this issue. It appears that the default when creating a new OS model is that Do Zone Sizing Calculation and Do System Sizing Calculation is toggled off. Why is that? Without input from the users, I think by default these should be toggled on. For example, when I import spaces, create thermal zones and thermostats, and add an autosized Packaged Rooftop Air Conditioner and assign zones to the diffusers, these two remain toggled off. It then gives this error and the user has to diagnose the problem.
Originally posted by @Ski90Moo in #691 (comment)
The text was updated successfully, but these errors were encountered: