Context Navigation

Changes between Initial Version and Version 1 of Ticket #5452, comment 31

-              initial
+              v1
 inductor.inductor[1].i + inductor.inductor[2].i + inductor.inductor[1].i = 0.0
 }}}
 Which is exactly what we are looking for.
+Which is exactly what we are looking for :)
 As I understand it, the what makes this model different from the ones where omc works is that the current in each of the three conductors is split in two branches. How exactly that is done is irrelevant (the specific diode equations do not enter into the set of constraint equations), what is important is the balance of currents at the connection nodes.
+As I understand it, what makes this model different from the ones where omc works is that the current in each of the three conductors is split in two branches. How exactly that is done is irrelevant (the specific diode equations do not enter into the set of constraint equations), what is important is the balance of currents at the connection nodes.
 We should investigate why {{{resolveLoops}}} does not figure this out, and extend that algorithm to also handle this case. Then, we should also consider whether to make {{{resolveLoops}}} active by default, as it may be essential in handling some models which are found out there. Unfortunately we can't think of trying it after index reduction has failed, because the failure is not structural (which could be caught by the backend), but rather numerical, and so only visible at runtime, se we'd need to make sure that resolveLoops always works fine.