Not all OutputEvents are exposed as Ports in MultiDynamics

[tclose]

Not all OutputEvents are necessarily exposed as Ports in MultiDynamics objects. However, this is checked for in the Dynamics init method (L171 nineml/abstraction/dynamics/base.py). So really we should just check that all declared output event ports are in the list of inferred ports, not that the declared list is identical to the inferred one.

[tclose]

NB: output ports are "inferred" from output events

[sanchalitorpe13]

Hi @tclose,
I’d like to help with this issue. From what I understand, the check in Dynamics.init currently expects the declared output events list to exactly match the inferred ports list. A more robust approach might be to only ensure that all declared output events are present in the inferred ports, without requiring exact equality.

I can try implementing this change and add a test to confirm that MultiDynamics objects handle additional inferred ports correctly.