Tweet
Does anyone have any experience using the Google Compute Engine (or Amazon Web Services, or any other IAAS for that matter) to do RNA-Seq analysis with TopHat? The computers I have available are not at all suited to the task, and so I'd be interested to hear from anyone who has used one of these services.
-
-
GoogleCompute
Hi
I'm also interested in hearing of anyone doing analyses on GoogleCompute. It seems much more functional and certainly cheaper now.
Thanks -
I used Amazon Web Services EC2 to analyze some RNA-Seq data with Bowtie, Tophat and Cufflinks a few years ago.
I used a Ubuntu Linux ami, with 16 Gigabytes of ram, which doesn't seem like a lot now. I had files with 90 million 1X50 reads. I had started off with either a
4 Gb or 8 Gb machine, but got segmentation faults.
I just used a basic Linux ami, so I had to install all the bioinformatics software i wanted to use, like the Bowtie, Tophat, etc.Comment
-
Google Compute
Thanks for the information inscent.
Does anyone have information on recent use of the Google Compute?
Thank youComment
-
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...06-18-2026, 07:11 AM -
Data variability is still an issue in sequencing technologies despite the advances in reproducibility and accuracy of these platforms. But the problem does not originate in the sequencing itself, but in the previous steps, before the sample reaches the sequencer.
The first step is collection, followed by preservation and sample preparation for analysis. Most scientists overlook those steps, but not being careful might just be skewing the experiment’s results.
...06-02-2026, 10:05 AM
Comment