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

Monopogen treats multiple samples as single sample in germline SNV calling #72

Open
yu-tong-wang opened this issue Aug 14, 2024 · 3 comments

Comments

@yu-tong-wang
Copy link

yu-tong-wang commented Aug 14, 2024

I've encountered an issue where Monopogen appears to process multiple samples as a single sample during germline SNV calling, despite correctly handling them as separate samples in the preprocessing step, with multiple samples across different rows.

Key observations:
Preprocessing correctly identifies 4 samples.
Germline calling reports "1 samples in 4 input files".
All filtered BAM files have identical RG tags (SM:atac_possorted_bam).

I suspect the identical RG tags may cause this behavior. Is there a way to force Monopogen to treat each input file as a separate sample? Alternatively, should we modify the RG tags in our original BAM files? Any guidance on resolving this issue would be appreciated. Let me know if you need any additional information.

Update: the RG tags are unique in my original BAM files, and preprocessing module took 4 samples as separate samples, but also modified the RG info to be the same in the preprocessing step. It is important to modify the BamFilter function in germline.py to preserve the original Read Group information when creating the filtered BAM files. The problem most likely arose because my original BAM files are of the same name across different folders, which is very common.

bash atac_out/Script/runGermline_chr20.sh
[mpileup] 1 samples in 4 input files
(mpileup) Max depth is above 1M. Potential memory hog!
Lines total/split/realigned/skipped: 61434549/866633/85422/0
[2024-08-14 12:29:23,079] INFO Monopogen.py Success! See instructions above.

@jinzhuangdou
Copy link
Collaborator

Good suggestion. We will add different RG groups during the bamFilter step soon.

@SiyuanHuang1
Copy link

Same issue! Are there any updates? @jinzhuangdou

@SiyuanHuang1
Copy link

hello, Yutong, have you addressed this problem? @yu-tong-wang

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

3 participants