Tweet
What Operating System Do You Use For Analysis?
I'm interested to know what operating systems people here use. This will help me and others decided what platforms to focus testing on.
-
82Linux 32-bit6.10%5Linux 64-bit59.76%49Unix variant0.00%0Windows XP3.66%3Windows 7 (32-bit)1.22%1Windows 7 (64-bit)2.44%2Mac OS X (Intel)19.51%16Mac OS X (PowerPC)3.66%3Cloud based1.22%1Other (Please mention)2.44%2 -
I'd also be interested to know what distro the Linux users use. This may help as well. Perhaps maintainers or others could also add why they use this particular distro?
I run my analysis on an Ubuntu server, Jaunty. I just use the available server, so I can't say anything useful about why it runs Jaunty. -
The workstation I use currently runs Slackware64.-13.0, but it will be upgraded to 13.1 sometime soon. I chose Slackware due to my own familiarity with it, plus support is readily available. I've had people in the Slackware community help me get things working, even if they didn't know much of the tools themselves.Comment
-
Wow, I'm surprised there are so many Macs... good thing the new SpliceMap supports OS X. I'll make a post about that later.Comment
-
Ubuntu 10.04 (Lucid) 64bitComment
-
I think most of the people that uses mac, they use them for the initial coding and prototyping, idea testing and then they through the real deal to a HPC cluster, typically linux based.Originally posted by john_mu View Post-drdComment
-
Or work on smaller organisms like viruses or bacteria where you don't need so much RAM.Originally posted by drio View PostComment
-
Fedora7-64bit, it's a little out of time!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