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

Polyploidy #220

Open
goeckeritz opened this issue Jul 4, 2023 · 3 comments
Open

Polyploidy #220

goeckeritz opened this issue Jul 4, 2023 · 3 comments

Comments

@goeckeritz
Copy link

Hi Brentp,

I have a sample that's triploid. Any plans to allow smoove to be able to given a ploidy before calling?

@brentp
Copy link
Owner

brentp commented Jul 4, 2023

Hi, that probably won't be officially supported, but I think it might mostly work as-is. It will be less sensitive since only 1/3 of the reads will support an event (ideally) as opposed to 1/2.

@goeckeritz
Copy link
Author

Gotcha. Mostly I just think it would need to be able to make more than 2 calls per site. Is there a way to keep multi-mappers (reads containing the XA tag) when running smoove? Since I'm working with a polyploid, a lot of reads map to more than one region. I would just like to use the best mapping, even if it does map twice... any chance I can tell smoove not to drop XA reads?

@brentp
Copy link
Owner

brentp commented Jul 7, 2023

Hi, smoove doesn't look at the XA tag (and discards reads with mapping-quality of 0), only the SA tag, you'd have to do some pre-processing before sending to smoove for this to work.

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

2 participants