New study: "We find that scientists are overwhelmingly (95%) failing to publish their #code and that there has been no significant improvement over time, but we also find evidence that code sharing can considerably improve #citations, particularly when combined with #OpenAccess publication." https://www.researchsquare.com/article/rs-3222221/v1
I am super excited about this mini-conference on #reproducibility in #linguistics that I am organising this evening: Four of my M.A. students will be reporting on their attempts to reproduce the results of four published quantitative linguistics papers for which the data is available, but not the code!
Colleagues, they have a lot of things to report! So, if you're in the area (Cologne), do come along! There will be #ReproducibiliTea and Christmas biscuits! 🍵 🍪 #OpenScience
Beautiful slide deck on reproducible software environments by Ricardo Wurmus presented yesterday at a seminar of the German Research Network (DFN): https://elephly.net/downies/2023-dfn-slides.pdf
Starts with an acute quote of @khinsen explaining why #reproducibility matters.
An inspiring talk by @khinsen at The First Workshop on Reproducible Software Environments for Research and High-Performance Computing
"We shape our tools and then our tools shape us"
"Convivial tools empower their users. Radical monopolies make users dependent on a technological elite"
"We should come back to the goal of having scientific computing environments that normal scientists can manipulate without the help of expert programmers"
Incredible new episode from @brodriguesco on Nix and CI/CD. I agree with him on that it seems impossible that this kind of magic is not more widely known.
What better time than #OpenAccessWeek for Computo's first toot?
Hello, fediverse! Computo is a journal of the French Statistical Society (but don't worry, everything is in English), and our goal is to publish computational/algorithmic contributions in statistics and machine learning in a reproducible, open access way. Our papers are submitted as notebooks, and you can read them as html or pdf files.
I've released version 1.19.0-3 of my @nlnetlabs#unbound#docker image with updated build environments and unbound base to #alpinelinux 3.19.0. I have reduced two image layers by adding a separate build stage. The tags of the build environments got pinned for better #reproducibility, too.
SymfonyCon has been a fantastic experience, especially for the opportunity to meet so many incredible people for the first time. Our live discussions have already yielded tangible results. After PHPUnit, GrumPHP is now including a composer.lock for achieving total reproducibility.
This underscores the importance of the social aspect in our work, it's crucial and should never be underestimated.
From a Wash Post article on evidence humans were in N. America earlier than previously thought. I myself have a mixed-feelings middle-ground view on peer review, but I'm in a very different field.
"The peer-review process is designed to help validate scientific claims, but Lowery argues that in archaeology it often leads to a circle-the-wagon mentality, allowing scientists to wave away evidence that doesn’t support the dominant paradigm. He says he isn’t seeking formal publishing routes because “life’s too short,” comparing this aspect of academic science to “the dumbest game I’ve ever played.”"
April 4th we'll learn about how to package your code, based on chapter 11 of “Building reproducible analytical pipelines with R” by Bruno Rodrigues (https://raps-with-r.dev/packages.html)
One important lesson from the #xz situation is that we should not allow binary blobs to enter the build process because they can't be audited. (In the case of xz-utils, most of the malicious code was hidden in a binary test archive.)
Some time ago, I have banned all binaries from the revision control system used for our papers. That means no PDFs, PNGs, etc. In our case, it's not malicious code but #reproducibility; nevertheless, the challenges are quite similar. (1/3)
During meeting no.9, we'll learn how to streamline your analysis using {targets} package, based on chapter 13 of “Building reproducible analytical pipelines with R” by Bruno Rodrigues (https://raps-with-r.dev/targets.html).
Does anyone else maintain #changelog (s) for their #computer (s)?
I enter all configuration adjustments and #update (s) in a #markdown file for each machine.
This might seem like unnecessary extra work, but has paid off several times for the sake of traceability or #reproducibility in the past. 🤓 #musicproduction#linuxaudio