Skip to content
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

--rrbs and --emseq parameter and argument usage #389

Open
deep-buddingcoder opened this issue Mar 20, 2024 · 0 comments
Open

--rrbs and --emseq parameter and argument usage #389

deep-buddingcoder opened this issue Mar 20, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@deep-buddingcoder
Copy link

Description of feature

Hi,
I am not a avid user of github and not sure if this is the right place to ask question about a existing feature usage (but not related to new feature request). So pardon me, if I am wrong.

Experimentally, I have generated a human cancer cell line genomic DNA library (MspI digestion followed by NEB EMseq protocol) for CpG methylation analysis using NGS data.

I have couple of questions related to read trimming by Trim_galore!:

Q1. What is the source information for the selection of parameters and arguments for --emseq flag <--clip_r1 10 --clip_r2 10 --three_prime_clip_r1 10 --three_prime_clip_r2 10>? I am not able to match these with information presented in method section of couple of EMseq related papers published by NEB (PMID: 34140313 and PMID: 33468551).

Q2. If I use --rrbs and --emseq flag, both, which argument will be used by the program Trim_galore!:
<three_prime_clip_r1 2 --three_prime_clip_r2 2> for --rrbs flag
Or
<three_prime_clip_r1 10 --three_prime_clip_r2 10> for --emseq flag?

Let me know, if you need additional information from my end.
Thanks
Deep

@deep-buddingcoder deep-buddingcoder added the enhancement New feature or request label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant