Notice that this model has the commando Linearise, simulate and plot. The model being linearised is IDEAS.LIDEAS.Examples.ZoneLinearise. The linearisation creates 3 text files and 1 mat file in the simulation folder: uNames_ZoneLinearise.txt (inputs name), xNames_ZoneLinearise.txt (state names), yNames_ZoneLinearise.txt (output names) and ssm_ZoneLinearise.mat (state space model). The name of the states were manually copied into the model to retrieve the initial state values. Also the input names were manually copied to feed their value to the SSM model included in this example. However, the input names winBusIn, weaBus, ctrlInput, and prescribed were renamed to winBusOut, weaBusOut, ctrlInputTest, and prescribedOut to coincide with the variables created in the model.
Notice that the error between the state space model output and the zone output is rather large. This is unusual and it is probably accentuated by the fact that the model is not very physical is (no roof, random dimensions, ...). IDEAS.LIDEAS.Validation.Case900ValidationNonLinearInputs shows that the error remains limited for more realistic models.
IDEAS.Media.Specialized.DryAir
.