Hi everyone
Thanks for the comments. I will indeed just be giving a brief overview of GRChombo, but I’d be very happy to provoke a discussion of what people feel are the key requirements/recommendations for public codes. GRChombo is still relatively new and certainly has a lot to learn from an established code like the ET.
Looking forward to the discussion!
Katy
-------------------------------------------- Dr. Katy Clough Postdoctoral Research Associate Institut für Astrophysik Georg-August-Universität Göttingen, Germany --------------------------------------------
On 16 Apr 2018, at 22:37, Erik Schnetter <schnetter@gmail.commailto:schnetter@gmail.com> wrote:
Boud
On a theoretical level you are correct.
On a practical level, I find the most important things for reproducible computational science are: - use a version control system - produce all simulations for a paper with one particular, documented version of the code - store all parameter/input files in the paper repository
And most of all: - have a working tutorial with simple examples that helps people get started with the code
I'm not expecting a tutorial from Katy (I'm expecting an overview), but if you want to build a community, you might want to think about offering such a tutorial, e.g. via videoconferencing, once you have a few interested people.
-erik
On Mon, Apr 16, 2018 at 4:46 PM, Boud Roukema <boud@astro.uni.torun.plmailto:boud@astro.uni.torun.pl> wrote: hi Helvi, all,
On Mon, 16 Apr 2018, helvi witek wrote:
Katy Clough kindly agreed to give us an introduction to GRChombo ( http://www.grchombo.org/), their new, publicly available numerical relativity code.
GRChombo is *not* just publicly available; it is free software in the formal sense of "free software" (i.e. free-licensed software - https://en.wikipedia.org/wiki/free_software), under the BSD 3-clause licence:
https://github.com/GRChombo/GRChombo/blob/master/LICENSE
For a code to be publicly available is not very useful in itself, since that includes non-free codes, for which it is illegal to modify the code, redistribute it, and/or redistribute modified versions.
What is critical for a scientific community like ours is to be able to correct bugs in the code, add features, have other people correct bugs in turn, and freely redistribute corrected versions, while giving proper credit to who did what and including proper revision/history control. For software to be publicly available is insufficient to support this community process; in contrast, being free-licensed software - such as GRChombo - guarantees the right to free development by the community.
Cheers Boud _______________________________________________ Cosmoparticle-wg mailing list Cosmoparticle-wg@einsteintoolkit.orgmailto:Cosmoparticle-wg@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/cosmoparticle-wg
-- Erik Schnetter <schnetter@gmail.commailto:schnetter@gmail.com> http://www.perimeterinstitute.ca/personal/eschnetter/ _______________________________________________ Cosmoparticle-wg mailing list Cosmoparticle-wg@einsteintoolkit.orgmailto:Cosmoparticle-wg@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/cosmoparticle-wg