Update Spawn autosizing documentation - #69
Conversation
| ``Sizing:Zone`` object may reference a zone directly or reference a ``ZoneList``; | ||
| Spawn resolves these references without regard to letter case. If autosizing is | ||
| requested but the idf file has no ``Sizing:Zone`` objects, Spawn issues a warning and | ||
| the sizing parameters retain their default values. |
| Spawn removes interzonal air exchange objects from the idf file. It also removes | ||
| infiltration objects for zones that are connected to Modelica and inserts zero-flow | ||
| infiltration objects for these zones. Infiltration objects for zones that are used only | ||
| for system sizing and are not connected to Modelica remain in the idf file. |
There was a problem hiding this comment.
@kbenne "Infiltration objects for zones that are used only
for system sizing and are not connected to Modelica remain in the idf file."
Is this true also for simulation? Hence, maybe the sentence should read something like, "Infiltration objects for zones that are used only for system sizing and boundary conditions during simulation and are not represented as thermal zones in Modelica remain in the idf file."
?
| heating load, outdoor air temperature and humidity at the design condition, minimum | ||
| outdoor air mass flow rate, and time within the sizing day when the design load occurs. | ||
| For each connected zone, Spawn also exposes the zone temperature and humidity set | ||
| points. These set points are continuous FMU outputs rather than calculated parameters, |
There was a problem hiding this comment.
@kbenne Is it true that set points are continuous FMU outputs rather than parameters? On the Modelica side, we retrieve those values as parameters, just like all the other autosizing parameters, see https://github.com/lbl-srg/modelica-buildings/blob/issue3866_24_2_0_autosize/Buildings/ThermalZones/EnergyPlus_24_2_0/BaseClasses/ThermalZoneAdapter.mo#L164.
UPDATE: Ok I see indeed I see in the fmu xml that they are fmi outputs. The Modelica code assigning them to parameter values upon initialization still seems to work. Any reason to make them continuous outputs of the FMU? Do they change with time for all time points in the simulation?
2 participants
No description provided.