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

Parse2 clarification #193

Open
NMaziak opened this issue Nov 30, 2023 · 0 comments
Open

Parse2 clarification #193

NMaziak opened this issue Nov 30, 2023 · 0 comments

Comments

@NMaziak
Copy link

NMaziak commented Nov 30, 2023

Hello,

Thank you so much for creating such useful tools! I'm currently doing analysis on Micro-C data and had some questions on the parse2 options --report-orientation and --report-position.

Just for reference, we have paired-end reads (150 bp), so I thought it would be nice to try parse2. I'm just not sure if it would be more sensible to follow the defaults of parse2 (--report-orientation outer and --report-position junction), or if it makes more sense to follow the defaults used by parse -walks-policy all (--report-position outer). I would really appreciate it if I could understand better why the defaults vary between the two.

I have already tested both, and the maps looks very similar, as expected, but just wanted to gain some clarity and see if there are any caveats I am missing. For example, when is it sensible to use --report-position readand--report-orientation read`?

Thanks again,
Noura

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