...
Rule 1 to 1
This rule means thathat the multiplexer gets one message from the first input port and one message from the 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 slots.
See an example workflow below:
| HTML |
|---|
<center>
<img src="/wiki/download/attachments/16126399/multiplexer_element_1to1.png"/>
</center>
|
As you can see:
- There are elements A, B, C, and the Multiplexer.
- A and B are data readers.
- A gets three data objects as input. These objects are denoted as I, II, and III. A has two slots, so the input data objects may also have various data. For example, this may be "Sequence" and "Set of annotations" slots and the data are read from three GenBank files.
- B gets two data objects as input. These objects are denoted as IV and V. B also has two slots in this example.
- C gets messages in the workflow from B. It has one output slot. For example, this may be "Set of annotations" slot, i.e. additional annotations were calculated for input objects IV and V.
- Now in the Multiplexer element we have three messages from A, that corresponds to the three input objects I, II, and III. And we have two messages from B and C elements, that corresponds to the two input objects IV and V with additional information, calculated in C.
- The multiplexer rule is "1 to 1". This means that we only take into account messages the have a pair. Thus the "Message 3" is ignored in this case. "Message 1" is concatenated with "Message 6" and produces "Message 8". "Message 2" is concatenated with "Message 7" and produces "Message 9".
Also see the Find Substrings at Sequences, Search for TFBS examples with Multiplexer element.
...