A Nature interview with Victoria Stodden on making research reproducible and sharing research code. Victoria Stodden is now one of the reproducibility editors of JASA. Read the article here.
Very interesting article here.
- Presentations at the Australian National Data Service (ANDS), 2007-now.
- Harvard Purdue Data Management Symposium, June 16-17, 2015.
EPFL is organizing a workshop on open research data on October 28, 2014. Interesting program and list of speakers, I hope some great conclusions and policies will follow!
While preparing my talk last week in Leuven, I wanted to update the slide with non-reproducible results making news headlines. Unfortunately, it’s always very easy to find recent material for that slide…
An interesting site which I recently discovered in that respect, is RetractionWeb: an overview of retracted works. And when reading some of the recent posts, I can fully see how the authors have a hard time keeping up with all related news. The authors also describe why they started this blog. Great site! Sad to see so much news on it.
It has been silent here for a while again, which by no means implies that people promoting reproducible research were sitting still.
ResearchCompendia.org is a site set up by Victoria Stodden and her colleagues at Columbia university. It invites everyone to upload their research compendia (paper with source code) onto the site. It has a clean interface, and the source code for the site is maintained at GitHub. Currently the site already contains more than 200 compendia, maybe soon also yours?
Another nice article on reproducible research by Victoria Stodden in IMS Bulletin:
V. Stodden, Resolving Irreproducibility in Empirical and Computational Research, IMS Bulletin, Nov 2013.
I just read a very well-written article on reproducible research, giving 10 simple but important rules for making your results (more) reproducible:
It’s probably the way things go, but still I feel sad about it. One of the reproducible research tools linked on our site does not seem to exist anymore: ResearchAssistant (by Daniel Ramage). Typical story: PhD student graduates, and moves on to another position (I did find a “now at Google” when searching what happened), and the web pages with useful links and tools disappear. RIP.
(If you read this blog in the next month, and you know that ResearchAssistant is still alive, let me know. I promise to keep the link alive for another month.)
Given the fact that you are reading this blog, I am assuming you are into sharing your code and data. However, what is not so clear to me, is where we should be sharing these data (assuming data includes code, which people often seem to forget).
- On our own personal web page? Seems like an excellent place to me, but too many of those personal sites are extremely short-lived. I notice this every time I update links.
- On our institution’s publication pages? That would probably be my preferred choice at this moment. Often with a longer life-span than personal webpages, and still “close enough to yourself”. Some issues arise with people working at a company (but then, are you often allowed to share code/data in such a situation?), or with people moving from one institution to another, but those all seem fairly limited compared to some of the alternatives.
- On the publisher’s web pages? That would make it consistent with the related publication. However, I’m not sure I want to transfer ownership of my code and data to the publisher as well.
- On “social media” such as ResearchGate, or Academia.edu? At first I was enthusiast about these, but I start having my doubts. Who is behind these sites? How are they counting on making money, based on my data? Now that some of those start spamming me with e-mail, and asking me whether I have questions for the authors of a paper I downloaded, I become even more skeptical.
- Any other suggestions?
Maybe I am too critical about this, or too old-fashioned. Or just too commercially oriented, and not open enough to share with everyone potentially interested in my work. Who will tell?