Konrad Hinsen

@ctb Yes, your blog post is very appropriate. But it's not just time that is a problem. The code I am trying to use has been found OK by reviewers...

@Chris1221 The main problem I see with any CI-based approach is: what happens when the tests fail? Who does the work of analyzing what went wrong and how to fix...

An idea to reduce platform dependencies in the future: assign a third reviewer with a different scientific background, whose sole task is to re-run the computations from the instructions. This...

@oliviaguest It would be great to have research software engineers for doing this, but that's still a rare species. I'd say we take whoever is willing (and able) to do...

@ThomasA Do you think it's possible to provide a reasonable-length instruction page, with code templates if necessary/useful, to help potential authors use Travis CI for their ReScience submission? Even if...

I played with Markdeep a while ago. It's quite powerful, and easy to deploy as all there is to copy around is a single HTML file with embedded JavaScript and...

After a quick look at PythonTeX, I'd say it works much like a bunch of similar tools, such as [emacs/org-mode](https://www.jstatsoft.org/article/view/v046i03), [Lepton](http://www.math.univ-paris13.fr/~lithiao/ResearchLepton/Lepton.html). A single combined input contains text and code sections,...

Let me summarize the problem to verify that I understood it correctly: All relevant real-life data in computational finance is available to anyone willing to pay for it, but may...

@braverock Thanks for all the additional information! It's still not entirely clear to me how one could do effective replication work in your context. Apparently it is accepted that authors...

Zenodo's current file size limit is 50 GB, so that looks like a good option for hosting the data. Coming up with the right metadata will probably require some serious...