<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.anunna.wur.nl/index.php?action=history&amp;feed=atom&amp;title=Reproducibility_Guidelines</id>
	<title>Reproducibility Guidelines - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.anunna.wur.nl/index.php?action=history&amp;feed=atom&amp;title=Reproducibility_Guidelines"/>
	<link rel="alternate" type="text/html" href="https://wiki.anunna.wur.nl/index.php?title=Reproducibility_Guidelines&amp;action=history"/>
	<updated>2026-06-20T00:36:50Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://wiki.anunna.wur.nl/index.php?title=Reproducibility_Guidelines&amp;diff=2869&amp;oldid=prev</id>
		<title>Haars0011: IA migration §8: new Reproducibility Guidelines (versions/containers/Git/WUR GitLab/workflow engines; absorbs Manual GitLab pointer) (via create-page on MediaWiki MCP Server)</title>
		<link rel="alternate" type="text/html" href="https://wiki.anunna.wur.nl/index.php?title=Reproducibility_Guidelines&amp;diff=2869&amp;oldid=prev"/>
		<updated>2026-06-18T14:22:22Z</updated>

		<summary type="html">&lt;p&gt;IA migration §8: new Reproducibility Guidelines (versions/containers/Git/WUR GitLab/workflow engines; absorbs Manual GitLab pointer) (via create-page on MediaWiki MCP Server)&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Reproducible work means that you — or someone else — can run your analysis again later and get the same result. On a shared, evolving cluster this takes a little discipline, but the building blocks are all available on Anunna.&lt;br /&gt;
&lt;br /&gt;
== Pin your software versions ==&lt;br /&gt;
&lt;br /&gt;
* Load specific module versions rather than defaults, and record the [[Environment Modules|bucket]] and module versions you used. A job that loads &amp;lt;code&amp;gt;Python/3.11.3&amp;lt;/code&amp;gt; from the &amp;lt;code&amp;gt;2024&amp;lt;/code&amp;gt; bucket will behave the same next year; one that loads whatever happens to be current may not.&lt;br /&gt;
* For your own environments, pin versions too — record them in a &amp;lt;code&amp;gt;requirements.txt&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;environment.yml&amp;lt;/code&amp;gt;, or equivalent. See [[Installing Personal Software]] and [[Python]].&lt;br /&gt;
&lt;br /&gt;
== Use containers for full reproducibility ==&lt;br /&gt;
&lt;br /&gt;
A container captures an entire software stack — operating-system libraries, tools, and dependencies — in a single image that runs the same anywhere. On Anunna, use [[Apptainer]] (formerly Singularity). A container is the strongest guarantee that your environment will not drift over time.&lt;br /&gt;
&lt;br /&gt;
== Keep your code in version control ==&lt;br /&gt;
&lt;br /&gt;
Track your scripts and pipelines with [https://git-scm.com/ Git] so you have a history of what changed and can return to any version.&lt;br /&gt;
&lt;br /&gt;
WUR runs a GitLab instance at [https://git.wur.nl git.wur.nl] where you can host your repositories. Set up SSH keys for it the same way as for any SSH service — see [[SSH Access]] for generating a key pair — and add the public key to your GitLab account.&lt;br /&gt;
&lt;br /&gt;
== Automate the steps ==&lt;br /&gt;
&lt;br /&gt;
A [[Workflow Engines (Snakemake, Nextflow)|workflow engine]] records the exact steps, their order, and their dependencies, so the whole pipeline can be rerun from scratch. This is far more reproducible than running commands by hand.&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Apptainer]]&lt;br /&gt;
* [[Environment Modules]]&lt;br /&gt;
* [[Workflow Engines (Snakemake, Nextflow)]]&lt;br /&gt;
* [[Installing Personal Software]]&lt;/div&gt;</summary>
		<author><name>Haars0011</name></author>
	</entry>
</feed>