Welcome to the MIT BIOMICRO CENTER
BioMicro Center News
JUNE 17, 2013
First, we have a number of BioMicroCenter:People staffing changes to tell you about. The end of June will see three members of the core moving on. Ryan Abo, one of our informatics scientists, will be heading to the Dana Farber and Paraj Patel and Pierrick Millet will be returning to Northeastern. Our new co-op students, Ashley Machado and Alexander Soltoff will be starting July 1st. We are currently undertaking a job search to look for Ryan’s replacement. If you have any concerns about the personnel changes, please feel free to contact me.
In a piece of good news, the root cause of the critical failures we have had with our MiSeq for the last month plus with homopolymer samples appear to have been identified and should be fixed today. A recent software upgrade that was supposed to improve the handling of homopolymeric samples apparently failed to install properly, resulting in a mix of pipeline versions that was unable to handle the sequences at all. I do want to thank everyone for their patience as we have struggled with this problem and assure everyone we will move through our backlog on the MiSeq as fast as we possibly can. I also want to thank the techs in the lab, especially Scott Morin, who have been working weekends to try to get as many samples through the MiSeq as possible.
Finally, with the end of the fiscal year, our annual price adjustments are due to take effect on July 1st. You can find a complete list of the new prices here . The largest change is a reduction in cost for HiSeq sequencing, especially for longer reads. This is associated with a significant decrease in the amount of time we will be holding data on our servers and with the recent switch from fastq + SAM file formats to retaining only BAM files. (see January 2013 notes).
APRIL 20, 2013
We have noticed a number of technical issues with some Illumina runs. We want to share with you to make sure you are aware of some changes and newly identified technical issues with the platform and what we are doing to correct them where we can. All of these changes are from the Illumina side and none were especially well documented (some not at all). These issues are unlikely to be limited to the BMC, so samples from elsewhere on campus or around the country may also have these issues. Please read this as it may have some impact on your analyses.
Just to begin, all of these changes are subtle and not obvious in most cases directly from the sequencers. It was the rare cases that had dramatic effects that caused us to notice them. If you decide you need to have samples rerun, we will work with you to try to get Illumina to replace the reagents and to get the samples rerun. Unfortunately, there is no way we can possibly do bulk reruns of several months’ worth of studies.
The most concerning issue is a dropout of GC rich regions in clustering. This has been an on-again off-again issue with Illumina that we have addressed over a year ago by improvements in amplification cycling conditions and enzyme selection. Some time, several months ago (we do not have a precise window), Illumina appears to have changed the chemistry of one of their clustering components and that caused a major change in performance on GC rich areas. This can be seen as an absence of reads from very GC rich areas but, because these areas are rare in most genomes, they cannot be seen on the flowcell wide metrics. This issue is found on current HiSeq and MiSeqV2 kits but not on MiSeqV1 kits nor, we suspect, on the GAII. We have been able to address this problem by adding a brief boiling step during NaOH denaturation of the samples and have implemented this as SOP starting about two weeks ago. This drop out of regions can cause significant issues for several studies – most notably ChIP analyses – when you are comparing data from different chemistries.
A second concern is one that has been reported in the community but we have not identified on our machines – yet – where samples from a run are being observed in the following run as minor contaminants. This issue is limited to the MiSeq and HiSeq2500 (we do not have the latter) where the tubes that add sample to the flowcell are not changed. This contamination is reported to be <1% and so would not show up on our quality metrics. However, if your MiSeq analyses are being based on finding a few reads in a large pool of discarded data or you are doing a number of sequential runs, you may wish to validate your data more carefully using an alternative technique such as qPCR or sanger sequencing. There is currently no technical fix to this problem.
A third issue has been around for a while though we had not appreciated the implications. Illumina’s newer versions of basecalling software have become less capable of handling uniform sequence (all A’s for example). In earlier versions, only 5 basepairs of variability were needed and intensities could be determined by the control lane we run on all HiSeq flowcells. Now, it appears that nt 1-25 all must have representation of all 4 bases at all positions, even with a control lane. This has always been an issue on the MISeq and we have solved it by spiking in 30%PhiX in the lane (as opposed to our normal 0.1% spike in). Similar solutions can be used on the HiSeq. Given this change, we are re-evaluating whether there is value in using the 8th lane as a control. The latest version of MiSeq software (only a couple days old) supposedly allows us to lower the fraction to 5%, but how successful this is remains to be seen. Base rearrangement with the GAII allows the GAII to avoid this issue.
Finally, it appears that custom priming on the MiSeq is not the same as custom priming on the HiSeq and GAII. It can still be done, but the Tm requirement is much higher. Primers that work on the HiSeq may fail on the MiSeq. As long as your Tm matches or exceeds the Tm used for Illumina primers, the MiSeq should work, but the MiSeq’s different chemistry (formamide instead of heat denaturation) is less forgiving.
In summary, we have a number of technical challenges that may (or may not) effect you and we want to make sure you have all the information we can give you. I want to thank the researchers and labs that have been very patient as we have struggled running their samples which led us to identify these problems. If you believe these issues have effected your data, please do not hesitate to contact me and we can discuss how to move forward.
MARCH 11, 2013
Quick update from BioMicro:
JANUARY 9, 2013
Happy new years to everyone. A couple new things happening in BioMicro that we want to make everyone aware of.
ABOUT THE BIOMICRO CENTER
The MIT BioMicro Center was founded in 2000 as the core bio-fabrication and microarray processing facility at MIT. The Center is a joint endeavor between the Department of Biology, the Koch Institute for Integrative Cancer Research, the Department of Biological Engineering and the MIT Center for Environmental Health Sciences. The BioMicro Center offers a wide range of genomic services to researchers at MIT. The majority of services rendered pertain to massively parallel sequencing using the Illumina Genome Analyzer (both library preparation and sequencing). Commercial array processing and include both the Affymetrix Gene Chip and Agilent DNA array platforms continues to be a significant portion of our portfolio. Real-time PCR and Agilent BioAnalyzer services are available in the facility both as services available to researchers, as well as for quality control of microarray and sequencing samples. In addition, the Center has a presence in high-throughput screening with robotics and plate reading as well as informatics and computational support. The BioMicro Center serves the Koch Institute as the MicroArray Technologies Core and as part of the Bioinformatics and Computing Core and the MIT Center for Environmental Health Sciences as part of the Genomics and Imaging Core
Experimental and analytical work done in the BioMicro Center is funded by the NIH and must be made available through the NIH's open access policy. All Koch Institute and CEHS labs must acknowledge their core grants for work done in the core with the following language.
Error fetching PMID 23662897:
Error fetching PMID 23657361:
Error fetching PMID 23352431:
Error fetching PMID 23630078:
Error fetching PMID 23523371:
Error fetching PMID 22981692:
Error fetching PMID 22847430:
Error fetching PMID 22102570:
Error fetching PMID 21892155:
Error fetching PMID 20720539:
Error fetching PMID 20581084:
Error fetching PMID 19531355:
RECENT CHANGES TO THE WEBSITE