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
I am trying to run a configuration where the input is a tuple of paths, some of which are optional. The pattern in this repository works for separate path inputs (or, so says the author), but extending it to my use case results in the error Not a valid path value: NO_FILE.
In this simple example demonstrating the issue, the input is a CSV file defining RNA-seq sample names, forward and reverse read fastqs, and a STAR genome index to align them to. The reverse read is optional.
My question to the community is how I can work around this issue.
"NO_FILE" is a value, not a path. If you pass file("NO_FILE"), the process will accept the channel as valid. Check the code below. It does one thing is the input is a file, and something else if it's a string that equals NO_FILE:
I am trying to run a configuration where the input is a tuple of paths, some of which are optional. The pattern in this repository works for separate path inputs (or, so says the author), but extending it to my use case results in the error
Not a valid path value: NO_FILE
.In this simple example demonstrating the issue, the input is a CSV file defining RNA-seq sample names, forward and reverse read fastqs, and a STAR genome index to align them to. The reverse read is optional.
My question to the community is how I can work around this issue.
Repository setup
Run
The text was updated successfully, but these errors were encountered: