Replies: 1 comment 1 reply
-
Hi @tamasgal , From what I can gather with this snippet, I think you should look into the combine operator which would help you create tuples. You could further use Probably, the actual files might follow a different naming convention or you might decide to change the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey, I have the following situation: I need to preprocess a few files before the actual analysis can happen and I have two sets of them:
There are just a few calibration files and each data files requires the right one. To pick the correct calibration, one needs to inspect the file.
This is how my workflow looks like for now, to demonstrate the situation, given the following files:
A.detx
,B.detx
,C.detx
1.evt.gz
,2.evt.gz
,3.evt.gz
,4.evt.gz
,5.evt.gz
,6.evt.gz
,7.evt.gz
I need some mechanism/process (
combined
in the above workflow) which takes the preprocesseddata
anddetectors
and then creates a list of tuples out of them, like:[(B.detx, 1.evt.gz), (A.detx, 2.evt.gz), (A.detx, 3.evt.gz), (A.detx, 4.evt.gz), (A.detx, 5.evt.gz), (A.detx, 6.evt.gz), (C.detx, 7.evt.gz)]
. In thiscombined
process, I need access to all thedata
andcalibration
files to be able to emit a corresponding pair. As written above, to pick the correct calibration, I need to do some quick checks on thedata
files...I checked the operators but could not figure out which one could fit. I also checked the patterns in https://github.com/nextflow-io/patterns/tree/master/docs but they seem to be a bit outdated and I anyways need DSL2.
Beta Was this translation helpful? Give feedback.
All reactions