Tweet
Last week, we ran our first Ti plate with the signal processing during the run (vs. doing only image collection then signal afterwards). The images were all collected properly and looked likel signal processing was fine until ~step 130 where it caused the SW to crash and kick out to the adminrig login screen with the red flashing light. I logged back in and took the images and did runAnalysisPipe and everything was fine. Any similar experience for others?
-
-
What version of the Newbler pipeline do you have? -
we're running 2.0.01.12. We've recently noticed too that the signal processing is not completing (i.e. no Wells tab/information) so we have to do the signal processing on the datarig (same SW but no problems).Comment
-
I was hoping someone else would reply with a more authoritative answer. However, I have a vague recollection from a local next gen meeting of someone mentioning this was a known issue with a recent Newbler update (hence my question about which version you were using).
I'd suggest you check with your Roche contact to see if this is the case.Comment
-
Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.07-01-2026, 11:43 AM
-
I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.
Here are nine questions we think about, in roughly the order they matter, before...
Comment