You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While src and dest fields are unambiguous in the directionality of connections, that via shared message is bidirectional. If MOOSE is automatically ordering the subfields (dest and src) in a shared messaged, the outcomes should be identical irrespective of the order of the arguments to moose.connect. But in the example below, where I create two HHChannels, x and y and connect them a to a compartment comp, this is not the case:
While
src
anddest
fields are unambiguous in the directionality of connections, that viashared
message is bidirectional. If MOOSE is automatically ordering the subfields (dest and src) in a shared messaged, the outcomes should be identical irrespective of the order of the arguments tomoose.connect
. But in the example below, where I create twoHHChannels
,x
andy
and connect them a to a compartmentcomp
, this is not the case:Also, the incoming and outgoing message listings seem confusing.
The text was updated successfully, but these errors were encountered: