Konrad Hinsen

I see basically two issues with HPC projects: 1. access to computational resources 2. effort required from reviewers to do a reproduction attempt In the submission I am handling, I...

I never had a doubt about that so far. The point of reviewing reproducibility is to check if someone else can get the same result, and thus potentially adapt the...

Thanks @benureau, that sounds like something worth trying. We'd ask authors submitting HPC-style work to provide a toy version of their computation for reviewing. Ideally, running the toy version would...

JOSS experience would definitely be of interest, but I have no idea who might be involved with this. In general, I'd expect JOSS to have less of an issue with...

Thanks @diehlpk! I think it is important to consider *why* one is verifying reproducibility. If it's a guard against mistake or fraud by the authors, the Zoom demonstration is helpful,...

A preprint related to this topic: [Reproducibility Practice in High Performance Computing: Community Survey Results](https://doi.org/10.22541/au.162569014.42317740/v1)

I agree with @nicolas-cellier-aka-nice. From a mathematical point of view, insisting on numbers being magnitudes was a big mistake in the Smalltalk class hierarchy.

A shorter code snippet with the same effect: ```Smalltalk |a | a := PMMatrix rows: #(#(-1 -1 1) #(-2 -1 2) #(-3 -2 3)). a decompose. ``` The SVD algorithm...

@AtharvaKhare Yes, that's one of the robust ones. And GSL is more generally a good source of inspiration, it's a very robust library. One ingredient to Golub-Reinsch is LU decomposition,...

Done: #116.