Update: as pointed out in the comments, the amusing error in this article has been “corrected” (or at least, “edited away”). Thanks for your interest.
Update: I note that this article is now “Highly Accessed” ;)
An integrative analysis of DNA methylation and RNA-Seq data for human heart, kidney and liver
BMC Systems Biology 2011, 5(Suppl 3):S4
(insert statistical method here). No, really.
With thanks to Simon J Greenhill and Dave Winter.
A couple of years ago, I noted that some journals were not making the process of commenting on articles especially easy. My latest experience suggests that little has changed.
Read the rest…
Bioinformaticians (and anyone else who programs) love effective automation of mundane tasks. So it may amuse you to learn that I used to update PMRetract, my PubMed retraction notice monitoring application, by manually running the following steps in order:
- Run query at PubMed website with term “Retraction of Publication[Publication Type]”
- Send results to XML file
- Run script to update database with retraction and total publication counts for years 1977 – present
- Run script to update database with retraction notices
- Run script to update database with retraction timeline
- Commit changes to git
- Push changes to Github
- Dump local database to file
- Restore remote database from file
- Restart Heroku application
I’ve been meaning to wrap all of that up in a Rakefile for some time. Finally, I have. Along the way, I learned something about using efetch from BioRuby and re-read one of my all-time favourite tutorials, on how to write rake tasks. So now, when I receive an update via RSS, updating should be as simple as:
In other news: it’s been quiet here, hasn’t it? I recently returned from 4 weeks overseas, packed up my office and moved to a new building. Hope to get back to semi-regular posts before too long.