Using MTK when I *import* ModelingToolkit?

[BLI]

@baggepinnen

Use complete(model).z for the output. It’s unfortunate that this discrepancy exists, but I think @cryptic.ax has some explanation for why it’s hard to get rid of.

Yeah, that also works. And it saves me from creating the “fictitious” downstream system.

Of course, if I produce true “components”, then the straightforward thing is to use “analysis point” names also for the output in linearize.

[baggepinnen]

@BLI

But with “analysis points”, I must instead think in terms of linearization from one connection point to another connection point.

I still think of this as linearizing between an input and an output. If there is nothing connected at either end, just use the variable rather than an analysis point, you should never have to create any dummy systems just for linearization to work.

@BLI

In my simple example above, at the outset, that is the only component there is, and there is no component upstream or downstream in the information flow.

So I need to create fictitious upstream and downstream “components”

no, if there is nothing connected, just use variables rather than analysis points.

[baggepinnen]

I just realized that I have in fact documented analysis points in a bit more detail here

Analysis Points | Dyad

This shows their use from Dyad, but they of course behave the same in MTK, it’s only the syntax for creating them that is slightly different. In MTK, you can create them by adding the name straight to a connection itself connect(out, :name, in).