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

should we define "ligation_site_regex" if we choose enzyme "none"? #179

Open
shengqh opened this issue Feb 15, 2023 · 0 comments
Open

should we define "ligation_site_regex" if we choose enzyme "none"? #179

shengqh opened this issue Feb 15, 2023 · 0 comments

Comments

@shengqh
Copy link

shengqh commented Feb 15, 2023

Currently, we set enzyme "none" and didn't set ligation_site_regex in configuration json file since we used MNase. Based on the wdl code, the ligation_site would be determined as "XXXX" in hic-pipeline. However, in call-calculate_stats_on_library task, the stats_0_lib0.txt looks weird. Should we set ligation_site_regex to something else even the enzyme is none?

Read type: Paired End
Sequenced Read Pairs: 4144224
No chimera found: 187008411 (4512.51%)
One or both reads unmapped: 187008411 (4512.51%)
2 alignments: 72160909 (1741.24%)
2 alignments (A...B): 43056597 (1038.95%)
2 alignments (A1...A2B; A1B2...B1A2): 29104312 (702.29%)
3 or more alignments: 0 (0.00%)
Ligation Motif Present: N/A
Average insert size: 0.00
Total Unique: -68843076 (-95.40%, -1661.18%)
Total Duplicates: 141003985 (195.40%, 3402.42%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant