marcel hendrix

This would mean that the delay control input should be inhibited until T = T_present + T_delay(new) ? That should be easy to do (but complex to predict what its effect will be).

The IPC additions make debugging really difficult with all these alternative code paths. I didn't use it when I needed something like this because it was unclear what IPC/ATESSE does exactly and how it should be used. The proper thing to do to appease dusty deck users might be to conditionally compile the code and announce that it will be removed in future releases. IIRC, removing the code is not really simple as it hooks into details of the time stepper.

OK. It looks to me that hybrids are supposed to do something with g_mif_info.breakpoint.current as soon as they know that the analog timestep is final. That could be difficult. The hybrid codes can't simply wait until EVTcall_hybrids() happens, because what they want to do next might depend on what other hybrids are going to do with breakpoint.current and there would be a deadlock. If the closest breakpoint simply wins, it could be that the state of the all the loosing hybrids must be recomputed....

... as hybrid (analog+digital) device instances already get a look at the solution just before it is committed ... Please expand a bit on this?

Who do you want to embrace this standard? I am sure end-users will love it, but they won't engage in defining and standardizing the interface(s). For simulator dev teams it is easy to give input (e.g for NGSPICE it's exactly the XSPICE interface) but getting all these interfaces aligned will be an unappetizing political, not a technical, battle. However, I know from personal experience that it would be very beneficial for non-SPICE tools to integrate/define a SPICE component. For instance, microcontroller...

Who do you want to embrace this standard? I am sure end-users will love it, but they won't engage in defining and standardizing the interface(s). For simulator dev teams it is easy to give input (e.g for NGSPICE it's exactly the XSPICE interface) but getting all these interfaces aligned will be a unappetizing political, not a technical battle. However, I know from personal experience that it would be very beneficial for non-SPICE tools to integrate/define a SPICE component. For instance, microcontroller...

Coupling factor (wrongly) required to be positive

Here you have two (intended to be behavioral) current sources Vx2 and Vx3 (better call them Bi1 and Bi2), with the same node label X1. Do you really want to put them in parallel? Also, I wouldn't give a node the name of a possible device. Again, please supply a netlist.