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

In most samples, INDELs are several times more than SNVs. #82

Open
monagai opened this issue Jan 2, 2024 · 2 comments
Open

In most samples, INDELs are several times more than SNVs. #82

monagai opened this issue Jan 2, 2024 · 2 comments

Comments

@monagai
Copy link

monagai commented Jan 2, 2024

I tried NanoSeq 3.5.1 for rats and mice data.
In most samples, INDELs are several times more than SNVs.
The number of SNVs seems proper. INDELs seems too much.

Is it reasonable status as a result of NanoSeq 3.5.1 or shoud I change some of my procedures?
May latest NanoSeq (INDEL caller was changed in 3.5.2) output much different results?
Any advice would be appreciated.

[conditions]

  • NanoSeq 3.5.1
  • tumor samples We used normal samples with certain treatments as tumor samples. They were dealt with "HpyCH4V"
  • Matched normal samples (control samples) : WGS, x30
  • I executed NanoSeq step by step. I didn't use Nextflow.
  • I made neat bams for normal filtered bams with randomreadinbundle.
  • I didn't specify -C (SNP.sorted.bed.gz) and -D (NOISE.sorted.bed.gz) for runNanoSeq.py dsa because there seems to be no such data for rats or mice.
  • I didn't execute VerifyBamId and efficiency_nanoseq.pl.
  • I followed all the instruction other than above.
@monagai monagai changed the title In most samples, INDELs are several times more than SNV. In most samples, INDELs are several times more than SNVs. Jan 2, 2024
@fa8sanger
Copy link
Collaborator

fa8sanger commented Jan 2, 2024 via email

@monagai
Copy link
Author

monagai commented Jan 3, 2024

Thank you for your advice!
Sorry for that my first comment for tumor was wrong. I revised it.
I used default parameters for all steps.
I will re-run using the latest version and check the data with your advice!

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