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
In the description of Fork and ForkBranchhere, Fork "shows a set of mutually-exclusive alternatives". How are the mutually exclusive parameters in each ForkBranch written into the workflow function? Perhaps I confusing that fact that the interface elements are mutually exclusive, but the parameters are not?
E.g. I have one ForkBranch has a single parameter (single end FASTQ), and another ForkBranch that has two parameters (one for each end of paired end FASTQs). So the user must specify either the parameters in the first ForkBranch or the second, but not both.
So which of the following are the workflow function signatures?
All are optional. But then how do we enforce from the interface that unpaired_fq is None when the other ForkBranch is used
In the description of
Fork
andForkBranch
here,Fork
"shows a set of mutually-exclusive alternatives". How are the mutually exclusive parameters in eachForkBranch
written into the workflow function? Perhaps I confusing that fact that the interface elements are mutually exclusive, but the parameters are not?E.g. I have one
ForkBranch
has a single parameter (single end FASTQ), and anotherForkBranch
that has two parameters (one for each end of paired end FASTQs). So the user must specify either the parameters in the firstForkBranch
or the second, but not both.So which of the following are the workflow function signatures?
unpaired_fq
isNone
when the otherForkBranch
is usedunpaired_fq
when paired FASTQs are given?The text was updated successfully, but these errors were encountered: