-
Notifications
You must be signed in to change notification settings - Fork 5
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
Made the hic
param pattern more flexible
#131
Conversation
|
For visibility, @SarahBailey1998, @ignacio3437 |
script "./hicparam.nf" | ||
function "checkHiCParam" | ||
|
||
test("Dummy_hic.R{1,2}.fq.gz") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SarahBailey1998, @ignacio3437
The permissible patterns are tested here. Are we missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would "dummy_hic_{1,2).merged.fastq.gz be allowed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you mean: dummy_hic_{1,2}.merged.fastq.gz
and not dummy_hic_{1,2).merged.fastq.gz
, then yes.
The permissible pattern is ^\S+\{1,2\}[\w\.]*\.f(ast)?q\.gz$
\S+ will cover the dummy_hic_ part
We can test it here: https://regex101.com
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah that's what I mean, I made a typo sorry! Awesome
PR checklist
hic
param pattern more flexiblenf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).