This may be desired functionality or something that you may want to fix at some point (either in the code or manual)?
So, according to the manual of v. 4.5.7 oo_.steady_state contains the computed steady state. I don’t think this is true when an analytical steady state is provided using, say, the steady_state_model; block. The attached MWE demonstrates this (MWE.mod (373 Bytes)). Here oo_.steady_state contains three zeros, while the actual value of the steady state [1,1,1.0101] ends up in oo_.dr.ys.
Once steady; is invoked in the .mod file, however, everything will work as expected, and, in that case, oo_.steady_state will have the expected contents even in the presence of a steady_state_model; block…
Anyway, this slightly unexpected functionality was causing a bigger block of code I wrote to malfunction, so highlighting in case anyone else runs into similar issues.
Thanks and I hope this helps.