-
Notifications
You must be signed in to change notification settings - Fork 79
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
Losing large % of reads due to lack of clone sequence #383
Comments
Yes, by default CDR3 is clonal sequence, so lack of clonal sequence means no CDR3 sequence were found for 46.61% of the reads. Please provide several (2-3 would be enough) reads in fastq format, for which you can map CDR3 but MiXCR fails to. For instance can you please show CDR3 for the read 1606 that you provided. P.S. Please post all sequences in the text form instead of a picture, so it would be possible to copy-paste them (e.g. to BLAST). |
Thank you for your help, I have put 4 fastq reads in to text format - the first is productive and maps a CDR3, the others align initially but are then lost at assembly. |
I just checked your reads with IgBlast -- they don't contain CDR3 (except first). |
Additionally, with MiXCR you can manually look how they align with |
Same here. |
Thank you for checking - I assume then the problem is with the data, and we will look in to trying to further optimise CDR3 coverage. |
Closing the issue, the problem seems to be in the data. P.S. Please read this, it is a very common source for nonproductive byproducts of sample preparation. |
Hello,
I am using MiXCR to analyse mouse TCRB illumina data, obtained from cDNA amplicons, and whilst 60-70% of the sequences initially align, whilst assembling I lose a further approximately 30% of the reads per sample. I can improve alignment to 90% by allowing for partial alignment, but still lose the majority of reads at the assembly step. The report says this is due to a lack of clone sequence - I presume a lack of CDR3 present? This is unexpected as our reads are from J-V so would expect high coverage of the CDR3 region. Is there any other reason that would account for this?
I have included a snapshot of both the alignment and assembly reports from a typical sample. Thanks in advance for any advice.
The text was updated successfully, but these errors were encountered: