-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow fromFilePairs to handle non globbing file patterns #946
Comments
Not sure why this is happening. I think the main reason is that it's not founding the any wildcard character. |
Same issue here.
Params file
Yields:
However, if I set the params to the following, it works:
Nextflow version: nextflow version 0.31.1.4886 |
This commit implements the support for non blobbing pattern for Channel.fromFilePairs method. This means that it is possible to specify a file path without any wildcard as matching pattern, eg. Channel.fromFilePairs('/some/path/file-name.txt') It returns the pair: ['file-name', ['/some/path/file-name.txt']] Bonus: when the specified pattern does not contain any wildcard character it defaults automatically to *single* pair, therefore it’s not necessary to specify `size: 1` to handle this scenario.
This commit implements the support for non globbing pattern for
It returns the pair:
Bonus: when the specified pattern does not contain any wildcard |
A common pattern to support having both single or paired-end reads onto the same channel definition is to do something like:
This works fine for when
params.reads
is a glob pattern, but if you provide only a single file with an absolute path like:--singleEnd --reads "/absolute/path/to/single/fastq.gz"
Nextflow throws an error:
An immediate solution would be to add a wildcard to the provided path, but would it be possible for the
fromFilePairs
channel to also acceptUnixPath
arguments?The text was updated successfully, but these errors were encountered: