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
Is your feature request related to a problem? Please describe.
MMQ currently forwards the pin the input pin i.e. the output pin is explicitly set to the input pin. This usually works. However, in cases where any downstream module intends to receive inputs from the original modules & via MMQ module, it will fail. The framework will complain about a module getting same pin twice.
Describe the solution you'd like
MMQ should support forwarding the same pin or adding a new pin with the same metadata as input pin. So, although the pinId of the output pin from MMQ is different from input pin, it has same metadata.
Describe alternatives you've considered
None
Additional context
m1->m2
m1->mmq
mmq->m2
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
MMQ currently forwards the pin the input pin i.e. the output pin is explicitly set to the input pin. This usually works. However, in cases where any downstream module intends to receive inputs from the original modules & via MMQ module, it will fail. The framework will complain about a module getting same pin twice.
Describe the solution you'd like
MMQ should support forwarding the same pin or adding a new pin with the same metadata as input pin. So, although the pinId of the output pin from MMQ is different from input pin, it has same metadata.
Describe alternatives you've considered
None
Additional context
The text was updated successfully, but these errors were encountered: