-
Notifications
You must be signed in to change notification settings - Fork 144
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
Add CX report support from bismark_methylation_extractor #372
Comments
We can certainly look into it 👍🏻 Note that it is possible to tweak the arguments supplied to tools yourself, without modifying pipeline code - through using Nextflow configs. This can let you get moving right away, without waiting for a new parameter to be added to the pipeline (which is better, but takes a while). See the docs on the topic here. Feel free to jump into the |
Hello, Thank you for your quick reply. It's indeed a good way of doing things, although having the option directly in the pipeline would be a plus :) But it'll do just fine in the meantime. Thank you very much. |
I was a little surprised by this result at first, primarily since we have used the older version of |
Should be an easy modification. The arguments for this step are set in the pipeline here: Lines 207 to 217 in 54f823e
In fact, |
eg. if we always want this flag when running the pipeline with - params.comprehensive ? ' --comprehensive --merge_non_CpG' : '',
+ params.comprehensive ? ' --comprehensive --merge_non_CpG --CX' : '', |
Thanks @ewels I think doing this within a custom config that overrides the above logic to do what I need should work. I'm wondering whether this is something that could be documented as an example in the nf-core methylseq docs, modifying or tweaking this specific step seems to come up regularly enough. |
A small update on this. I did manage to get this running by simply using a custom conf with the following in the process block:
However, I'm leaving this here in case others have the same problem I had. The
It's not consistent, but removing that extra parameter fixed the issue. It's not clear why this occurred yet so will need some debugging. Note this had several EM-Seq controls included, so maybe it had an issue with those. |
Description of feature
Hello,
Would it be possible for you to add the
--CX
option from thebismark_methylation_extractor
script as you were able to add the--comprehensive option
?Regards.
The text was updated successfully, but these errors were encountered: