Please create an account to participate in the Slashdot moderation system


Forgot your password?
Compare cell phone plans using Wirefly's innovative plan comparison tool ×

Submission + - 20% of Scientific Papers On Genes Contain Conversion Errors Caused by Excel (

An anonymous reader writes: A new report from scientists Mark Ziemann, Yotam Eren, and Assam El-Osta says that 20% of scientific papers on genes contain gene name conversion errors caused by Excel. In the scientific article, titled “Gene name errors are widespread in the scientific literature,” article’s abstract section, the scientists explain: “The spreadsheet software Microsoft Excel, when used with default settings, is known to convert gene names to dates and floating-point numbers. A programmatic scan of leading genomics journals reveals that approximately one-fifth of papers with supplementary Excel gene lists contain erroneous gene name conversions.” It’s easy to see why Excel might have problems with certain gene names when you see the “gene symbols” that the scientists use as examples: “For example, gene symbols such as SEPT2 (Septin 2) and MARCH1 [Membrane-Associated Ring Finger (C3HC4) 1, E3 Ubiquitin Protein Ligase] are converted by default to ‘2-Sep’ and ‘1-Mar’, respectively. Furthermore, RIKEN identifiers were described to be automatically converted to floating point numbers (i.e. from accession ‘2310009E13’ to ‘2.31E+13’). Since that report, we have uncovered further instances where gene symbols were converted to dates in supplementary data of recently published papers (e.g. ‘SEPT2’ converted to ‘2006/09/02’). This suggests that gene name errors continue to be a problem in supplementary files accompanying articles. Inadvertent gene symbol conversion is problematic because these supplementary files are an important resource in the genomics community that are frequently reused. Our aim here is to raise awareness of the problem.”

Comment Re:All the data means all the data (Score 2) 184

Years of attacks from various security services and law enforcement agencies has made it hard for wikileaks to process these leaks. Attacks on sources of funding, payment processing, communications, anyone who with for/with them...

So now they have to pick between not releasing and dumping everything unedited. There is no good option.

Comment Re:Domain modelling [Re:Shying away from OOP(s)] (Score 1) 670

you don't know what the fuck OO is in the first place

Nobody agrees on the definition or formal characteristics.

And nobody agrees on who gets to decide the definition. There is no standards body who defines what OO is. YOU are not it.

Every tool has a proper place and use, and making relative value judgements between them is something fuckwits do when they only know how to use one thing.

I've mentioned multiple times I do choose to use it to some degree. I've found practical utility for it under certain circumstances. So what is this "one thing"?

how you've rooted out this terrible OO hoax perpetrated on the industry

Well, okay, "hoax" is possibly a little harsh, but I do believe that OO-domain-modeling was thrust on the industry by hucksters wanting to sell books and consulting services; and millions, if not billions were spent chasing this false dream.

The primary focus of these hucksters was in domain modeling. Therefore, other than a small blurb, I didn't used to make much of a distinction between "OO" and "OO domain modelling".

A bigger distinction is made now in the industry because practical experience and failures taught many that domain modeling is NOT where OO shines. I know you disagree that domain modeling was the main stated selling point of OO, but we'll just have to let that disagreement stand (unless somebody can present reliable surveys of beliefs).

Why does it matter to you anyhow? It's water under the bridge. I'm not understanding your complaint. It appears you want to make this all about me instead of OO. That's why you appear to be a troll. Non-trolls talk about the subject at hand. Say something about OO and than back your claim with evidence: that's not asking too much.

You seem to agree there that scientifically comparing the utility of software engineering paradigms/techniques is either a gray art or requires resources not yet committed by anybody. Good, that part is mostly settled then.

Comment Re:Alarming Battery Costs (Score 1, Interesting) 105

The battery is good for 900,000 miles to 80% capacity remaining. Accelerated testing confirms it, as do drivers with 300k miles or more on their cars. It's basically 2x a typical petrol engine, similar to a diesel.

When it's end of life you can sell it for recycling into other applications like home UPS/solar storage.

Comment Re:This is the same guy (Score 4, Insightful) 280

Actually it is. It is short hand for:

* What have you done that is even 1/10 as meaningful as what Woz has accomplished?
* Where are your devices that helped change the world?
* Where is your computer langue?
* Where were you when they were _creating_ the personal computer movement?
* After starting a fortune 50 company why _isn't_ Woz allowed to "retire"?
* Why are you so insecure that you must put down others?
* Why do you criticize others when you're too afraid to even use a real name?

Only a troll criticizes a visionary and great engineer due to their own insecurity.

Submission + - Animation Explains Multi-GPU Load-Balancing Tasks and Memory

Scott Michaud writes: While DirectX 12, Mantle, and Vulkan allow developers to list all GPUs in a system, and communicate with them individually, Crossfire and SLI accomplished that task in DirectX 11 and OpenGL. Apart from the very early implementations, which interleaved monitor scanlines (or otherwise cut up a single frame) between devices, these systems used the Alternate Frame Rendering (AFR) algorithm to divide work. Because neighbouring frames require roughly the same amount of work, and old APIs submit work through restrictive interfaces, memory was mirrored across GPUs and, except for AMD's Hybrid Crossfire and LucidLogix HYDRA Engine, GPUs needed to be roughly identical. The new APIs open the dialogue between software and hardware, but the load balancing algorithms, themselves, have their own limitations.

Comment Hyper-linking was invented in the 60's .... (Score 1) 68

Not sure why Tim gets credit when hyper-linking was demo'd back in 1968 ...

The Mother of All Demos, presented by Douglas Engelbart (1968)

Alan Kay points out the same thing @17:03

Alan Kay - Normal Considered Harmful

Slashdot Top Deals

"You need tender loving care once a week - so that I can slap you into shape." - Ellyn Mustard