aboutsummaryrefslogtreecommitdiff
path: root/README.md
AgeCommit message (Collapse)AuthorLines
2018-02-08Instructions to delete README.md before startingMohammad Akhlaghi-0/+5
`README.md' is for this pipeline, not the research project that is using it. Therefore it might be confused with the `README' that is devoted to the research project. So in the checklist, a point was added to delete this file before making the first new commit.
2018-02-08Basic titles now corrected after copyright in README.mdMohammad Akhlaghi-18/+16
The basic title, short description and author section of the checklist was moved immediately after copyright because it is more related to it. The description of Gnuastro is now before `README' because the user will confront Gnuastro in `README' and this will provide a good introduction on what to do with it.
2018-02-08Moved creation of a new Git repo to the end of the checklistMohammad Akhlaghi-23/+30
The creation of a new Git repo is now moved to the end of the checklist. It was not in place as the third step before. Now, the user makes all the standard changes and just before they start going into the details of their research, they define their new repository.
2018-02-08Minor edits in README.mdMohammad Akhlaghi-4/+7
The description of adding a title and authors was made slightly more clear.
2018-02-08Adding title and description also mentioned in README.mdMohammad Akhlaghi-1/+22
The first commit didn't have an explanation on correcting the title of the project in the final PDF or the top-level Makefile, so a pointer was added to the list. Also, some extra dependencies were removed from `README' and its paragraphs were scaled to the new width of 75 characters that is defined in `.dir-locals.el' (for Emacs settings, taken from Gnuastro).
2018-02-07First commit to the reproduction pipeline templateMohammad Akhlaghi-0/+400
Let's start working on this pipeline independently with this first commit. It is based on my previous experiences, but I had never made a skeleton of a pipeline before, it was always within a working analysis. But now that the pipeline has a separate repository for its self, we will be able to work on it and use it as a base for future work and modify it to make it even better. Hopefully in time (and with the help of others), it will grow and become much more robust and useful.