Open DeadParrot opened 3 years ago
In SimpleHouse
, what state shows the noisy derivatives?
I have not yet tracked back the SimpleHouse behavior to the states that first mis-track like I did for TwoFloor_TwoZone (as in my Mar 25, 2021 email) but I can see the same effect of the QSS variant that does continuous trajectory propagation fixing mis-tracking for the rad.vol[*].dynBal.U variables.
Some Buildings library models have state variable derivatives, particularly those of self-observer variables, that have poor QSS derivative accuracy with noisy derivatives (distinct from any noise caused by numerical differentiation) that cause excessive requantizations and, sometimes, solution mis-tracking. This needs to be understood and addressed with QSS extensions and/or controls.
Analysis of this behavior revealed a few things:
--dtMax
small enough to essentially change QSS into a traditional uniform time stepping solver the solutions track correctly. This gives the clue that the problem is due to the mismatch between the variable states at step times and the between-step trajectory values propagated to derivative computations.Models showing this behavior include ASHRAE2006, TwoFloor_TwoZone, and SimpleHouse. The larger models are hard to diagnose with because the derivatives are built from deeply layered expressions that depend on some "opaque" internal FMU variables that are not exposed. The smaller SimpleHouse model is probably a better basis for diagnosing the behavior and will be used in the next phase of work on this issue.