`
`From:
`Sent:
`To:
`Subject:
`
`Clement Chu [Ciement.Chu@ucsf.edu]
`1/29/2008 11:56:22 PM
`'Christina Fan' [chfan@stanford.edu]
`RE: Fwd: 454 sequencing
`
`Hi christina,
`
`The reagent lead time tends to be about 3 weeks or so from Illumina. we
`don't currently stock kits in the CAT.
`I e-mailed Steve and told him the
`fastest way would probably be to ask Joe DeRisi if his lab has available
`reagents.
`I know he and Jonathan Weissman bought several kits a while back
`and I don't believe they have used them all yet. Perhaps ask Steve if he
`has contacted Joe yet, and if not go ahead and fire off an e-mail to Joe and
`ask.
`
`Best,
`clement
`
`----~original Message-----
`From: christina Fan [mailto:chfan@stanford.edu]
`sent: Tuesday, January 29, 2008 2:46 PM
`To: Clement.Chu@ucsf.edu
`subject: Re: Fwd: 454 sequencing
`
`Hi clement,
`I am a student in Steve's lab and I am the person working on the solexa
`sequencing project.
`I have already prepared a library. I would like to know how soon you
`would be able to receive the sequencing reagents for 36nt readlength. I
`heard that the reagents are back-ordered and wonder if your lab can
`somehow get them faster?
`Thanks for your help!
`christina
`
`Stephen Quake wrote:
`> clement
`>
`> Joe Derisi might have told you we are interested in running a few
`> samples on your solexa. How long is the queue to get something on the
`> machine and do you guys stock the sequencing reagents?
`>
`> best,
`>
`> steve
`>
`>
`> ---------- Forwarded message ----------
`> From: Joe DeRisi <joe@derisilab.ucsf.edu>
`> Date: Jan 9, 2008 9:31 PM
`> subject: Re: 454 sequencing
`>To: stephen Quake <quake@stanford.edu>
`>
`>
`> Hi Steve,
`> Great. The solexa guy here is clement chu. His email is
`> clement.Chu@ucsf.edu. I will let him know that you or someone from
`> your lab will contact him.
`>
`> our machine is currently configured for 8 lanes/flowcell, with 330
`> tiles per lane. For a good library, you should get 20-30k clusters per
`> tile, which, in an ideal world, would give you about 9 million reads
`> per lane, each 36nt. In reality, folks are getting 2-4 million, and
`>the 8th lane is usually reserved for a control. It is clear the read
`> length can be extended, if you are willing to tolerate some additional
`> errors.
`> Depending on your application, we can advise on library construction
`strategies.
`
`STANFORD EXHIBIT 2122
`SEQUENOM v. STANFORD
`CASE IPR2013-00390
`
`
`
`thanks for dropping by the other day - it was a big help.
`
`>
`>
`>
`> -joe
`>
`>
`> on Jan 9, 2008 3:06 PM, Stephen Quake <quake@stanford.edu> wrote:
`>
`>> joe,
`>>
`each
`>> the person in my lab to contact about a 454 run is rick white.
`>> full run is 400,000 reads of~ 250 bp each.
`the configuration is two
`>> large chambers, which are independently loaded (ie can be different
`>> samples).
`there are other configurations (up to 16 independent
`>>samples) and it is possible to do runs of shorter reads (100bp), which
`>> are slightly cheaper.
`>>
`>> best
`>>
`>> steve
`>>
`>>
`>> -----------------------
`>> Stephen Quake
`>> Professor of Bioengineering
`>> Stanford University
`>>
`>> PLEASE REPLY TO: quake@stanford.edu
`>>
`>>
`>
`>
`>
`>
`
`No virus found in this incoming message.
`Checked by AVG Free Edition.
`Version: 7.5.516 I Virus Database: 269.19.1511249 - Release Date: 112912008
`9:51 AM
`
`No virus found in this outgoing message.
`checked by AVG Free Edition.
`Version: 7.5.516 I Virus Database: 269.19.1511249 - Release Date: 112912008
`9:51AM
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
