diff options
Diffstat (limited to 'README-hacking.md')
| -rw-r--r-- | README-hacking.md | 28 |
1 files changed, 17 insertions, 11 deletions
diff --git a/README-hacking.md b/README-hacking.md index a598373..d944fb0 100644 --- a/README-hacking.md +++ b/README-hacking.md @@ -180,13 +180,22 @@ evolving rapidly, so some details will differ between the different versions. The more recent papers will tend to be the most useful as good working examples. - - Roukema ([2020](https://arxiv.org/abs/2007.11779), + - Peper & Roukema ([2020](https://arxiv.org/abs/2010.03742), + arXiv:2010.03742): The live version of the controlled source is [at + Codeberg](https://codeberg.org/boud/elaphrocentre); the main input + dataset, a software snapshot, the software tarballs, the project + outputs and editing history are available at + [zenodo.4062461](https://zenodo.org/record/4062461); and the + archived git history is available at + [swh:1:dir:c4770e81288f340083dd8aa9fe017103c4eaf476](https://archive.softwareheritage.org/swh:1:dir:c4770e81288f340083dd8aa9fe017103c4eaf476). + + - Roukema ([2020](https://arxiv.org/abs/2007.11779), arXiv:2007.11779): The live version of the controlled source is [at Codeberg](https://codeberg.org/boud/subpoisson); the main input dataset, a software snapshot, the software tarballs, the project outputs and editing history are available at [zenodo.3951152](https://zenodo.org/record/3951152); and the - archived git history is also available at + archived git history is available at [swh:1:dir:fcc9d6b111e319e51af88502fe6b233dc78d5166](https://archive.softwareheritage.org/swh:1:dir:fcc9d6b111e319e51af88502fe6b233dc78d5166). - Akhlaghi et al. ([2020](https://arxiv.org/abs/2006.03018), @@ -240,10 +249,9 @@ working examples. Citation -------- -A paper to fully describe Maneage has been submitted. Until then, if you -used it in your work, please cite the paper that implemented its first -version: Akhlaghi & Ichikawa -([2015](http://adsabs.harvard.edu/abs/2015ApJS..220....1A), ApJS, 220, 1). +If you use Maneage in your project please cite Akhlaghi et +al. ([2020](https://arxiv.org/abs/2006.03018), arXiv:2006.03018). It has +been submitted and is under peer review. Also, when your paper is published, don't forget to add a notice in your own paper (in coordination with the publishing editor) that the paper is @@ -1254,11 +1262,9 @@ for the benefit of others. - *Configuration files*: If your research uses special programs as part of the processing, put all their configuration files in a devoted directory (with the program's name) within - `reproduce/software/config`. Similar to the - `reproduce/software/config/gnuastro` directory (which is put in - Maneage as a demo in case you use GNU Astronomy Utilities). It is - much cleaner and readable (thus less buggy) to avoid mixing the - configuration files, even if there is no technical necessity. + `reproduce/software/config`. It is much cleaner and readable (thus + less buggy) to avoid mixing the configuration files, even if there is + no technical necessity. - **Contents**: It is good practice to follow the following |