...
This rule means that the multiplexer gets one message from the first input port and one message from the second input port, joins them into a single message, and transfers it to the output. This procedure is repeated while there are available messages in both input slotsports.
See an example workflow below:
| HTML |
|---|
<center> <img src="/wiki/download/attachments/16126399/multiplexer_element_1to1Multiplexer Element_1.png"/> </center> |
As you can see:
...
| HTML |
|---|
<center> <img src="/wiki/download/attachments/16126399/multiplexer_element_1toManyMultiplexer Element_2.png"/> </center> |
As you can see the conditions are the same as in the first "1 to 1" case, described above:
...
- "Message 1" + "Message 6" = "Message 8"
- "Message 1" + "Message 7" = "Message 9"
- "Message 2" + "Message 6" = "Message 10"
- "Message 2" + "Message 7" = "Message 11"
- "Message 3" + "Message 6" = "Message 12"
- "Message 3" + "Message 7" = "Message 13"
Parameters in GUI
| Parameter | Description | Default value |
|---|---|---|
| Multiplexing rule | Available values are:
See the detailed description of the values above. | 1 to 1 |
Parameters in Workflow File
Type: multiplexer
| Parameter | Parameter in the GUI | Type |
|---|---|---|
| multiplexing-rule | Multiplexing rule | string |
Input/Output Ports
The Multiplexer has element has ports, but it has not slots, because its use the whole data flow.
The element has 2 2 input port:
- The first input port:
- Name in GUI: First input
- port
- Name
- in Workflow File: input-data-1
- The second input port:
- Name in GUI: Second input
- port
- Name
- in Workflow File: input-data-2
The element has 1 output 1 output port:
- Name in GUI: Multiplexed output
- Name in Workflow File: output-data
Element in Samples
Also see the Find Substrings at Sequences, Search for TFBS examples with Multiplexer element.The element is used in the following workflow samples: