Age | Commit message (Collapse) | Author | Lines |
|
The place of the lecture was updated and the figure on Git branching
from the Maneage paper is also brought-in to show the capabilities.
|
|
Some very minor improvements were also made.
|
|
The long format is better for the actual talk.
|
|
Since this is an RDA-affiliated talk, its better for these slides to
be present.
|
|
I also found that in the short version hadn't properly accounted for
the new Git history images, and it has been corrected.
|
|
Until now, we would immeditely jump from the part on answering the
project's questions to Git branches. But this isn't too useful for
someone who doesn't know Git! So to start the Git branching
discussion, now we first show a small image of the workflow with a
"today" printed over it. Then another one with a "tomorrow". In the
next slide we abstract them to circles with hashes!
|
|
|
|
The short version of the slides is now ready. There is a '\longformat'
macro that will significantly increase the number of slides, but not
substantially (they are just the incremental things).
Some minor modifications were also made in the long version.
|
|
A first draft of the summarized slides was written for the talk in the
RDA Adoption week.
|
|
The main slides have become too long, so a shorter version is
necessary. With this commit, I am starting work on a short version.
|
|
This helps show the scale of the problem, and that its not only
astronomy papers that are complaining.
|
|
Since the webpage now already has `maneage' in the URL, the filename
also needed to be corrected.
|
|
The new `maneage.org' webpage is now displayed as the place to get the
most recent slides.
|
|
A name was finally selected for Maneage, so the slides also needed to
be updated.
|
|
|
|
I recently came across this quote and thought it fits nicely after the
discussion on software citation.
|
|
|
|
|
|
A few slides were added in the end to show the usage of the template
by various teams.
|
|
This helps connect better with the discussion on Git right after this
step.
|
|
The principles section was made more clear.
|
|
|
|
Until now, there wasn't any good transition onto the project, so the
principles have now been added.
|
|
While fixing the location, I made this mistake!
|
|
I will be preseinting it there tomorrow.
|
|
It was still 2019, so it has been updated to 2020.
|
|
This helps viewers feel a better connection with a standard paper.
|
|
Until now, we were only showing three lower level Makefiles and
configuration files, but since we don't have much Bash and Python
files, I just made it four and shrank the extra space.
|
|
Until now, I was using the arXiv version, but now that the full PDF
with the special journal format is out, I thought its better to use
that.
|
|
Until now the directories were light green (similar to the Make files
in the data lineage plot) which was confusing. Now that they have a
different color, they can be better distinguished as directories
vs. files.
|
|
The file architecture plot was a little crowded, so I am now first
showing the files discussed in previous plots, and then showing the
whole thing. Also, the 4 commands necessary to reproduce a project are
added.
|
|
I just made this for the paper and thought it would be good to have
here is well.
|
|
The journal name and volume was added, also because its a little long,
the main terms were made all-caps.
|
|
This quote (that a paper is just an advertisement of the scholarship,
not the scholarship itself) beautifully summarizes the problem!
|
|
The image that is used for replicability was intentionally chosen
because it has an astronomer sitting behind the secondary mirror
(showing the hard work that goes into data collection). But the image
has too many details and the person can be completely missed by the
viewers. So I just darkened the outer parts and added an arrow to let
the audience understand the point of the image.
|
|
|
|
The previous definition of hardware/software reproducibility was
mainly my own. But I recently came across the National Academies
report that gives a precise definition, so I used those terms and
cited the National Academies report.
|
|
A verification step was recently added to the pipeline, so it was
necessary to add it here is well.
|
|
Since some of the audience is not yet fully familiar with Git, I
thought its necessary to remind them in the slide showing Git
branching, that every commit contains all aspects of the project.
|
|
Following the convention of the Make-demo plot (where green files are
input and blue files are built), the first graph's gray boxes were
also changed to blue.
Some other minor corrections were made.
|
|
The set of slides that show how the built files relate to each other
through Makefiles was edited to first show the final target, and track
it all the way to the raw configuration files. This is in-line with
how I describe Make (that Make starts from the end).
This great suggestion was made by Idafen Santana PĂ©rez.
|
|
To help the audience, the legend of the graph (the description at the
bottom of the page) now also says that the built files are shown in
the Makefiles that produces them.
|
|
Until now, the connection between the first and second slides (after
the title) wasn't clear, so the title and fir paragraph of the
NoiseChisel+M51 slide was slightly modified to be more in-line with
the previous slide.
|
|
As Raul pointed out, to avoid confusion for a color-blind audience, or
when its printed in black-and-white, its best to not just base the
source-build distinction in the graph based on color.
With this commit, the source files have sharp edges and the built
files have round edges.
|
|
After showing the graph (and how everything is connected), it was
useful to remind the viewers on the benefits of Make to create this
structure.
|
|
It could be confusing, but we are only using LaTeX in the template so
far, so its better to just use LaTeX.
|
|
Some minor modifications were made in the graph showing the
organization of the analysis with Make. Also, a `tex/preamble.tex' was
defined to simplify the main source.
|
|
Until now, there was only one slide, with many boxes and arrows
connecting them. It was too complicated to understand for the viewers.
With this commit, it is broken up into separate slides, with each
box/arrow added on each slide as we progress. This helps clearly show
the logic behind all the connections.
The LaTeX source of this graph is in the paper that describes the
project, I will later bring that source into the slides too (and
remove all the extra figures).
|
|
Some arrows and text were added over the shown Makefile to better help
the eye when the viewers aren't familiar with Make.
|
|
Until now, as an example of uploading to Zenodo (besides uploading to
arXiv), I was mentioning `zenodo.1164774'. But this link doesn't have
any software to show. So I just updated the Zenodo link to the more
recent upload of `zenodo.3408481'.
|