<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Research Tooling |</title><link>https://AaronScherf.github.io/tags/research-tooling/</link><atom:link href="https://AaronScherf.github.io/tags/research-tooling/index.xml" rel="self" type="application/rss+xml"/><description>Research Tooling</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Fri, 06 Nov 2026 00:00:00 +0000</lastBuildDate><image><url>https://AaronScherf.github.io/media/sharing.jpg</url><title>Research Tooling</title><link>https://AaronScherf.github.io/tags/research-tooling/</link></image><item><title>reprokit</title><link>https://AaronScherf.github.io/projects/reprokit/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><guid>https://AaronScherf.github.io/projects/reprokit/</guid><description>&lt;p&gt;A result is only worth as much as someone else&amp;rsquo;s ability to get it again. reprokit is the scaffolding I use to make that possible: a fixed way to describe sources, their reuse terms, and how they were checked, plus a command that tells a newcomer whether their setup works.&lt;/p&gt;
&lt;h2 id="the-problem"&gt;The problem&lt;/h2&gt;
&lt;p&gt;Research projects usually fail to reproduce for ordinary reasons. The data source was never recorded, or its terms of use were not checked. A step depended on a file that existed only on one laptop. The instructions assumed the reader already knew what a terminal was. And when something does break, the message is written for the person who wrote the code.&lt;/p&gt;
&lt;p&gt;I started building it while working on my
, which combines several sources with different formats and rules. That project needed proof that its outputs rebuild exactly. I wanted that proof to be reusable, so the next project starts with it instead of adding it at the end.&lt;/p&gt;
&lt;h2 id="what-i-built"&gt;What I built&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Source descriptors.&lt;/strong&gt; A structured record for each dataset: provider, variables and units, place and time coverage, how access works, reuse terms, and how far the data has been verified. A validator checks that the record is complete and consistent with the project&amp;rsquo;s settings, and that a claim like &amp;ldquo;verified on real data&amp;rdquo; has a matching verification note.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Evidence projects.&lt;/strong&gt; A second project kind for literature and desk research keeps a source manifest and checks citations against included, verified sources. &lt;code&gt;verify-sources&lt;/code&gt; checks DOI and OpenAlex identifiers online; &lt;code&gt;migrate-review&lt;/code&gt; converts an older literature review into a draft manifest for screening.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;reprokit validate&lt;/code&gt;.&lt;/strong&gt; One command that checks all of a project&amp;rsquo;s records and prints a plain explanation for anything missing. It can also warn when a source needs an account but the README does not say how to get the data by hand.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;reprokit quick-check&lt;/code&gt;.&lt;/strong&gt; A short self-test on made-up data. It reports PASS or FAIL in ordinary language, with the next command to type, and tells the reader that it does not test the real data.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Run summaries.&lt;/strong&gt; A project can write a readable file listing the rows produced, recorded time and memory per step, and checksums for its outputs, so two people can compare their results by comparing fingerprints.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A project template.&lt;/strong&gt; A repository generated with a README for non-developers (what a terminal is, what each file is for, what to do when the check fails), a protocol document, a test setup, automated checks on Linux and Windows, and a scan for accidentally committed secrets.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Small guards learned the hard way.&lt;/strong&gt; A loader for a project&amp;rsquo;s &lt;code&gt;.env&lt;/code&gt; file for account keys (values are never printed), and a Git setting that stops Windows from rewriting line endings in data files and silently changing their checksums.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="how-well-it-works-so-far"&gt;How well it works so far&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;It is in real use.&lt;/strong&gt; The compound shocks panel is built on it. Both of that project&amp;rsquo;s full rebuilds, run on 2026-11-06, finished with every checksum matching the earlier recorded run. Two more projects are in progress: Bangladesh Insurance Replication and Evidence Map; neither has reported research results here.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automated checks.&lt;/strong&gt; All 431 automated tests pass locally, and continuous integration is configured for Linux and Windows.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clearer first steps.&lt;/strong&gt; The generated README now explains that commands go in a terminal and names the files a newcomer will meet. Windows testing found the line-ending checksum bug above, which shipped as a fix in the next release.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Honest limits.&lt;/strong&gt; The compound shocks panel is the documented real-data use so far. The memory figure in its run summary counts only the main process, so it understates heavy steps. The checks confirm that a record is complete and consistent, not that its contents are true. Older projects need a manual update to receive new template text.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Releases so far are tagged v0.1.0 through v0.4.0 on GitHub.&lt;/p&gt;
&lt;h2 id="what-comes-next"&gt;What comes next&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Try it in the two in-progress projects&lt;/strong&gt; and see what breaks beyond the compound shocks panel.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Measure memory properly&lt;/strong&gt; and say plainly what the number covers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Make adoption easier&lt;/strong&gt; for an existing repository, including a clear note on how to generate a project from a local copy and how to repair line endings in older checkouts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migrate remaining records&lt;/strong&gt; to the current descriptor format so the stricter checks run everywhere.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Keep reviewing it with fresh eyes&lt;/strong&gt;, especially the first ten minutes for a reader who has never opened a terminal.&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>