![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Low Diversity Libraries on NextSeq | nangel | Illumina/Solexa | 5 | 11-23-2015 02:10 PM |
Questions about whole-exome sequencing on NextSeq 500 | newtoseq | Illumina/Solexa | 3 | 11-02-2014 07:26 PM |
Agilent SureSelect exome enrichment bed file | yl01 | Bioinformatics | 8 | 12-15-2013 02:45 AM |
low sureselect on-target reads | hawaii454-0 | Sample Prep / Library Generation | 3 | 04-10-2013 09:18 AM |
SureSelect exome sequencing on SOLiD | epistatic | SOLiD | 2 | 04-29-2011 03:52 PM |
![]() |
|
Thread Tools |
![]() |
#1 |
Junior Member
Location: Madrid Join Date: Jul 2015
Posts: 9
|
![]()
Hi everybody,
We are doing SureSelect all exome v6 on a High Output 300 cycle NextSeq Kit. The libraries were quantitated with QIASeq qPCR (works very weel with other libraries), and although we load the recomended concentration we always got low clustering (around 98 K/mm2). We also try increassing the loading concentration with the same result. Anyone has the same issue? Any suggestions?. Thanks for your help |
![]() |
![]() |
![]() |
#2 |
Member
Location: Illinois Join Date: Oct 2014
Posts: 37
|
![]()
Could you please attach Bioanalyzer traces of your pre and post capture libraries? That information may help troubleshoot the issue.
|
![]() |
![]() |
![]() |
#3 |
Junior Member
Location: Madrid Join Date: Jul 2015
Posts: 9
|
![]()
We use QIAxcell instead of bioanalyzer. I am attaching the files.
|
![]() |
![]() |
![]() |
#4 |
Member
Location: Illinois Join Date: Oct 2014
Posts: 37
|
![]()
Thanks for attaching these. The only pertinent comment I have about the traces is that the average library size is a bit larger than we commonly see for captures. Was genomic DNA used as the starting material?
The NextSeq can typically handle fragments of that size with no problem, however. You simply see a significant bias towards smaller fragments being able to cluster effectively. One thing we have seen with Agilent capture libraries is the presence of a poly-G tract at the beginning of the read that can really screw up the NextSeq's base calling software. How does the base diversity look on the run? Are you seeing high "G" calls anywhere? |
![]() |
![]() |
![]() |
Thread Tools | |
|
|