<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing with OASIS Tables v3.0 20080202//EN" "https://jats.nlm.nih.gov/nlm-dtd/publishing/3.0/journalpub-oasis3.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:oasis="http://docs.oasis-open.org/ns/oasis-exchange/table" xml:lang="en" dtd-version="3.0" article-type="research-article">
  <front>
    <journal-meta><journal-id journal-id-type="publisher">GChron</journal-id><journal-title-group>
    <journal-title>Geochronology</journal-title>
    <abbrev-journal-title abbrev-type="publisher">GChron</abbrev-journal-title><abbrev-journal-title abbrev-type="nlm-ta">Geochronology</abbrev-journal-title>
  </journal-title-group><issn pub-type="epub">2628-3719</issn><publisher>
    <publisher-name>Copernicus Publications</publisher-name>
    <publisher-loc>Göttingen, Germany</publisher-loc>
  </publisher></journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.5194/gchron-8-109-2026</article-id><title-group><article-title>FAIR fission track analysis with geochron@home</article-title><alt-title>FAIR fission track analysis with geochron@home</alt-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author" corresp="yes" rid="aff1">
          <name><surname>Vermeesch</surname><given-names>Pieter</given-names></name>
          <email>p.vermeesch@ucl.ac.uk</email>
        <ext-link>https://orcid.org/0000-0003-3404-1209</ext-link></contrib>
        <contrib contrib-type="author" corresp="no" rid="aff1">
          <name><surname>Band</surname><given-names>Tim</given-names></name>
          
        </contrib>
        <contrib contrib-type="author" corresp="no" rid="aff2">
          <name><surname>He</surname><given-names>Jiangping</given-names></name>
          
        </contrib>
        <contrib contrib-type="author" corresp="no" rid="aff1">
          <name><surname>Galbraith</surname><given-names>Rex</given-names></name>
          
        </contrib>
        <contrib contrib-type="author" corresp="no" rid="aff3">
          <name><surname>Carter</surname><given-names>Andrew</given-names></name>
          
        <ext-link>https://orcid.org/0000-0002-0090-5868</ext-link></contrib>
        <aff id="aff1"><label>1</label><institution>University College London, London WC1E 6BT, United Kingdom</institution>
        </aff>
        <aff id="aff2"><label>2</label><institution>King's College London, London SE1 8WA, United Kingdom</institution>
        </aff>
        <aff id="aff3"><label>3</label><institution>Birkbeck, University of London, London WC1E 7HX, United Kingdom</institution>
        </aff>
      </contrib-group>
      <author-notes><corresp id="corr1">Pieter Vermeesch (p.vermeesch@ucl.ac.uk)</corresp></author-notes><pub-date><day>25</day><month>February</month><year>2026</year></pub-date>
      
      <volume>8</volume>
      <issue>1</issue>
      <fpage>109</fpage><lpage>118</lpage>
      <history>
        <date date-type="received"><day>6</day><month>October</month><year>2025</year></date>
           <date date-type="rev-request"><day>15</day><month>October</month><year>2025</year></date>
           <date date-type="rev-recd"><day>23</day><month>December</month><year>2025</year></date>
           <date date-type="accepted"><day>6</day><month>January</month><year>2026</year></date>
      </history>
      <permissions>
        <copyright-statement>Copyright: © 2026 Pieter Vermeesch et al.</copyright-statement>
        <copyright-year>2026</copyright-year>
      <license license-type="open-access"><license-p>This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this licence, visit <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link></license-p></license></permissions><self-uri xlink:href="https://gchron.copernicus.org/articles/8/109/2026/gchron-8-109-2026.html">This article is available from https://gchron.copernicus.org/articles/8/109/2026/gchron-8-109-2026.html</self-uri><self-uri xlink:href="https://gchron.copernicus.org/articles/8/109/2026/gchron-8-109-2026.pdf">The full text article is available as a PDF file from https://gchron.copernicus.org/articles/8/109/2026/gchron-8-109-2026.pdf</self-uri>
      <abstract><title>Abstract</title>

      <p id="d2e130">Fission track thermochronology is based on the visual analysis of optical images. This visual process is prone to observer bias. Fission track datasets are currently reported as numerical summary tables. The interpretation of these tables requires a high degree of trust between the fission track analyst and the user of the data. geochron@home is software that removes this requirement of trust. It combines a browser-based “virtual microscope” with an online database to provide FAIR (Findable, Accessible, Interoperable and Reproducible) access to fission track data.</p>

      <p id="d2e133">geochron@home serves four different purposes. It can be used (1) to count fission tracks in “private mode”, i.e. hidden from other users on the internet; (2) to archive fission track images and counts for inspection by other users; (3) to create tutorials for new students of the fission track method; and (4) to serve randomly selected selections of images to citizen scientists. We illustrate these four applications with examples that demonstrate (1) geochron@home's ability to compare and combine fission track counts for multiple users within a lab group; (2) the value of the geochron@home archive in the peer review system; (3) the use of simple tutorials in teaching novice users how to count fission tracks; and (4) the opportunities and challenges of crowd-sourced fission track analysis.</p>

      <p id="d2e136">geochron@home was written in Python and Javascript. Its code is freely available for inspection and modification, allowing users to set up their own geochron@home server. Alternatively, users who would like to upload data to the archive, but do not have the facilities to set up their own server, may use the server at University College London free of charge. The archive accepts image stacks acquired on any type of digital microscope, and accommodates fission track data (counts and length measurements) from external fission track analysis suites such as Fission Track Studio and Track<italic>Flow</italic>.</p>

      <p id="d2e142">We anticipate that the introduction of FAIR workflows will make fission track data more accurate and more future proof. Storing fission track data online will benefit future developments in fission track thermochronology. For example, archival datasets of peer reviewed fission track counts can be used to train and improve machine learning algorithms for automated fission track analysis. We invite other geochronological methods to follow the fission track community's lead in FAIR data processing. This would benefit all the Earth Science disciplines that depend on geochronological data.</p>
  </abstract>
    
<funding-group>
<award-group id="gs1">
<funding-source>Natural Environment Research Council</funding-source>
<award-id>NE/T001518/1</award-id>
</award-group>
</funding-group>
</article-meta>
  </front>
<body>
      

<sec id="Ch1.S1" sec-type="intro">
  <label>1</label><title>Introduction</title>
      <p id="d2e154">Science is on an irreversible trajectory towards greater openness. Geochronology is no exception to this trend, as this journal illustrates with its open access and review policies. Funding agencies increasingly demand that research results and data are shared with the public. Currently, geochronological data are generally provided as flat tables of dates or isotopic ratio estimates. However, in other fields of science such as physics, it is common practice to share the raw unprocessed measurements along with processing instructions <xref ref-type="bibr" rid="bib1.bibx1" id="paren.1"><named-content content-type="pre">e.g.,</named-content></xref>. This paper moves geochronology in the same direction. It presents a mechanism to generate and store fully FAIR <xref ref-type="bibr" rid="bib1.bibx22" id="paren.2"><named-content content-type="pre">Findable, Accessible, Interoperable and Reproducible;</named-content></xref> data in the context of fission track analysis.</p>
      <p id="d2e167">Unlike most other geochronometers, which require mass spectrometers to estimate parent-daughter ratios, fission tracks are observed under an optical microscope and counted by a human observer.  In recent years, digital microscopy has moved fission track data acquisition from the ocular lenses of a microscope to the computer screen <xref ref-type="bibr" rid="bib1.bibx6 bib1.bibx5 bib1.bibx16" id="paren.3"/>. Ongoing developments in artificial intelligence generate further opportunities to improve the throughput and accuracy of fission track data <xref ref-type="bibr" rid="bib1.bibx12 bib1.bibx9 bib1.bibx13 bib1.bibx2" id="paren.4"/>. But despite the richness of the digital datasets produced by these novel tools, fission track data are still reported as numerical summary tables. These tables require an unnecessary degree of trust between the “producer” and “consumer” of the data.</p>
      <p id="d2e177">geochron@home is a free and open software platform that allows geochronologists to share their raw fission track data over the internet for perusal by peer reviewers, colleagues and the general public. geochron@home is a virtual petrographic microscope connected to a database with digital image stacks of etched fission track samples. The platform can be used to acquire, archive and inspect fission track data in full adherence to the FAIR data principles. In Sect. <xref ref-type="sec" rid="Ch1.S2"/>, we will describe geochron@home's software architecture in five steps. We will show that this architecture accommodates imagery from any type of digital microscope. It enables flexible workflows that can be adapted to four different applications.</p>
      <p id="d2e182">Using image stacks of Mount Dromedary apatite, we will show how geochron@home can be used to count fission tracks in “private mode” (Sect. <xref ref-type="sec" rid="Ch1.S3"/>); to archive published fission track datasets in “public mode” (Sect. <xref ref-type="sec" rid="Ch1.S4"/>); to build tutorials for training purposes (Sect. <xref ref-type="sec" rid="Ch1.S5"/>); and to crowd-source fission track data on the internet (Sect. <xref ref-type="sec" rid="Ch1.S6"/>). Because geochron@home is free and open, it can be extended and improved by any interested party. We make some suggestions for future improvements in Sect. <xref ref-type="sec" rid="Ch1.S7"/>. We hope that the geochron@home's example will be followed in other geochronological disciplines, as this will benefit not only geochronology itself, but all the other disciplines that depend on it (Sect. <xref ref-type="sec" rid="Ch1.S8"/>).</p>
</sec>
<sec id="Ch1.S2">
  <label>2</label><title>Workflow</title>
      <p id="d2e206">The geochron@home workflow separates the acquisition of microscope images from their analysis, providing the flexibility to accommodate data from different microscope manufacturers. The workflow can be broken down into five steps.</p>
      <p id="d2e209"><list list-type="order">
          <list-item>

      <p id="d2e214">Acquisition of <inline-formula><mml:math id="M1" display="inline"><mml:mi>z</mml:mi></mml:math></inline-formula>-stacks of microscope images in reflected and transmitted light for each of the grains in a sample and, optionally, for the accompanying external detector (Fig. <xref ref-type="fig" rid="F1"/>). At University College London (UCL), this first step is currently accomplished by a Python macro within Zeiss' Zen Blue software.  However, geochron@home can also accommodate imagery from other platforms, such as Fission Track Studio <xref ref-type="bibr" rid="bib1.bibx6" id="paren.5"><named-content content-type="pre">Zeiss;</named-content></xref> and Track<italic>Flow</italic>
<xref ref-type="bibr" rid="bib1.bibx16" id="paren.6"><named-content content-type="pre">Nikon;</named-content></xref>.</p>
          </list-item>
          <list-item>

      <p id="d2e242">Prepare the <inline-formula><mml:math id="M2" display="inline"><mml:mi>z</mml:mi></mml:math></inline-formula>-stacks for uploading to the geochron@home database. This database requires that the images are organised as a nested sequence of directories, in which a “project” consists of “samples” that comprise a number of “grains”.  Each grain corresponds to a numbered sequence of <monospace>.jpeg</monospace> images, one for each layer of the <inline-formula><mml:math id="M3" display="inline"><mml:mi>z</mml:mi></mml:math></inline-formula>-stack. Note that the raw microscope images are generally not stored as <monospace>.jpeg</monospace> files but in uncompressed <monospace>.czi</monospace> (for Zen Blue), <monospace>.tif</monospace> (for Fission Track Studio 1 and 2) or <monospace>.nd2</monospace> (for Nikon/Track<italic>Flow</italic>) formats. Conversion from these raw images to sequences of <monospace>.jpeg</monospace> files is done with a shell script using Imagemagick <xref ref-type="bibr" rid="bib1.bibx14" id="paren.7"/>.</p>

      <p id="d2e284">In addition to the sequence of <monospace>.jpeg</monospace> images, a low level “grain” folder can also include an optional file called <monospace>roi.json</monospace> containing the vertices of a default region of interest for spontaneous (and/or induced) track counting. The database structure can also accommodate existing fission track counting results.  For example, if a user has already counted their fission tracks in Fission Track Studio, then they can store those results in a <monospace>.json</monospace> file at the “sample” level directory. Because Fission Track Studio stores its results in an <monospace>.xml</monospace> format, a second conversion script was created to translate those results into an equivalent <monospace>.json</monospace> format. Both <monospace>.xml</monospace> and <monospace>.json</monospace> are extensible, providing a mechanism to accommodate future updates of the metadata (Sect. <xref ref-type="sec" rid="Ch1.S7"/>).</p>
          </list-item>
          <list-item>

      <p id="d2e314">Upload the data to the geochron@home platform. geochron@home is a Django web-app with a PostgreSQL database.  The database can be accessed via a Python API and a (more limited) web-based GUI. Accessing the API requires administrator privileges. Administrators can create projects, samples and grains; download data; and set the access rights of “ordinary” users. Projects can be private or public. The source code and installation instructions for geochron@home are freely available over GitHub (see the Data Availability statement at the end of this paper). This allows fission track users to set up their own server. Alternatively, fission track labs can upload their data to the UCL server by contacting the corresponding author.</p>
          </list-item>
          <list-item>

      <p id="d2e320">Analyse the images with a browser-based “virtual fission track microscope” powered by the Leaflet library (JavaScript). This virtual instrument acts as a front-end to geochron@home. It has a simple user interface with controls to zoom, pan and focus in or out of the digital image stack. Depending on the permissions granted to the user by the administrator, the virtual microscope offers a number of different options.  Entry level “ordinary” users are only allowed to count tracks by clicking within a pre-defined “region of interest”. In contrast, “superusers” are allowed to define their own regions of interest. Once the user is satisfied that they have counted all the fission tracks in a particular grain, they can submit the results to the server. They are then presented with a new set of images until all grains are counted.</p>

      <p id="d2e323">The determination of who qualifies as a “superuser” is made by the administrator of each geochron@home server. For the UCL server, this role is held by the first author of this paper. Because the geochron@home source code is free and open, anyone may set up and administer their own server independently of the development team.</p>
          </list-item>
          <list-item>

      <p id="d2e329">Post-processing. The fission track data can either be downloaded as a flat data table of counts and areas, or as a <monospace>.json</monospace> file containing the locations of all the counted tracks. geochron@home does not provide any tools to post-process these files. They are meant to be passed on to other tools such as spreadsheet applications or IsoplotR <xref ref-type="bibr" rid="bib1.bibx17" id="paren.8"/>.</p>
          </list-item>
        </list></p>
      <p id="d2e340">The five-step workflow can be used for several applications, including (1) conventional fission track analysis; (2) archiving published fission track results; (3) building tutorials; and (4) crowd-sourcing fission track data. The next sections of this paper will illustrate these applications with real world examples.</p>

      <fig id="F1" specific-use="star"><label>Figure 1</label><caption><p id="d2e346">Screenshots of raw fission track data for the external detector method in geochron@home. GR: an apatite grain in reflected light; GT: the same grain in transmitted light; MR: the corresponding mica detector in reflected light; MT: the mica detector in transmitted light. White rectangles mark the region of interest (ROI), within which an analyst has counted fission tracks by marking their etch pits (shown in yellow). The raw data for this figure can be viewed on the geochron@home archive (<uri>https://github.com/pvermees/GaHa</uri>, last access: 15 January 2026).</p></caption>
        <graphic xlink:href="https://gchron.copernicus.org/articles/8/109/2026/gchron-8-109-2026-f01.jpg"/>

      </fig>

</sec>
<sec id="Ch1.S3">
  <label>3</label><title>Counting fission tracks in “private mode”</title>
      <p id="d2e366">Administrators can define regions of interest (ROI) and count or edit the fission track coordinates of any grain in a geochron@home database. They can also assign other users to groups, and give these groups access to a subset of the projects in the database. Administrators have fine control over the permissions of the groups. For example, they can allow the members of one group to define their own ROIs, whilst requiring members of another group to count fission tracks in predefined ROIs.  Groups provide a mechanism to compare and combine the results of multiple analysts of the same sample. Figure <xref ref-type="fig" rid="F2"/> illustrates this with two sets of fission track density estimates for the same sample of Mount Dromedary apatite <xref ref-type="bibr" rid="bib1.bibx7" id="paren.9"/>, analysed by two users (PV and AC).</p>
      <p id="d2e374">Let <inline-formula><mml:math id="M4" display="inline"><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">1</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math id="M5" display="inline"><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> be the numbers of spontaneous tracks counted by the two users over areas <inline-formula><mml:math id="M6" display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mn mathvariant="normal">1</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math id="M7" display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>, respectively. Then their estimated track densities are given by <inline-formula><mml:math id="M8" display="inline"><mml:mrow><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo mathvariant="normal" stretchy="false">^</mml:mo></mml:mover><mml:mn mathvariant="normal">1</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">1</mml:mn></mml:msub><mml:mo>/</mml:mo><mml:msub><mml:mi>A</mml:mi><mml:mn mathvariant="normal">1</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math id="M9" display="inline"><mml:mrow><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo mathvariant="normal" stretchy="false">^</mml:mo></mml:mover><mml:mn mathvariant="normal">2</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msub><mml:mo>/</mml:mo><mml:msub><mml:mi>A</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>. In this situation when the two areas overlap, <inline-formula><mml:math id="M10" display="inline"><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">1</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math id="M11" display="inline"><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> cannot be treated as independent Poisson counts because the two analysts will count some of the same tracks. It can be shown that, under simple (ideal) assumptions, the uncertainty of the ratio of the estimated track densities is given approximately by

          <disp-formula id="Ch1.E1" content-type="numbered"><label>1</label><mml:math id="M12" display="block"><mml:mrow><mml:mstyle displaystyle="true"><mml:mfrac style="display"><mml:mrow><mml:mtext>se</mml:mtext><mml:mo>(</mml:mo><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo stretchy="false" mathvariant="normal">^</mml:mo></mml:mover><mml:mn mathvariant="normal">1</mml:mn></mml:msub><mml:mo>/</mml:mo><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo stretchy="false" mathvariant="normal">^</mml:mo></mml:mover><mml:mn mathvariant="normal">2</mml:mn></mml:msub><mml:mo>)</mml:mo></mml:mrow><mml:mrow><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo stretchy="false" mathvariant="normal">^</mml:mo></mml:mover><mml:mn mathvariant="normal">1</mml:mn></mml:msub><mml:mo>/</mml:mo><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo stretchy="false" mathvariant="normal">^</mml:mo></mml:mover><mml:mn mathvariant="normal">2</mml:mn></mml:msub></mml:mrow></mml:mfrac></mml:mstyle><mml:mo>≈</mml:mo><mml:msqrt><mml:mrow><mml:mstyle displaystyle="true"><mml:mfrac style="display"><mml:mn mathvariant="normal">1</mml:mn><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">1</mml:mn></mml:msub></mml:mrow></mml:mfrac></mml:mstyle><mml:mo>+</mml:mo><mml:mstyle displaystyle="true"><mml:mfrac style="display"><mml:mn mathvariant="normal">1</mml:mn><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msub></mml:mrow></mml:mfrac></mml:mstyle><mml:mo>-</mml:mo><mml:mstyle displaystyle="true"><mml:mfrac style="display"><mml:mrow><mml:mn mathvariant="normal">2</mml:mn><mml:mspace linebreak="nobreak" width="0.125em"/><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">0</mml:mn></mml:msub></mml:mrow><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">1</mml:mn></mml:msub><mml:mspace linebreak="nobreak" width="0.125em"/><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msub></mml:mrow></mml:mfrac></mml:mstyle></mml:mrow></mml:msqrt></mml:mrow></mml:math></disp-formula>

        where <inline-formula><mml:math id="M13" display="inline"><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">0</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> is the number of tracks counted by both observers in the area of overlap (<inline-formula><mml:math id="M14" display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mn mathvariant="normal">0</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>, say) between their respective ROIs.</p>
      <p id="d2e625">The combined data plots of Fig. <xref ref-type="fig" rid="F2"/>b and c contain two sets of counts for 25 grains, with <inline-formula><mml:math id="M15" display="inline"><mml:mrow><mml:mo>∑</mml:mo><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">1</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">686</mml:mn></mml:mrow></mml:math></inline-formula> (PV) and <inline-formula><mml:math id="M16" display="inline"><mml:mrow><mml:mo>∑</mml:mo><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">679</mml:mn></mml:mrow></mml:math></inline-formula> (AC), and a weighted mean track density ratio <inline-formula><mml:math id="M17" display="inline"><mml:mrow><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo stretchy="false" mathvariant="normal">^</mml:mo></mml:mover><mml:mn mathvariant="normal">1</mml:mn></mml:msub><mml:mo>/</mml:mo><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo stretchy="false" mathvariant="normal">^</mml:mo></mml:mover><mml:mn mathvariant="normal">2</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">0.94</mml:mn></mml:mrow></mml:math></inline-formula> with relative standard error 0.013. PV counted 600 tracks in those common areas <inline-formula><mml:math id="M18" display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mn mathvariant="normal">0</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>, of which 549 were also counted by AC. Conversely, AC counted 622 tracks of which 549 were also counted by PV. The ratio of the two analysts' track density estimates based just on the common area is therefore 600/622 <inline-formula><mml:math id="M19" display="inline"><mml:mo>=</mml:mo></mml:math></inline-formula> 0.965 with relative standard error 0.018, calculated from Eq. (<xref ref-type="disp-formula" rid="Ch1.E1"/>), with <inline-formula><mml:math id="M20" display="inline"><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">1</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">686</mml:mn></mml:mrow></mml:math></inline-formula>, <inline-formula><mml:math id="M21" display="inline"><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">679</mml:mn></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math id="M22" display="inline"><mml:mrow><mml:msub><mml:mi>N</mml:mi><mml:mn mathvariant="normal">0</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">549</mml:mn></mml:mrow></mml:math></inline-formula>. This is close to the weighted mean ratio of 0.94 (Fig. <xref ref-type="fig" rid="F2"/>c), and is slightly nearer to 1. It indicates that PV under-counts the Mount Dromedary apatite by 3.5 % relative to AC.  The existence of “observer bias” is well documented <xref ref-type="bibr" rid="bib1.bibx15" id="paren.10"/>.  It is one of the reasons why fission track analysis is often done relative to age standards: observer bias does not have to be a problem provided that it is consistent between samples and standards.</p>

      <fig id="F2" specific-use="star"><label>Figure 2</label><caption><p id="d2e767">Comparison of fission track data for Mount Dromedary apatite by two analysts (PV <inline-formula><mml:math id="M23" display="inline"><mml:mo>=</mml:mo></mml:math></inline-formula> Pieter Vermeesch and AC <inline-formula><mml:math id="M24" display="inline"><mml:mo>=</mml:mo></mml:math></inline-formula> Andrew Carter). <bold>(a)</bold> the track counts and ROIs of both users for grain 3, shown in blue (PV) and red (AC); <bold>(b)</bold> comparison of the track densities for PV and AC for all 25 grains analysed by the two analysts with a reference line for <inline-formula><mml:math id="M25" display="inline"><mml:mrow><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo stretchy="false" mathvariant="normal">^</mml:mo></mml:mover><mml:mtext>PV</mml:mtext></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mover accent="true"><mml:mi mathvariant="italic">ρ</mml:mi><mml:mo mathvariant="normal" stretchy="false">^</mml:mo></mml:mover><mml:mtext>AC</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>; <bold>(c)</bold> radial plot of the same data, using Eq. (<xref ref-type="disp-formula" rid="Ch1.E1"/>).</p></caption>
        <graphic xlink:href="https://gchron.copernicus.org/articles/8/109/2026/gchron-8-109-2026-f02.png"/>

      </fig>

</sec>
<sec id="Ch1.S4">
  <label>4</label><title>The geochron@home archive (GaHa)</title>
      <p id="d2e834">Once a set of fission track images has been analysed and the analyst is confident that the results are accurate, the status of the results can be changed from private to public. This makes the results visible over the internet as a list of URLs, where each grain number and user ID corresponds to a unique address. The geochron@home archive (GaHa) brings fission track geochronology into the era of FAIR science. It allows peer reviewers to inspect the raw data from which thermochronological inferences are made. The archive is open to submissions from any fission track laboratory, free of charge. However, as mentioned in Sect. <xref ref-type="sec" rid="Ch1.S2"/>, it is also possible to establish a new archive elsewhere. At the time of writing, GaHa contains data for three studies:</p>
      <p id="d2e839"><list list-type="order">
          <list-item>

      <p id="d2e844"><xref ref-type="bibr" rid="bib1.bibx8" id="text.11"/>: this is an LA-ICP-MS based fission track study of detrital apatite from the northeastern Tibetan Plateau. It contains image stacks of semitracks in 1146 apatite grains from 16 different samples.</p>
          </list-item>
          <list-item>

      <p id="d2e852"><xref ref-type="bibr" rid="bib1.bibx15" id="text.12"/>: this is a round-robin study in which digital image stacks of 44 apatite crystals were circulated among 14 different analysts. These analysts used the FastTrack image analysis software <xref ref-type="bibr" rid="bib1.bibx6" id="paren.13"><named-content content-type="pre">which is part of the Fission Track Studio suite;</named-content></xref> to define their own ROIs and count the semitracks and horizontally confined fission tracks in them. GaHa presents the results of the round-robin experiment as a <inline-formula><mml:math id="M26" display="inline"><mml:mrow><mml:mn mathvariant="normal">44</mml:mn><mml:mo>×</mml:mo><mml:mn mathvariant="normal">14</mml:mn></mml:mrow></mml:math></inline-formula> grid of URLs.</p>
          </list-item>
          <list-item>

      <p id="d2e877">This study: All the raw fission track data used in this article are available on GaHa, along with the post-processing software that was used to produce the figures. Together, these resources provide the reader with all the information needed to fully reproduce our results, “from cradle to grave”. To our knowledge, this is the first geochronological study to do so.</p>
          </list-item>
        </list></p>
</sec>
<sec id="Ch1.S5">
  <label>5</label><title>geochron@home tutorials</title>
      <p id="d2e891">Given the right permissions (assigned by an administrator), users can build tutorial pages by annotating features in fission track images. These features can be tracks or other objects such as scratches, inclusions, dislocations or holes. A selection of tutorial pages is presented to new users when they first log into geochron@home. They must complete the tutorial before being allowed to count fission tracks.  The tutorial pages can be revisited at any time by visiting the corresponding link on the geochron@home landing page.</p>
      <p id="d2e894">Some exemplar annotations in the current tutorial pages were made by an experienced fission track analyst (Andrew Carter). This basic tutorial provides a quick and easy mechanism to train novice users in the art of fission track analysis. The tutorial pages are in their infancy and offer only a limited degree of interactivity. Users can click on features to read the annotations. A more detailed, comprehensive tutorial will grow with the wider input from experienced analysts and future plans include the addition of fully interactive “quizzes” (Sect. <xref ref-type="sec" rid="Ch1.S8"/>). The limitations of the current tutorials are apparent in the results of the crowd-sourcing experiment described in the next section of this paper.</p>
</sec>
<sec id="Ch1.S6">
  <label>6</label><title>Crowd-sourcing fission track data</title>
      <p id="d2e907">In 1906, Sir Francis Galton visited a county fair in which a contest was held to guess the weight of an ox. 787 people participated in the event. Galton discovered that the median of all their estimates was within 0.8 % of the true weight of the ox and more accurate than 90 % of the individual estimates. Such is the “wisdom of crowds” <xref ref-type="bibr" rid="bib1.bibx4" id="paren.14"/>. Similar effects are seen in fission track geochronology. An interlaboratory comparison study by <xref ref-type="bibr" rid="bib1.bibx10" id="text.15"/> showed that the average of several fission track age estimates is closer to the known age of mineral standards than the age obtained by individual observers. Inspired by these previous experiments, we used geochron@home to bring fission track analysis to a proverbial “county fair” of citizen scientists.</p>
      <p id="d2e916">We here present the results of a type of “crowd-sourcing” experiment that was carried out at UCL as part of an undergraduate course in isotope geology. 68 students were asked to create an account on the geochron@home server by selecting a unique username and password. After spending a few minutes to complete the compulsory tutorial (Sect. <xref ref-type="sec" rid="Ch1.S5"/>), they were asked to count fission tracks in randomly assigned image stacks of Mount Dromedary apatite. Each student was required to analyse at least 15 grains, using pre-defined ROIs. In a matter of hours, the students amassed a dataset of 37 331 fission track counts in 34 grains.  This large dataset was parsed into separate data files – one for each student – which they processed during an assessed programming exercise.</p>

<table-wrap id="T1" specific-use="star" orientation="landscape"><label>Table 1</label><caption><p id="d2e924">Counts of fission tracks in the same ROIs of 25 grains made by PV and 68 students. Only 20 students are shown due to space constraints; the full table is provided in the GaHa.  Each student counted a subset of the grains. The grains are listed in increasing order of PV's counts. The last 3 columns give, for each student, the number of grains counted <inline-formula><mml:math id="M27" display="inline"><mml:mrow><mml:msub><mml:mi>n</mml:mi><mml:mi mathvariant="normal">g</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> and the weighted mean <inline-formula><mml:math id="M28" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mo>∑</mml:mo><mml:mspace width="0.125em" linebreak="nobreak"/><mml:msub><mml:mi>w</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mspace width="0.125em" linebreak="nobreak"/><mml:msub><mml:mi>r</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo>/</mml:mo><mml:mo>∑</mml:mo><mml:mspace width="0.125em" linebreak="nobreak"/><mml:msub><mml:mi>w</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> and standard deviation <inline-formula><mml:math id="M29" display="inline"><mml:mrow><mml:msub><mml:mi>s</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:msqrt><mml:mrow><mml:mo>∑</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mspace width="0.125em" linebreak="nobreak"/><mml:mo>(</mml:mo><mml:msub><mml:mi>r</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo>-</mml:mo><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub><mml:msup><mml:mo>)</mml:mo><mml:mn mathvariant="normal">2</mml:mn></mml:msup><mml:mo>/</mml:mo><mml:mo>(</mml:mo><mml:msub><mml:mi>n</mml:mi><mml:mi mathvariant="normal">g</mml:mi></mml:msub><mml:mi mathvariant="normal">−</mml:mi><mml:mn mathvariant="normal">1</mml:mn><mml:mo>)</mml:mo></mml:mrow></mml:msqrt></mml:mrow></mml:math></inline-formula> where <inline-formula><mml:math id="M30" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> is the ratio of the student's count to PV's count for grain <inline-formula><mml:math id="M31" display="inline"><mml:mi>i</mml:mi></mml:math></inline-formula> and <inline-formula><mml:math id="M32" display="inline"><mml:mrow><mml:msub><mml:mi>w</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> is PV's count for grain <inline-formula><mml:math id="M33" display="inline"><mml:mi>i</mml:mi></mml:math></inline-formula>. (<inline-formula><mml:math id="M34" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> is the same as the ratio of the student's total count over the <inline-formula><mml:math id="M35" display="inline"><mml:mrow><mml:msub><mml:mi>n</mml:mi><mml:mi mathvariant="normal">g</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> grains to PV's total count over the same grains).  The students are listed in decreasing order of <inline-formula><mml:math id="M36" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula>. <inline-formula><mml:math id="M37" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">m</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> is the ratio of the students' median count per grain to PV's count.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="29">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="right"/>
     <oasis:colspec colnum="3" colname="col3" align="right"/>
     <oasis:colspec colnum="4" colname="col4" align="right"/>
     <oasis:colspec colnum="5" colname="col5" align="right"/>
     <oasis:colspec colnum="6" colname="col6" align="right"/>
     <oasis:colspec colnum="7" colname="col7" align="right"/>
     <oasis:colspec colnum="8" colname="col8" align="right"/>
     <oasis:colspec colnum="9" colname="col9" align="right"/>
     <oasis:colspec colnum="10" colname="col10" align="right"/>
     <oasis:colspec colnum="11" colname="col11" align="right"/>
     <oasis:colspec colnum="12" colname="col12" align="right"/>
     <oasis:colspec colnum="13" colname="col13" align="right"/>
     <oasis:colspec colnum="14" colname="col14" align="right"/>
     <oasis:colspec colnum="15" colname="col15" align="right"/>
     <oasis:colspec colnum="16" colname="col16" align="right"/>
     <oasis:colspec colnum="17" colname="col17" align="right"/>
     <oasis:colspec colnum="18" colname="col18" align="right"/>
     <oasis:colspec colnum="19" colname="col19" align="right"/>
     <oasis:colspec colnum="20" colname="col20" align="right"/>
     <oasis:colspec colnum="21" colname="col21" align="right"/>
     <oasis:colspec colnum="22" colname="col22" align="right"/>
     <oasis:colspec colnum="23" colname="col23" align="right"/>
     <oasis:colspec colnum="24" colname="col24" align="right"/>
     <oasis:colspec colnum="25" colname="col25" align="right"/>
     <oasis:colspec colnum="26" colname="col26" align="right" colsep="1"/>
     <oasis:colspec colnum="27" colname="col27" align="right"/>
     <oasis:colspec colnum="28" colname="col28" align="right"/>
     <oasis:colspec colnum="29" colname="col29" align="right"/>
     <oasis:thead>
       <oasis:row rowsep="1">
         <oasis:entry namest="col1" nameend="col29" align="center">grain ID </oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">user</oasis:entry>
         <oasis:entry colname="col2">1</oasis:entry>
         <oasis:entry colname="col3">41</oasis:entry>
         <oasis:entry colname="col4">32</oasis:entry>
         <oasis:entry colname="col5">3</oasis:entry>
         <oasis:entry colname="col6">4</oasis:entry>
         <oasis:entry colname="col7">10</oasis:entry>
         <oasis:entry colname="col8">28</oasis:entry>
         <oasis:entry colname="col9">31</oasis:entry>
         <oasis:entry colname="col10">11</oasis:entry>
         <oasis:entry colname="col11">30</oasis:entry>
         <oasis:entry colname="col12">22</oasis:entry>
         <oasis:entry colname="col13">34</oasis:entry>
         <oasis:entry colname="col14">12</oasis:entry>
         <oasis:entry colname="col15">36</oasis:entry>
         <oasis:entry colname="col16">27</oasis:entry>
         <oasis:entry colname="col17">6</oasis:entry>
         <oasis:entry colname="col18">2</oasis:entry>
         <oasis:entry colname="col19">15</oasis:entry>
         <oasis:entry colname="col20">8</oasis:entry>
         <oasis:entry colname="col21">38</oasis:entry>
         <oasis:entry colname="col22">7</oasis:entry>
         <oasis:entry colname="col23">25</oasis:entry>
         <oasis:entry colname="col24">23</oasis:entry>
         <oasis:entry colname="col25">39</oasis:entry>
         <oasis:entry colname="col26">43</oasis:entry>
         <oasis:entry colname="col27"><inline-formula><mml:math id="M38" display="inline"><mml:mrow><mml:msub><mml:mi>n</mml:mi><mml:mi mathvariant="normal">g</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>
         <oasis:entry colname="col28"><inline-formula><mml:math id="M39" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>
         <oasis:entry colname="col29"><inline-formula><mml:math id="M40" display="inline"><mml:mrow><mml:msub><mml:mi>s</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">PV</oasis:entry>
         <oasis:entry colname="col2">9</oasis:entry>
         <oasis:entry colname="col3">10</oasis:entry>
         <oasis:entry colname="col4">11</oasis:entry>
         <oasis:entry colname="col5">12</oasis:entry>
         <oasis:entry colname="col6">14</oasis:entry>
         <oasis:entry colname="col7">14</oasis:entry>
         <oasis:entry colname="col8">18</oasis:entry>
         <oasis:entry colname="col9">19</oasis:entry>
         <oasis:entry colname="col10">21</oasis:entry>
         <oasis:entry colname="col11">21</oasis:entry>
         <oasis:entry colname="col12">22</oasis:entry>
         <oasis:entry colname="col13">22</oasis:entry>
         <oasis:entry colname="col14">25</oasis:entry>
         <oasis:entry colname="col15">25</oasis:entry>
         <oasis:entry colname="col16">27</oasis:entry>
         <oasis:entry colname="col17">28</oasis:entry>
         <oasis:entry colname="col18">32</oasis:entry>
         <oasis:entry colname="col19">35</oasis:entry>
         <oasis:entry colname="col20">37</oasis:entry>
         <oasis:entry colname="col21">44</oasis:entry>
         <oasis:entry colname="col22">46</oasis:entry>
         <oasis:entry colname="col23">50</oasis:entry>
         <oasis:entry colname="col24">52</oasis:entry>
         <oasis:entry colname="col25">63</oasis:entry>
         <oasis:entry colname="col26">66</oasis:entry>
         <oasis:entry colname="col27">25</oasis:entry>
         <oasis:entry colname="col28">1.00</oasis:entry>
         <oasis:entry colname="col29">0.00</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">255</oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">15</oasis:entry>
         <oasis:entry colname="col5">16</oasis:entry>
         <oasis:entry colname="col6">18</oasis:entry>
         <oasis:entry colname="col7">17</oasis:entry>
         <oasis:entry colname="col8">25</oasis:entry>
         <oasis:entry colname="col9">22</oasis:entry>
         <oasis:entry colname="col10"/>
         <oasis:entry colname="col11"/>
         <oasis:entry colname="col12">23</oasis:entry>
         <oasis:entry colname="col13">26</oasis:entry>
         <oasis:entry colname="col14"/>
         <oasis:entry colname="col15">25</oasis:entry>
         <oasis:entry colname="col16">31</oasis:entry>
         <oasis:entry colname="col17"/>
         <oasis:entry colname="col18">31</oasis:entry>
         <oasis:entry colname="col19">39</oasis:entry>
         <oasis:entry colname="col20">40</oasis:entry>
         <oasis:entry colname="col21"/>
         <oasis:entry colname="col22">37</oasis:entry>
         <oasis:entry colname="col23">63</oasis:entry>
         <oasis:entry colname="col24">48</oasis:entry>
         <oasis:entry colname="col25">65</oasis:entry>
         <oasis:entry colname="col26">67</oasis:entry>
         <oasis:entry colname="col27">18</oasis:entry>
         <oasis:entry colname="col28">1.08</oasis:entry>
         <oasis:entry colname="col29">0.84</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">271</oasis:entry>
         <oasis:entry colname="col2">9</oasis:entry>
         <oasis:entry colname="col3">11</oasis:entry>
         <oasis:entry colname="col4">14</oasis:entry>
         <oasis:entry colname="col5">14</oasis:entry>
         <oasis:entry colname="col6">16</oasis:entry>
         <oasis:entry colname="col7">15</oasis:entry>
         <oasis:entry colname="col8">23</oasis:entry>
         <oasis:entry colname="col9">18</oasis:entry>
         <oasis:entry colname="col10">22</oasis:entry>
         <oasis:entry colname="col11">22</oasis:entry>
         <oasis:entry colname="col12">23</oasis:entry>
         <oasis:entry colname="col13">19</oasis:entry>
         <oasis:entry colname="col14">28</oasis:entry>
         <oasis:entry colname="col15">22</oasis:entry>
         <oasis:entry colname="col16">27</oasis:entry>
         <oasis:entry colname="col17">29</oasis:entry>
         <oasis:entry colname="col18">31</oasis:entry>
         <oasis:entry colname="col19">35</oasis:entry>
         <oasis:entry colname="col20">34</oasis:entry>
         <oasis:entry colname="col21">41</oasis:entry>
         <oasis:entry colname="col22">46</oasis:entry>
         <oasis:entry colname="col23">56</oasis:entry>
         <oasis:entry colname="col24">54</oasis:entry>
         <oasis:entry colname="col25">52</oasis:entry>
         <oasis:entry colname="col26">56</oasis:entry>
         <oasis:entry colname="col27">25</oasis:entry>
         <oasis:entry colname="col28">0.99</oasis:entry>
         <oasis:entry colname="col29">0.61</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">215</oasis:entry>
         <oasis:entry colname="col2">10</oasis:entry>
         <oasis:entry colname="col3">10</oasis:entry>
         <oasis:entry colname="col4">12</oasis:entry>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6">9</oasis:entry>
         <oasis:entry colname="col7"/>
         <oasis:entry colname="col8">25</oasis:entry>
         <oasis:entry colname="col9">20</oasis:entry>
         <oasis:entry colname="col10">19</oasis:entry>
         <oasis:entry colname="col11">23</oasis:entry>
         <oasis:entry colname="col12">22</oasis:entry>
         <oasis:entry colname="col13">22</oasis:entry>
         <oasis:entry colname="col14"/>
         <oasis:entry colname="col15"/>
         <oasis:entry colname="col16"/>
         <oasis:entry colname="col17">35</oasis:entry>
         <oasis:entry colname="col18">30</oasis:entry>
         <oasis:entry colname="col19">34</oasis:entry>
         <oasis:entry colname="col20">36</oasis:entry>
         <oasis:entry colname="col21">34</oasis:entry>
         <oasis:entry colname="col22">56</oasis:entry>
         <oasis:entry colname="col23"/>
         <oasis:entry colname="col24">44</oasis:entry>
         <oasis:entry colname="col25">62</oasis:entry>
         <oasis:entry colname="col26">62</oasis:entry>
         <oasis:entry colname="col27">19</oasis:entry>
         <oasis:entry colname="col28">0.99</oasis:entry>
         <oasis:entry colname="col29">0.85</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">236</oasis:entry>
         <oasis:entry colname="col2">9</oasis:entry>
         <oasis:entry colname="col3">9</oasis:entry>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6"/>
         <oasis:entry colname="col7"/>
         <oasis:entry colname="col8">18</oasis:entry>
         <oasis:entry colname="col9"/>
         <oasis:entry colname="col10">19</oasis:entry>
         <oasis:entry colname="col11">18</oasis:entry>
         <oasis:entry colname="col12">21</oasis:entry>
         <oasis:entry colname="col13">20</oasis:entry>
         <oasis:entry colname="col14">27</oasis:entry>
         <oasis:entry colname="col15">23</oasis:entry>
         <oasis:entry colname="col16">28</oasis:entry>
         <oasis:entry colname="col17">30</oasis:entry>
         <oasis:entry colname="col18"/>
         <oasis:entry colname="col19">38</oasis:entry>
         <oasis:entry colname="col20"/>
         <oasis:entry colname="col21">41</oasis:entry>
         <oasis:entry colname="col22">39</oasis:entry>
         <oasis:entry colname="col23">55</oasis:entry>
         <oasis:entry colname="col24"/>
         <oasis:entry colname="col25"/>
         <oasis:entry colname="col26"/>
         <oasis:entry colname="col27">15</oasis:entry>
         <oasis:entry colname="col28">0.98</oasis:entry>
         <oasis:entry colname="col29">0.49</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">229</oasis:entry>
         <oasis:entry colname="col2">8</oasis:entry>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5">15</oasis:entry>
         <oasis:entry colname="col6">11</oasis:entry>
         <oasis:entry colname="col7">17</oasis:entry>
         <oasis:entry colname="col8">26</oasis:entry>
         <oasis:entry colname="col9"/>
         <oasis:entry colname="col10">21</oasis:entry>
         <oasis:entry colname="col11"/>
         <oasis:entry colname="col12">30</oasis:entry>
         <oasis:entry colname="col13"/>
         <oasis:entry colname="col14">36</oasis:entry>
         <oasis:entry colname="col15">24</oasis:entry>
         <oasis:entry colname="col16">35</oasis:entry>
         <oasis:entry colname="col17"/>
         <oasis:entry colname="col18">31</oasis:entry>
         <oasis:entry colname="col19"/>
         <oasis:entry colname="col20">30</oasis:entry>
         <oasis:entry colname="col21">29</oasis:entry>
         <oasis:entry colname="col22"/>
         <oasis:entry colname="col23">55</oasis:entry>
         <oasis:entry colname="col24">50</oasis:entry>
         <oasis:entry colname="col25">55</oasis:entry>
         <oasis:entry colname="col26">30</oasis:entry>
         <oasis:entry colname="col27">17</oasis:entry>
         <oasis:entry colname="col28">0.95</oasis:entry>
         <oasis:entry colname="col29">1.62</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">278</oasis:entry>
         <oasis:entry colname="col2">11</oasis:entry>
         <oasis:entry colname="col3">9</oasis:entry>
         <oasis:entry colname="col4">13</oasis:entry>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6">9</oasis:entry>
         <oasis:entry colname="col7">17</oasis:entry>
         <oasis:entry colname="col8"/>
         <oasis:entry colname="col9">20</oasis:entry>
         <oasis:entry colname="col10">19</oasis:entry>
         <oasis:entry colname="col11">27</oasis:entry>
         <oasis:entry colname="col12"/>
         <oasis:entry colname="col13">20</oasis:entry>
         <oasis:entry colname="col14"/>
         <oasis:entry colname="col15">22</oasis:entry>
         <oasis:entry colname="col16">28</oasis:entry>
         <oasis:entry colname="col17"/>
         <oasis:entry colname="col18"/>
         <oasis:entry colname="col19"/>
         <oasis:entry colname="col20">37</oasis:entry>
         <oasis:entry colname="col21"/>
         <oasis:entry colname="col22">39</oasis:entry>
         <oasis:entry colname="col23">44</oasis:entry>
         <oasis:entry colname="col24"/>
         <oasis:entry colname="col25">52</oasis:entry>
         <oasis:entry colname="col26"/>
         <oasis:entry colname="col27">15</oasis:entry>
         <oasis:entry colname="col28">0.94</oasis:entry>
         <oasis:entry colname="col29">0.77</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">216</oasis:entry>
         <oasis:entry colname="col2">8</oasis:entry>
         <oasis:entry colname="col3">11</oasis:entry>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6"/>
         <oasis:entry colname="col7">15</oasis:entry>
         <oasis:entry colname="col8"/>
         <oasis:entry colname="col9">20</oasis:entry>
         <oasis:entry colname="col10">22</oasis:entry>
         <oasis:entry colname="col11"/>
         <oasis:entry colname="col12">20</oasis:entry>
         <oasis:entry colname="col13">17</oasis:entry>
         <oasis:entry colname="col14"/>
         <oasis:entry colname="col15">20</oasis:entry>
         <oasis:entry colname="col16">27</oasis:entry>
         <oasis:entry colname="col17"/>
         <oasis:entry colname="col18">31</oasis:entry>
         <oasis:entry colname="col19"/>
         <oasis:entry colname="col20">34</oasis:entry>
         <oasis:entry colname="col21">39</oasis:entry>
         <oasis:entry colname="col22">36</oasis:entry>
         <oasis:entry colname="col23"/>
         <oasis:entry colname="col24"/>
         <oasis:entry colname="col25">57</oasis:entry>
         <oasis:entry colname="col26"/>
         <oasis:entry colname="col27">14</oasis:entry>
         <oasis:entry colname="col28">0.91</oasis:entry>
         <oasis:entry colname="col29">0.51</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">249</oasis:entry>
         <oasis:entry colname="col2">7</oasis:entry>
         <oasis:entry colname="col3">10</oasis:entry>
         <oasis:entry colname="col4">11</oasis:entry>
         <oasis:entry colname="col5">9</oasis:entry>
         <oasis:entry colname="col6">14</oasis:entry>
         <oasis:entry colname="col7">15</oasis:entry>
         <oasis:entry colname="col8">21</oasis:entry>
         <oasis:entry colname="col9">18</oasis:entry>
         <oasis:entry colname="col10"/>
         <oasis:entry colname="col11">19</oasis:entry>
         <oasis:entry colname="col12">21</oasis:entry>
         <oasis:entry colname="col13">21</oasis:entry>
         <oasis:entry colname="col14">27</oasis:entry>
         <oasis:entry colname="col15">27</oasis:entry>
         <oasis:entry colname="col16">26</oasis:entry>
         <oasis:entry colname="col17"/>
         <oasis:entry colname="col18">26</oasis:entry>
         <oasis:entry colname="col19">27</oasis:entry>
         <oasis:entry colname="col20">34</oasis:entry>
         <oasis:entry colname="col21">41</oasis:entry>
         <oasis:entry colname="col22">35</oasis:entry>
         <oasis:entry colname="col23">45</oasis:entry>
         <oasis:entry colname="col24">42</oasis:entry>
         <oasis:entry colname="col25">42</oasis:entry>
         <oasis:entry colname="col26">54</oasis:entry>
         <oasis:entry colname="col27">23</oasis:entry>
         <oasis:entry colname="col28">0.88</oasis:entry>
         <oasis:entry colname="col29">0.68</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">246</oasis:entry>
         <oasis:entry colname="col2">9</oasis:entry>
         <oasis:entry colname="col3">10</oasis:entry>
         <oasis:entry colname="col4">10</oasis:entry>
         <oasis:entry colname="col5">16</oasis:entry>
         <oasis:entry colname="col6">10</oasis:entry>
         <oasis:entry colname="col7">15</oasis:entry>
         <oasis:entry colname="col8">18</oasis:entry>
         <oasis:entry colname="col9">16</oasis:entry>
         <oasis:entry colname="col10">21</oasis:entry>
         <oasis:entry colname="col11">17</oasis:entry>
         <oasis:entry colname="col12">22</oasis:entry>
         <oasis:entry colname="col13">20</oasis:entry>
         <oasis:entry colname="col14">24</oasis:entry>
         <oasis:entry colname="col15">21</oasis:entry>
         <oasis:entry colname="col16">28</oasis:entry>
         <oasis:entry colname="col17">29</oasis:entry>
         <oasis:entry colname="col18">25</oasis:entry>
         <oasis:entry colname="col19">30</oasis:entry>
         <oasis:entry colname="col20">37</oasis:entry>
         <oasis:entry colname="col21">36</oasis:entry>
         <oasis:entry colname="col22">29</oasis:entry>
         <oasis:entry colname="col23">46</oasis:entry>
         <oasis:entry colname="col24">42</oasis:entry>
         <oasis:entry colname="col25">46</oasis:entry>
         <oasis:entry colname="col26">58</oasis:entry>
         <oasis:entry colname="col27">25</oasis:entry>
         <oasis:entry colname="col28">0.88</oasis:entry>
         <oasis:entry colname="col29">0.70</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">241</oasis:entry>
         <oasis:entry colname="col2">7</oasis:entry>
         <oasis:entry colname="col3">10</oasis:entry>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6"/>
         <oasis:entry colname="col7">16</oasis:entry>
         <oasis:entry colname="col8">17</oasis:entry>
         <oasis:entry colname="col9">19</oasis:entry>
         <oasis:entry colname="col10"/>
         <oasis:entry colname="col11"/>
         <oasis:entry colname="col12"/>
         <oasis:entry colname="col13"/>
         <oasis:entry colname="col14"/>
         <oasis:entry colname="col15">26</oasis:entry>
         <oasis:entry colname="col16">27</oasis:entry>
         <oasis:entry colname="col17">26</oasis:entry>
         <oasis:entry colname="col18">28</oasis:entry>
         <oasis:entry colname="col19">30</oasis:entry>
         <oasis:entry colname="col20"/>
         <oasis:entry colname="col21">32</oasis:entry>
         <oasis:entry colname="col22">36</oasis:entry>
         <oasis:entry colname="col23"/>
         <oasis:entry colname="col24">36</oasis:entry>
         <oasis:entry colname="col25"/>
         <oasis:entry colname="col26">58</oasis:entry>
         <oasis:entry colname="col27">14</oasis:entry>
         <oasis:entry colname="col28">0.87</oasis:entry>
         <oasis:entry colname="col29">0.67</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1"><inline-formula><mml:math id="M41" display="inline"><mml:mi mathvariant="normal">⋮</mml:mi></mml:math></inline-formula></oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6"/>
         <oasis:entry colname="col7"/>
         <oasis:entry colname="col8"/>
         <oasis:entry colname="col9"/>
         <oasis:entry colname="col10"/>
         <oasis:entry colname="col11"/>
         <oasis:entry colname="col12"/>
         <oasis:entry colname="col13"/>
         <oasis:entry colname="col14"/>
         <oasis:entry colname="col15"/>
         <oasis:entry colname="col16"/>
         <oasis:entry colname="col17"/>
         <oasis:entry colname="col18"/>
         <oasis:entry colname="col19"/>
         <oasis:entry colname="col20"/>
         <oasis:entry colname="col21"/>
         <oasis:entry colname="col22"/>
         <oasis:entry colname="col23"/>
         <oasis:entry colname="col24"/>
         <oasis:entry colname="col25"/>
         <oasis:entry colname="col26"/>
         <oasis:entry colname="col27"/>
         <oasis:entry colname="col28"/>
         <oasis:entry colname="col29"/>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">262</oasis:entry>
         <oasis:entry colname="col2">6</oasis:entry>
         <oasis:entry colname="col3">7</oasis:entry>
         <oasis:entry colname="col4">7</oasis:entry>
         <oasis:entry colname="col5">8</oasis:entry>
         <oasis:entry colname="col6">4</oasis:entry>
         <oasis:entry colname="col7">15</oasis:entry>
         <oasis:entry colname="col8">7</oasis:entry>
         <oasis:entry colname="col9">9</oasis:entry>
         <oasis:entry colname="col10">12</oasis:entry>
         <oasis:entry colname="col11">14</oasis:entry>
         <oasis:entry colname="col12">8</oasis:entry>
         <oasis:entry colname="col13">17</oasis:entry>
         <oasis:entry colname="col14">9</oasis:entry>
         <oasis:entry colname="col15">13</oasis:entry>
         <oasis:entry colname="col16">3</oasis:entry>
         <oasis:entry colname="col17">17</oasis:entry>
         <oasis:entry colname="col18">11</oasis:entry>
         <oasis:entry colname="col19">18</oasis:entry>
         <oasis:entry colname="col20">14</oasis:entry>
         <oasis:entry colname="col21">17</oasis:entry>
         <oasis:entry colname="col22">7</oasis:entry>
         <oasis:entry colname="col23">15</oasis:entry>
         <oasis:entry colname="col24">23</oasis:entry>
         <oasis:entry colname="col25">6</oasis:entry>
         <oasis:entry colname="col26">15</oasis:entry>
         <oasis:entry colname="col27">25</oasis:entry>
         <oasis:entry colname="col28">0.39</oasis:entry>
         <oasis:entry colname="col29">1.13</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">266</oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">5</oasis:entry>
         <oasis:entry colname="col5">6</oasis:entry>
         <oasis:entry colname="col6"/>
         <oasis:entry colname="col7">9</oasis:entry>
         <oasis:entry colname="col8"/>
         <oasis:entry colname="col9"/>
         <oasis:entry colname="col10"/>
         <oasis:entry colname="col11">8</oasis:entry>
         <oasis:entry colname="col12"/>
         <oasis:entry colname="col13"/>
         <oasis:entry colname="col14">10</oasis:entry>
         <oasis:entry colname="col15"/>
         <oasis:entry colname="col16">14</oasis:entry>
         <oasis:entry colname="col17">11</oasis:entry>
         <oasis:entry colname="col18">13</oasis:entry>
         <oasis:entry colname="col19">11</oasis:entry>
         <oasis:entry colname="col20">14</oasis:entry>
         <oasis:entry colname="col21"/>
         <oasis:entry colname="col22">13</oasis:entry>
         <oasis:entry colname="col23"/>
         <oasis:entry colname="col24"/>
         <oasis:entry colname="col25">14</oasis:entry>
         <oasis:entry colname="col26">24</oasis:entry>
         <oasis:entry colname="col27">13</oasis:entry>
         <oasis:entry colname="col28">0.36</oasis:entry>
         <oasis:entry colname="col29">0.56</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">275</oasis:entry>
         <oasis:entry colname="col2">4</oasis:entry>
         <oasis:entry colname="col3">7</oasis:entry>
         <oasis:entry colname="col4">12</oasis:entry>
         <oasis:entry colname="col5">8</oasis:entry>
         <oasis:entry colname="col6">2</oasis:entry>
         <oasis:entry colname="col7">7</oasis:entry>
         <oasis:entry colname="col8">5</oasis:entry>
         <oasis:entry colname="col9">12</oasis:entry>
         <oasis:entry colname="col10">12</oasis:entry>
         <oasis:entry colname="col11">10</oasis:entry>
         <oasis:entry colname="col12">15</oasis:entry>
         <oasis:entry colname="col13">15</oasis:entry>
         <oasis:entry colname="col14">2</oasis:entry>
         <oasis:entry colname="col15">9</oasis:entry>
         <oasis:entry colname="col16">13</oasis:entry>
         <oasis:entry colname="col17">5</oasis:entry>
         <oasis:entry colname="col18">8</oasis:entry>
         <oasis:entry colname="col19">9</oasis:entry>
         <oasis:entry colname="col20">6</oasis:entry>
         <oasis:entry colname="col21">12</oasis:entry>
         <oasis:entry colname="col22">4</oasis:entry>
         <oasis:entry colname="col23">6</oasis:entry>
         <oasis:entry colname="col24">26</oasis:entry>
         <oasis:entry colname="col25">17</oasis:entry>
         <oasis:entry colname="col26">32</oasis:entry>
         <oasis:entry colname="col27">25</oasis:entry>
         <oasis:entry colname="col28">0.36</oasis:entry>
         <oasis:entry colname="col29">1.14</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">268</oasis:entry>
         <oasis:entry colname="col2">2</oasis:entry>
         <oasis:entry colname="col3">4</oasis:entry>
         <oasis:entry colname="col4">6</oasis:entry>
         <oasis:entry colname="col5">4</oasis:entry>
         <oasis:entry colname="col6">3</oasis:entry>
         <oasis:entry colname="col7">8</oasis:entry>
         <oasis:entry colname="col8">4</oasis:entry>
         <oasis:entry colname="col9">4</oasis:entry>
         <oasis:entry colname="col10">7</oasis:entry>
         <oasis:entry colname="col11">5</oasis:entry>
         <oasis:entry colname="col12">5</oasis:entry>
         <oasis:entry colname="col13">8</oasis:entry>
         <oasis:entry colname="col14">9</oasis:entry>
         <oasis:entry colname="col15">6</oasis:entry>
         <oasis:entry colname="col16">13</oasis:entry>
         <oasis:entry colname="col17">10</oasis:entry>
         <oasis:entry colname="col18">13</oasis:entry>
         <oasis:entry colname="col19">12</oasis:entry>
         <oasis:entry colname="col20">16</oasis:entry>
         <oasis:entry colname="col21">16</oasis:entry>
         <oasis:entry colname="col22">6</oasis:entry>
         <oasis:entry colname="col23">17</oasis:entry>
         <oasis:entry colname="col24">19</oasis:entry>
         <oasis:entry colname="col25">20</oasis:entry>
         <oasis:entry colname="col26">12</oasis:entry>
         <oasis:entry colname="col27">25</oasis:entry>
         <oasis:entry colname="col28">0.32</oasis:entry>
         <oasis:entry colname="col29">0.55</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">244</oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3">5</oasis:entry>
         <oasis:entry colname="col4">3</oasis:entry>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6">4</oasis:entry>
         <oasis:entry colname="col7"/>
         <oasis:entry colname="col8"/>
         <oasis:entry colname="col9"/>
         <oasis:entry colname="col10">6</oasis:entry>
         <oasis:entry colname="col11">12</oasis:entry>
         <oasis:entry colname="col12">6</oasis:entry>
         <oasis:entry colname="col13"/>
         <oasis:entry colname="col14"/>
         <oasis:entry colname="col15">4</oasis:entry>
         <oasis:entry colname="col16"/>
         <oasis:entry colname="col17">13</oasis:entry>
         <oasis:entry colname="col18"/>
         <oasis:entry colname="col19"/>
         <oasis:entry colname="col20"/>
         <oasis:entry colname="col21"/>
         <oasis:entry colname="col22">10</oasis:entry>
         <oasis:entry colname="col23">9</oasis:entry>
         <oasis:entry colname="col24"/>
         <oasis:entry colname="col25">23</oasis:entry>
         <oasis:entry colname="col26">17</oasis:entry>
         <oasis:entry colname="col27">12</oasis:entry>
         <oasis:entry colname="col28">0.30</oasis:entry>
         <oasis:entry colname="col29">0.65</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">232</oasis:entry>
         <oasis:entry colname="col2">4</oasis:entry>
         <oasis:entry colname="col3">4</oasis:entry>
         <oasis:entry colname="col4">5</oasis:entry>
         <oasis:entry colname="col5">6</oasis:entry>
         <oasis:entry colname="col6">2</oasis:entry>
         <oasis:entry colname="col7">6</oasis:entry>
         <oasis:entry colname="col8">4</oasis:entry>
         <oasis:entry colname="col9">4</oasis:entry>
         <oasis:entry colname="col10">6</oasis:entry>
         <oasis:entry colname="col11">8</oasis:entry>
         <oasis:entry colname="col12">7</oasis:entry>
         <oasis:entry colname="col13">6</oasis:entry>
         <oasis:entry colname="col14">8</oasis:entry>
         <oasis:entry colname="col15">10</oasis:entry>
         <oasis:entry colname="col16">10</oasis:entry>
         <oasis:entry colname="col17">13</oasis:entry>
         <oasis:entry colname="col18">8</oasis:entry>
         <oasis:entry colname="col19">10</oasis:entry>
         <oasis:entry colname="col20">7</oasis:entry>
         <oasis:entry colname="col21">7</oasis:entry>
         <oasis:entry colname="col22">14</oasis:entry>
         <oasis:entry colname="col23">12</oasis:entry>
         <oasis:entry colname="col24">18</oasis:entry>
         <oasis:entry colname="col25">17</oasis:entry>
         <oasis:entry colname="col26">17</oasis:entry>
         <oasis:entry colname="col27">25</oasis:entry>
         <oasis:entry colname="col28">0.29</oasis:entry>
         <oasis:entry colname="col29">0.46</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">283</oasis:entry>
         <oasis:entry colname="col2">3</oasis:entry>
         <oasis:entry colname="col3">5</oasis:entry>
         <oasis:entry colname="col4">5</oasis:entry>
         <oasis:entry colname="col5">6</oasis:entry>
         <oasis:entry colname="col6">0</oasis:entry>
         <oasis:entry colname="col7">15</oasis:entry>
         <oasis:entry colname="col8">8</oasis:entry>
         <oasis:entry colname="col9">5</oasis:entry>
         <oasis:entry colname="col10">6</oasis:entry>
         <oasis:entry colname="col11">5</oasis:entry>
         <oasis:entry colname="col12">6</oasis:entry>
         <oasis:entry colname="col13">5</oasis:entry>
         <oasis:entry colname="col14">5</oasis:entry>
         <oasis:entry colname="col15">8</oasis:entry>
         <oasis:entry colname="col16">5</oasis:entry>
         <oasis:entry colname="col17">4</oasis:entry>
         <oasis:entry colname="col18">10</oasis:entry>
         <oasis:entry colname="col19">6</oasis:entry>
         <oasis:entry colname="col20">5</oasis:entry>
         <oasis:entry colname="col21">5</oasis:entry>
         <oasis:entry colname="col22">5</oasis:entry>
         <oasis:entry colname="col23">8</oasis:entry>
         <oasis:entry colname="col24">6</oasis:entry>
         <oasis:entry colname="col25">9</oasis:entry>
         <oasis:entry colname="col26">6</oasis:entry>
         <oasis:entry colname="col27">25</oasis:entry>
         <oasis:entry colname="col28">0.21</oasis:entry>
         <oasis:entry colname="col29">0.88</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">228</oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">3</oasis:entry>
         <oasis:entry colname="col5">2</oasis:entry>
         <oasis:entry colname="col6"/>
         <oasis:entry colname="col7">4</oasis:entry>
         <oasis:entry colname="col8">4</oasis:entry>
         <oasis:entry colname="col9">3</oasis:entry>
         <oasis:entry colname="col10">4</oasis:entry>
         <oasis:entry colname="col11">4</oasis:entry>
         <oasis:entry colname="col12"/>
         <oasis:entry colname="col13">6</oasis:entry>
         <oasis:entry colname="col14">4</oasis:entry>
         <oasis:entry colname="col15">4</oasis:entry>
         <oasis:entry colname="col16"/>
         <oasis:entry colname="col17">6</oasis:entry>
         <oasis:entry colname="col18">4</oasis:entry>
         <oasis:entry colname="col19"/>
         <oasis:entry colname="col20">8</oasis:entry>
         <oasis:entry colname="col21">8</oasis:entry>
         <oasis:entry colname="col22">12</oasis:entry>
         <oasis:entry colname="col23">8</oasis:entry>
         <oasis:entry colname="col24">8</oasis:entry>
         <oasis:entry colname="col25"/>
         <oasis:entry colname="col26">6</oasis:entry>
         <oasis:entry colname="col27">18</oasis:entry>
         <oasis:entry colname="col28">0.18</oasis:entry>
         <oasis:entry colname="col29">0.30</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">253</oasis:entry>
         <oasis:entry colname="col2">1</oasis:entry>
         <oasis:entry colname="col3">1</oasis:entry>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6">2</oasis:entry>
         <oasis:entry colname="col7">5</oasis:entry>
         <oasis:entry colname="col8">2</oasis:entry>
         <oasis:entry colname="col9"/>
         <oasis:entry colname="col10"/>
         <oasis:entry colname="col11">6</oasis:entry>
         <oasis:entry colname="col12">4</oasis:entry>
         <oasis:entry colname="col13">2</oasis:entry>
         <oasis:entry colname="col14">3</oasis:entry>
         <oasis:entry colname="col15">3</oasis:entry>
         <oasis:entry colname="col16">3</oasis:entry>
         <oasis:entry colname="col17"/>
         <oasis:entry colname="col18">4</oasis:entry>
         <oasis:entry colname="col19">3</oasis:entry>
         <oasis:entry colname="col20"/>
         <oasis:entry colname="col21">7</oasis:entry>
         <oasis:entry colname="col22">5</oasis:entry>
         <oasis:entry colname="col23"/>
         <oasis:entry colname="col24">5</oasis:entry>
         <oasis:entry colname="col25"/>
         <oasis:entry colname="col26"/>
         <oasis:entry colname="col27">16</oasis:entry>
         <oasis:entry colname="col28">0.13</oasis:entry>
         <oasis:entry colname="col29">0.32</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">245</oasis:entry>
         <oasis:entry colname="col2">1</oasis:entry>
         <oasis:entry colname="col3">1</oasis:entry>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6">3</oasis:entry>
         <oasis:entry colname="col7">2</oasis:entry>
         <oasis:entry colname="col8">2</oasis:entry>
         <oasis:entry colname="col9">3</oasis:entry>
         <oasis:entry colname="col10">2</oasis:entry>
         <oasis:entry colname="col11">4</oasis:entry>
         <oasis:entry colname="col12"/>
         <oasis:entry colname="col13">1</oasis:entry>
         <oasis:entry colname="col14">4</oasis:entry>
         <oasis:entry colname="col15">0</oasis:entry>
         <oasis:entry colname="col16"/>
         <oasis:entry colname="col17">4</oasis:entry>
         <oasis:entry colname="col18">6</oasis:entry>
         <oasis:entry colname="col19">3</oasis:entry>
         <oasis:entry colname="col20">4</oasis:entry>
         <oasis:entry colname="col21">3</oasis:entry>
         <oasis:entry colname="col22">3</oasis:entry>
         <oasis:entry colname="col23">7</oasis:entry>
         <oasis:entry colname="col24"/>
         <oasis:entry colname="col25">4</oasis:entry>
         <oasis:entry colname="col26">5</oasis:entry>
         <oasis:entry colname="col27">20</oasis:entry>
         <oasis:entry colname="col28">0.10</oasis:entry>
         <oasis:entry colname="col29">0.28</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1"><inline-formula><mml:math id="M42" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">m</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>
         <oasis:entry colname="col2">0.89</oasis:entry>
         <oasis:entry colname="col3">0.80</oasis:entry>
         <oasis:entry colname="col4">0.82</oasis:entry>
         <oasis:entry colname="col5">0.75</oasis:entry>
         <oasis:entry colname="col6">0.57</oasis:entry>
         <oasis:entry colname="col7">0.86</oasis:entry>
         <oasis:entry colname="col8">0.78</oasis:entry>
         <oasis:entry colname="col9">0.79</oasis:entry>
         <oasis:entry colname="col10">0.62</oasis:entry>
         <oasis:entry colname="col11">0.71</oasis:entry>
         <oasis:entry colname="col12">0.73</oasis:entry>
         <oasis:entry colname="col13">0.68</oasis:entry>
         <oasis:entry colname="col14">0.64</oasis:entry>
         <oasis:entry colname="col15">0.62</oasis:entry>
         <oasis:entry colname="col16">0.70</oasis:entry>
         <oasis:entry colname="col17">0.64</oasis:entry>
         <oasis:entry colname="col18">0.61</oasis:entry>
         <oasis:entry colname="col19">0.63</oasis:entry>
         <oasis:entry colname="col20">0.64</oasis:entry>
         <oasis:entry colname="col21">0.50</oasis:entry>
         <oasis:entry colname="col22">0.43</oasis:entry>
         <oasis:entry colname="col23">0.56</oasis:entry>
         <oasis:entry colname="col24">0.54</oasis:entry>
         <oasis:entry colname="col25">0.44</oasis:entry>
         <oasis:entry colname="col26">0.57</oasis:entry>
         <oasis:entry colname="col27"/>
         <oasis:entry colname="col28"/>
         <oasis:entry colname="col29"/>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <p id="d2e3354">The raw counts for the 68 students are given in Table <xref ref-type="table" rid="T1"/> and Fig. <xref ref-type="fig" rid="F3"/>, for the same selection of 25 grains that were analysed by AC and PV in Sect. <xref ref-type="sec" rid="Ch1.S3"/>, along with corresponding counts made by PV. Everyone analysed the same ROIs. Variation between the mean values is to be expected because of the differing numbers of tracks due to varying areas and U contents of the grains. But the variation between counts within grains (shown by the standard deviations in Fig. <xref ref-type="fig" rid="F3"/>) is due entirely to differences between the students' recognising and counting exactly the same tracks. These standard deviations increase with the mean number of tracks and are considerable in size, being on average about 40 % of the mean. With expert trained counters one would expect much smaller differences between counts.  Furthermore, the vast majority of students counted fewer tracks than PV did, often many fewer, and on two occasions someone counted no tracks at all. PV's count is always above the students' median and nearly always above the upper quartile (Fig. <xref ref-type="fig" rid="F3"/>).</p>
      <p id="d2e3367">The rightmost three columns of Table <xref ref-type="table" rid="T1"/> contain summary statistics (<inline-formula><mml:math id="M43" display="inline"><mml:mrow><mml:msub><mml:mi>n</mml:mi><mml:mi mathvariant="normal">g</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula>, <inline-formula><mml:math id="M44" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math id="M45" display="inline"><mml:mrow><mml:msub><mml:mi>s</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula>) giving, for each student, the number of grains counted and the weighted mean and standard deviation of the ratios of the student's count to PV's count for each grain (definitions provided in the caption). The true number of tracks in each ROI is unknown, so we are comparing the students with PV (remembering that PV's count is also subject to error, which is the same for each student). <inline-formula><mml:math id="M46" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> measures agreement with PV on average and <inline-formula><mml:math id="M47" display="inline"><mml:mrow><mml:msub><mml:mi>s</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> measures consistency over grains. For good agreement <inline-formula><mml:math id="M48" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> should be close to 1 and <inline-formula><mml:math id="M49" display="inline"><mml:mrow><mml:msub><mml:mi>s</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula> should be small.  Perfect agreement is <inline-formula><mml:math id="M50" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math id="M51" display="inline"><mml:mrow><mml:msub><mml:mi>s</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">0</mml:mn></mml:mrow></mml:math></inline-formula>. For comparison, an <inline-formula><mml:math id="M52" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">1.04</mml:mn></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math id="M53" display="inline"><mml:mrow><mml:msub><mml:mi>s</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">0.69</mml:mn></mml:mrow></mml:math></inline-formula> is obtained for PV and AC using just the counts in the common areas <inline-formula><mml:math id="M54" display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mn mathvariant="normal">0</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> from Sect. <xref ref-type="sec" rid="Ch1.S3"/>. With the caveat that the ROIs are different and PV's counts are different, this calculation shows that there is a group of 6 (possibly 9) students whose agreement with PV is comparable with AC's. This group does not include student 229 whose <inline-formula><mml:math id="M55" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">0.95</mml:mn></mml:mrow></mml:math></inline-formula> but with a large <inline-formula><mml:math id="M56" display="inline"><mml:mrow><mml:msub><mml:mi>s</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mn mathvariant="normal">1.62</mml:mn></mml:mrow></mml:math></inline-formula>. Students near the bottom of Table <xref ref-type="table" rid="T1"/> have undercounted the samples by such a large degree that their work can be qualified as vandalism. Sect. <xref ref-type="sec" rid="Ch1.S7"/> will suggest strategies to detect and counteract this type of behaviour.</p>
      <p id="d2e3559">In spite of the under-counting by the students, the ratio of their pooled track counts (<inline-formula><mml:math id="M57" display="inline"><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi mathvariant="normal">p</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula>) for two different grains is often close to PV's ratio, especially when comparing grains with similar track densities. This is illustrated in Fig. <xref ref-type="fig" rid="F4"/>a for grains 23 and 25.  For any point, the ratio of the two counts is given by the slope of a line from the origin to that point. Although the individual slopes vary considerably, the line with slope equal to the ratio of the total counts for all students (which is 0.97) passes close to PV's pair of counts (52, 50) shown by the blue dot (with ratio 1.04). It is interesting that the students with lower counts are mostly above this line and those with higher counts are all below it. There is a positive correlation between the pairs of counts, consistent with systematic observer effects (i.e., people who count a low value in one grain tend to count similarly low in the other, and vice versa). Comparing other pairs of grains shows similar results, with correlations varying between 0.4 and 0.9.</p>

      <fig id="F3"><label>Figure 3</label><caption><p id="d2e3577">Strip chart of the data shown in Table <xref ref-type="table" rid="T1"/>, with the students' medians and PV's counts shown as yellow and blue triangles, respectively.</p></caption>
        <graphic xlink:href="https://gchron.copernicus.org/articles/8/109/2026/gchron-8-109-2026-f03.png"/>

      </fig>

      <p id="d2e3588">As mentioned in Sect. <xref ref-type="sec" rid="Ch1.S2"/>, geochron@home stores the actual track positions marked by the users. This raw data can be downloaded as a <monospace>.json</monospace> file and inspected in detail. Figure <xref ref-type="fig" rid="F4"/>b shows two-dimensional histograms for the <inline-formula><mml:math id="M58" display="inline"><mml:mi>x</mml:mi></mml:math></inline-formula>–<inline-formula><mml:math id="M59" display="inline"><mml:mi>y</mml:mi></mml:math></inline-formula> positions of all the track positions generated by the students in grains 23 and 25. Visual comparison of the histograms with the optical images confirms that the students unanimously identified the most obvious semitracks, which contain a clearly visible etch pit and tail. Shorter and fainter tracks received fewer clicks. Datasets like this can be used to replace integer counts of fission tracks with probabilities, reflecting the ambiguity of some fission track datasets. Figure <xref ref-type="fig" rid="F4"/> also shows that some students counted the tails of the fission tracks rather than their etch pits, despite being told the opposite in the tutorial. Fixing this issue will require some improvements to the tutorial pages (Sect. <xref ref-type="sec" rid="Ch1.S7"/>).</p>

      <fig id="F4" specific-use="star"><label>Figure 4</label><caption><p id="d2e3620"><bold>(a)</bold> The track counts for grain 23 plotted against those for grain 25, for 36 students who counted both of those grains. The grey line through the origin has slope 0.97, equal to the ratio of the students' total counts for each grain.  The blue dot shows PV's counts for those two grains. <bold>(b)</bold> Optical images in transmitted light of Mount Dromedary apatites 23 and 25 in the crowd-sourcing experiment, along with two-dimensional histogram of the track locations for the two grains, as identified by the citizen scientists.</p></caption>
        <graphic xlink:href="https://gchron.copernicus.org/articles/8/109/2026/gchron-8-109-2026-f04.png"/>

      </fig>

</sec>
<sec id="Ch1.S7">
  <label>7</label><title>Outlook</title>
      <p id="d2e3642">geochron@home has been in development for a decade and remains a work in progress. Planned improvements include:</p>
      <p id="d2e3645"><list list-type="order">
          <list-item>

      <p id="d2e3650">Length measurements. The geochron@home archive already contains horizontally confined fission track measurements <xref ref-type="bibr" rid="bib1.bibx15" id="paren.16"/>. However, these results must be generated externally (e.g., using Fission Track Studio) and uploaded via a <monospace>.json</monospace> file.  The virtual microscope currently lacks the functionality to generate length data within geochron@home. This functionality will be added in a future update.</p>
          </list-item>
          <list-item>

      <p id="d2e3662">Dpar and Dper. Etch pits are currently stored as simple sets of <inline-formula><mml:math id="M60" display="inline"><mml:mi>x</mml:mi></mml:math></inline-formula>- and <inline-formula><mml:math id="M61" display="inline"><mml:mi>y</mml:mi></mml:math></inline-formula>-coordinates.  In reality, etch pits have a finite length (“Dpar”) and width (“Dper”), which serve as useful indicators for the horizontal etch rates along the c-axis and parallel to it <xref ref-type="bibr" rid="bib1.bibx3" id="paren.17"/>. Functions will be added to measure and visualise this type of data in geochron@home.</p>
          </list-item>
          <list-item>

      <p id="d2e3685">Interactive tutorial pages and embedded quality control. Section <xref ref-type="sec" rid="Ch1.S6"/> shows that the crowd-sourcing idea is not yet ready for general use. Two improvements will be made to make its results more reliable. First, a “quiz” will be added to the tutorial pages to ensure that novice users do not count the tails but the etch pits of fission tracks. Only users who click on the “correct” features in an unlabelled set of images will be allowed to count new samples. Second, future citizen scientists will occasionally be served reference images of known track density. Their counts for these “test” images will be used to identify trustworthy analysts (top of Table <xref ref-type="table" rid="T1"/>) and flag unreliable ones (bottom of Table <xref ref-type="table" rid="T1"/>).</p>
          </list-item>
          <list-item>

      <p id="d2e3697">Machine learning. Data science is experiencing an artificial intelligence (AI) revolution that has already started to transform the fission track method <xref ref-type="bibr" rid="bib1.bibx12 bib1.bibx9 bib1.bibx2" id="paren.18"/>.  Convolutional neural networks must be trained with example data. geochron@home is ideally suited for this task. Sect. <xref ref-type="sec" rid="Ch1.S6"/> showed how the opinion of multiple fission track analysts can be combined to label fission track images with probabilities rather than counts. This data format is close to the form in which data are treated within an AI algorithm.</p>
          </list-item>
          <list-item>

      <p id="d2e3708">Inverse counting. Once trained on historical data, AI algorithms can be used to count fission tracks automatically. Following the model of Fission Track Studio <xref ref-type="bibr" rid="bib1.bibx6 bib1.bibx5" id="paren.19"/>, machine learning can be used to reverse the fission track counting process. Instead of asking users to count the fission tracks in a sample, the software can ask them to check the results proposed by an AI algorithm, and to remove any features that are <italic>not</italic> fission tracks.  Regardless of whether fission tracks were counted manually or with a machine, the value of the geochron@home archive remains the same. It is important to document data so that samples can be reanalysed in the future, for example when a new and improved generation of machine learning algorithms becomes available.</p>
          </list-item>
        </list></p>
      <p id="d2e3719">These improvements will be made by ourselves pending additional funding. However, because geochron@home is free and open software, we invite any interested parties to join the effort and extend or improve our code.</p>
</sec>
<sec id="Ch1.S8" sec-type="conclusions">
  <label>8</label><title>Conclusions</title>
      <p id="d2e3730">This paper introduced geochron@home, a software platform for FAIR fission track analysis. We demonstrated four different applications of this platform using real data. Putting the FAIR data paradigm into practice, all the imagery, counts and source code for this paper are publicly available on the geochron@home archive. Using these resources, the reader can reproduce all the results that were presented in this publication.  We encourage other geochronologists to follow this example.  FAIR workflows promise to address the reproducibility crisis in science <xref ref-type="bibr" rid="bib1.bibx11" id="paren.20"/>.</p>
      <p id="d2e3736">Increased transparency will also introduce new challenges. As FAIR data practices become more widespread, the fission track community will need to define how extensively reviewers are expected to re-examine primary imagery and what level of discrepancy constitutes sufficient grounds for rejecting or disputing raw counts. Although these issues are beyond the scope of the present paper, they will require community-wide discussion as FAIR data reporting and review become more widely adopted.</p>
      <p id="d2e3739">geochron@home's rich archive of raw data can be reanalysed in the future. We anticipate that the adoption of FAIR data processing workflows will open up new research opportunities. For example, archived pairs of peer-reviewed fission track images and counts could be used to train the next generation of automated machine learning algorithms. Conversely, it is also possible that future improvements in fission track images analysis will be used to update the count data for published datasets, improving their accuracy.</p>
      <p id="d2e3742">Another advantage of the geochron@home workflow is the clear separation between image acquisition and image analysis. This separation lowers the hardware requirements for fission track geochronology and enables resource sharing. Because state-of-the-art digital microscopes are expensive, geochron@home makes it possible to envision a model in which sample preparation and scanning are outsourced to a centralized facility, while individual scientists analyze their own data online. In this way, a single microscope could serve multiple laboratories, making fission track analysis more accessible and affordable.</p>
      <p id="d2e3746">The fission track method has always been a test bed for new geochronological developments.  Because fission track data are imprecise, the fission track community has solicited the help of statisticians and mathematicians to develop its analytical protocols. Other geochronological communities are still catching up with concepts and tools such as overdispersion, mixture modelling and radial plots, which have been commonplace in fission track analysis for decades <xref ref-type="bibr" rid="bib1.bibx18" id="paren.21"/>. In a similar vein, the subjective nature of fission track identification has prompted the fission track community to organise inter-laboratory comparisons and round-robin studies long before other geochronological communities <xref ref-type="bibr" rid="bib1.bibx10 bib1.bibx15" id="paren.22"/>.</p>
      <p id="d2e3755">With the development of geochron@home, fission track thermochronology is once again ahead of the pack in terms of FAIR data analysis. geochron@home currently only stores images and counts. This is enough to reproduce the results of fission track studies using the external detector method, but not for LA-ICP-MS based data. FAIR data processing of LA-ICP-MS data requires a new generation of mass spectrometer data reduction software.  The development of such FAIR ICP-MS data pipelines will not only benefit fission track analysis but other chronometers as well, such as in-situ U–Pb, Rb–Sr and Lu–Hf.</p>
      <p id="d2e3758">With the establishment of FAIR data, geochronology will be well placed to avoid the reproducibility problems that have plagued other fields of science.</p>
</sec>

      
      </body>
    <back><notes notes-type="codedataavailability"><title>Code and data availability</title>

      <p id="d2e3765">geochron@home is free software released under the GPL-3 license. The package and its source code are available from <uri>https://github.com/pvermees/geochron-at-home</uri> (last access: 15 January 2026; DOI: <ext-link xlink:href="https://doi.org/10.5281/zenodo.18166196" ext-link-type="DOI">10.5281/zenodo.18166196</ext-link>, <xref ref-type="bibr" rid="bib1.bibx21" id="altparen.23"/>).  The raw data (imagery) are available at the geochron@home archive (<uri>https://github.com/pvermees/GaHa</uri>, last access: 15 January 2026; DOI: <ext-link xlink:href="https://doi.org/10.5281/zenodo.18672351" ext-link-type="DOI">10.5281/zenodo.18672351</ext-link>, <xref ref-type="bibr" rid="bib1.bibx19" id="altparen.24"/>).  R-scripts to reproduce the figures are provided in the supplementary information (<uri>https://github.com/pvermees/supplements</uri>, last access: 15 January 2026; DOI: <ext-link xlink:href="https://doi.org/10.5281/zenodo.18672428" ext-link-type="DOI">10.5281/zenodo.18672428</ext-link>, <xref ref-type="bibr" rid="bib1.bibx20" id="altparen.25"/>).</p>
  </notes><notes notes-type="authorcontribution"><title>Author contributions</title>

      <p id="d2e3799">PV designed the study, acquired the funding and counted fission tracks. JH created geochron@home. TB expanded geochron@home and wrote the accompanying microscope image acquisition software. RG derived Eq. (<xref ref-type="disp-formula" rid="Ch1.E1"/>), designed Table <xref ref-type="table" rid="T1"/> and verified the other calculations. AC provided the samples, prepared the training data and counted fission tracks. PV and RG wrote the paper with input from the other authors.</p>
  </notes><notes notes-type="competinginterests"><title>Competing interests</title>

      <p id="d2e3809">At least one of the (co-)authors is a member of the editorial board of <italic>Geochronology</italic>. The peer-review process was guided by an independent editor, and the authors also have no other competing interests to declare.</p>
  </notes><notes notes-type="disclaimer"><title>Disclaimer</title>

      <p id="d2e3819">Publisher's note: Copernicus Publications remains neutral with regard to jurisdictional claims made in the text, published maps, institutional affiliations, or any other geographical representation in this paper. The authors bear the ultimate responsibility for providing appropriate place names. Views expressed in the text are those of the authors and do not necessarily reflect the views of the publisher.</p>
  </notes><notes notes-type="sistatement"><title>Special issue statement</title>

      <p id="d2e3825">This article is part of the special issue “Recent developments in thermochronology”.</p>
  </notes><ack><title>Acknowledgements</title><p id="d2e3831">We would like to thank Murat Tamer and Ling Chung for their detailed and constructive reviews, and the students of GEOL0017 (“Isotope Geology”) for their contribution to the crowd-sourcing experiment of Sect. <xref ref-type="sec" rid="Ch1.S6"/>.</p></ack><notes notes-type="financialsupport"><title>Financial support</title>

      <p id="d2e3838">This research has been supported by the Natural Environment Research Council (grant no. NE/T001518/1).</p>
  </notes><notes notes-type="reviewstatement"><title>Review statement</title>

      <p id="d2e3844">This paper was edited by Shigeru Sueoka and reviewed by Murat Taner Tamer and Ling Chung.</p>
  </notes><ref-list>
    <title>References</title>

      <ref id="bib1.bibx1"><label>Abbott et al.(2016)</label><mixed-citation>Abbott, B. P., Abbott, R., Abbott, T. D., et al.: Observation of gravitational waves from a binary black hole merger, Physical Review Letters, 116, 061102, <ext-link xlink:href="https://doi.org/10.1103/PhysRevLett.116.061102" ext-link-type="DOI">10.1103/PhysRevLett.116.061102</ext-link>, 2016.</mixed-citation></ref>
      <ref id="bib1.bibx2"><label>Boone et al.(2025)Boone, Chung, Faux, Nattala, Church, Jiang, McMillan, Jones, Liu, Jiang, Ehinger, Drummond, Kohn, and Gleadow</label><mixed-citation>Boone, S. C., Chung, L., Faux, N., Nattala, U., Church, T., Jiang, C., McMillan, M., Jones, S., Liu, D., Jiang, H., Ehinger, K., Drummond, T., Kohn, B., and Gleadow, A.: Raising the Bar: Deep Learning on Comprehensive Database Sets New Benchmark for Automated Fission-Track Detection, Computers &amp; Geosciences, 208, 106096, <ext-link xlink:href="https://doi.org/10.1016/j.cageo.2025.106096" ext-link-type="DOI">10.1016/j.cageo.2025.106096</ext-link>, 2025.</mixed-citation></ref>
      <ref id="bib1.bibx3"><label>Donelick(1993)</label><mixed-citation> Donelick, R. A.: Method of fission track analysis utilizing bulk chemical etching of apatite, US Patent 5,267,274, 1993.</mixed-citation></ref>
      <ref id="bib1.bibx4"><label>Galton(1907)</label><mixed-citation>Galton, F.: Vox Populi, Nature, 75, 450–451, <ext-link xlink:href="https://doi.org/10.1038/075450a0" ext-link-type="DOI">10.1038/075450a0</ext-link>, 1907.</mixed-citation></ref>
      <ref id="bib1.bibx5"><label>Gleadow(2019)</label><mixed-citation>Gleadow, A.: Future developments in fission track thermochronology, in: Fission track thermochronology and its application to geology, edited by: Malusà, Marco and Fitzgerald, P., chap. 4, Springer, <ext-link xlink:href="https://doi.org/10.1007/978-3-319-89421-8_4" ext-link-type="DOI">10.1007/978-3-319-89421-8_4</ext-link>, 2019.</mixed-citation></ref>
      <ref id="bib1.bibx6"><label>Gleadow et al.(2009)Gleadow, Gleadow, Belton, Kohn, Krochmal, and Brown</label><mixed-citation>Gleadow, A. J., Gleadow, S. J., Belton, D. X., Kohn, B. P., Krochmal, M. S., and Brown, R. W.: Coincidence mapping – a key strategy for the automatic counting of fission tracks in natural minerals, Geological Society, London, Special Publications, 324, 25–36, <ext-link xlink:href="https://doi.org/10.1144/SP324.2" ext-link-type="DOI">10.1144/SP324.2</ext-link>, 2009.</mixed-citation></ref>
      <ref id="bib1.bibx7"><label>Green(1985)</label><mixed-citation>Green, P.: Comparison of zeta calibration baselines for fission-track dating of apatite, zircon and sphene, Chemical Geology: Isotope Geoscience Section, 58, 1–22, <ext-link xlink:href="https://doi.org/10.1016/0168-9622(85)90023-5" ext-link-type="DOI">10.1016/0168-9622(85)90023-5</ext-link>, 1985.</mixed-citation></ref>
      <ref id="bib1.bibx8"><label>Guo et al.(2025)Guo, Zhang, Lease, Malusà, Chew, Lu, Wu, Xiang, Wang, Grasemann, and Xiao</label><mixed-citation>Guo, C., Zhang, Z., Lease, R., Malusà, M. G., Chew, D., Lu, H., Wu, L., Xiang, D., Wang, N., Grasemann, B., and Xiao, W.: Apatite geo-thermochronology and geochemistry constrain oligocene-miocene growth and geodynamics of the northeastern Tibetan Plateau, Geophysical Research Letters, 52, e2024GL113157, <ext-link xlink:href="https://doi.org/10.1029/2024GL113157" ext-link-type="DOI">10.1029/2024GL113157</ext-link>, 2025.</mixed-citation></ref>
      <ref id="bib1.bibx9"><label>Li et al.(2022)Li, Xu, Su, and Yang</label><mixed-citation>Li, R., Xu, Z., Su, C., and Yang, R.: Automatic identification of semi-tracks on apatite and mica using a deep learning method, Computers &amp; Geosciences, 162, 105081, <ext-link xlink:href="https://doi.org/10.1016/j.cageo.2022.105081" ext-link-type="DOI">10.1016/j.cageo.2022.105081</ext-link>, 2022.</mixed-citation></ref>
      <ref id="bib1.bibx10"><label>Miller et al.(1985)Miller, Duddy, Green, Hurford, and Naeser</label><mixed-citation>Miller, D. S., Duddy, I. R., Green, P. F., Hurford, A. J., and Naeser, C. W.: Results of interlaboratory comparison of fission-track age standards: fission-track workshop – 1984, Nuclear Tracks and Radiation Measurements, 10, 383–391, <ext-link xlink:href="https://doi.org/10.1016/0735-245X(85)90127-9" ext-link-type="DOI">10.1016/0735-245X(85)90127-9</ext-link>, 1985.</mixed-citation></ref>
      <ref id="bib1.bibx11"><label>Miyakawa(2020)</label><mixed-citation>Miyakawa, T.: No raw data, no science: another possible source of the reproducibility crisis, Molecular Brain, 13, <ext-link xlink:href="https://doi.org/10.1186/s13041-020-0552-2" ext-link-type="DOI">10.1186/s13041-020-0552-2</ext-link>, 2020.</mixed-citation></ref>
      <ref id="bib1.bibx12"><label>Nachtergaele and De Grave(2021)</label><mixed-citation>Nachtergaele, S. and De Grave, J.: AI-Track-tive: open-source software for automated recognition and counting of surface semi-tracks using computer vision (artificial intelligence), Geochronology, 3, 383–394, <ext-link xlink:href="https://doi.org/10.5194/gchron-3-383-2021" ext-link-type="DOI">10.5194/gchron-3-383-2021</ext-link>, 2021.</mixed-citation></ref>
      <ref id="bib1.bibx13"><label>Ren et al.(2023)Ren, Li, Xiao, Yang, and Wang</label><mixed-citation>Ren, Z., Li, S., Xiao, P., Yang, X., and Wang, H.: Artificial intelligent identification of apatite fission tracks based on machine learning, Machine Learning: Science and Technology, 4, 045039, <ext-link xlink:href="https://doi.org/10.1088/2632-2153/ad0e17" ext-link-type="DOI">10.1088/2632-2153/ad0e17</ext-link>, 2023.</mixed-citation></ref>
      <ref id="bib1.bibx14"><label>Still(2006)</label><mixed-citation> Still, M.: The Definitive Guide to ImageMagick, 1st edn., Springer, ISBN 978-1-59059-590-9, 2006.</mixed-citation></ref>
      <ref id="bib1.bibx15"><label>Tamer et al.(2025)Tamer, Chung, Ketcham, and Gleadow</label><mixed-citation>Tamer, M. T., Chung, L., Ketcham, R. A., and Gleadow, A. J. W.: The need for fission-track data transparency and sharing, Geochronology, 7, 45–58, <ext-link xlink:href="https://doi.org/10.5194/gchron-7-45-2025" ext-link-type="DOI">10.5194/gchron-7-45-2025</ext-link>, 2025.</mixed-citation></ref>
      <ref id="bib1.bibx16"><label>Van Ranst et al.(2020)Van Ranst, Baert, Fernandes, and De Grave</label><mixed-citation>Van Ranst, G., Baert, P., Fernandes, A. C., and De Grave, J.: Technical note: Nikon–TRACKFlow, a new versatile microscope system for fission track analysis, Geochronology, 2, 93–99, <ext-link xlink:href="https://doi.org/10.5194/gchron-2-93-2020" ext-link-type="DOI">10.5194/gchron-2-93-2020</ext-link>, 2020. </mixed-citation></ref>
      <ref id="bib1.bibx17"><label>Vermeesch(2018a)</label><mixed-citation>Vermeesch, P.: <monospace>IsoplotR</monospace>: a free and open toolbox for geochronology, Geoscience Frontiers, 9, 1479–1493, <ext-link xlink:href="https://doi.org/10.1016/j.gsf.2018.04.001" ext-link-type="DOI">10.1016/j.gsf.2018.04.001</ext-link>, 2018a.</mixed-citation></ref>
      <ref id="bib1.bibx18"><label>Vermeesch(2018b)</label><mixed-citation>Vermeesch, P.: Statistics for fission-track thermochronology, in: Fission track thermochronology and its application to geology, edited by: Malusá, M. and Fitzgerald, P., chap. 6, Springer, <ext-link xlink:href="https://doi.org/10.1007/978-3-319-89421-8_6" ext-link-type="DOI">10.1007/978-3-319-89421-8_6</ext-link>, 2018b.</mixed-citation></ref>
      <ref id="bib1.bibx19"><label>Vermeesch(2026a)</label><mixed-citation>Vermeesch, P.: pvermees/GaHa: v.2, Zenodo [data set], <ext-link xlink:href="https://doi.org/10.5281/zenodo.18672351" ext-link-type="DOI">10.5281/zenodo.18672351</ext-link>, 2026a.</mixed-citation></ref>
      <ref id="bib1.bibx20"><label>Vermeesch et al.(2026b)</label><mixed-citation>Vermeesch, P.: pvermees/supplements/geochron@home, Zenodo [data set], <ext-link xlink:href="https://doi.org/10.5281/zenodo.18672428" ext-link-type="DOI">10.5281/zenodo.18672428</ext-link>, 2026b.</mixed-citation></ref>
      <ref id="bib1.bibx21"><label>Vermeesch et al.(2026)</label><mixed-citation>Vermeesch, P., Band, T., and He, J.: pvermees/geochron-at-home: 1.0, Zenodo [software], <ext-link xlink:href="https://doi.org/10.5281/zenodo.18166196" ext-link-type="DOI">10.5281/zenodo.18166196</ext-link>, 2026.</mixed-citation></ref>
      <ref id="bib1.bibx22"><label>Wilkinson et al.(2016)</label><mixed-citation>Wilkinson, M. D., Dumontier, M., Aalbersberg, I. J., et al.: The FAIR Guiding Principles for scientific data management and stewardship, Scientific data, 3, 1–9, <ext-link xlink:href="https://doi.org/10.1038/sdata.2016.18" ext-link-type="DOI">10.1038/sdata.2016.18</ext-link>, 2016.</mixed-citation></ref>

  </ref-list></back>
    <!--<article-title-html>FAIR fission track analysis with geochron@home</article-title-html>
<abstract-html/>
<ref-html id="bib1.bib1"><label>Abbott et al.(2016)</label><mixed-citation>
      
Abbott, B. P., Abbott, R., Abbott, T. D., et al.:
Observation of gravitational waves from a binary black hole merger, Physical
Review Letters, 116, 061102, <a href="https://doi.org/10.1103/PhysRevLett.116.061102" target="_blank">https://doi.org/10.1103/PhysRevLett.116.061102</a>, 2016.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib2"><label>Boone et al.(2025)Boone, Chung, Faux, Nattala, Church, Jiang,
McMillan, Jones, Liu, Jiang, Ehinger, Drummond, Kohn, and
Gleadow</label><mixed-citation>
      
Boone, S. C., Chung, L., Faux, N., Nattala, U., Church, T., Jiang, C.,
McMillan, M., Jones, S., Liu, D., Jiang, H., Ehinger, K., Drummond, T., Kohn,
B., and Gleadow, A.: Raising the Bar: Deep Learning on Comprehensive Database
Sets New Benchmark for Automated Fission-Track Detection, Computers &amp;
Geosciences, 208, 106096, <a href="https://doi.org/10.1016/j.cageo.2025.106096" target="_blank">https://doi.org/10.1016/j.cageo.2025.106096</a>, 2025.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib3"><label>Donelick(1993)</label><mixed-citation>
      
Donelick, R. A.: Method of fission track analysis utilizing bulk chemical
etching of apatite, US Patent 5,267,274, 1993.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib4"><label>Galton(1907)</label><mixed-citation>
      
Galton, F.: Vox Populi, Nature, 75, 450–451, <a href="https://doi.org/10.1038/075450a0" target="_blank">https://doi.org/10.1038/075450a0</a>, 1907.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib5"><label>Gleadow(2019)</label><mixed-citation>
      
Gleadow, A.: Future developments in fission track thermochronology, in:
Fission track thermochronology and its application to geology, edited by:
Malusà, Marco and Fitzgerald, P., chap. 4, Springer,
<a href="https://doi.org/10.1007/978-3-319-89421-8_4" target="_blank">https://doi.org/10.1007/978-3-319-89421-8_4</a>, 2019.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib6"><label>Gleadow et al.(2009)Gleadow, Gleadow, Belton, Kohn, Krochmal, and
Brown</label><mixed-citation>
      
Gleadow, A. J., Gleadow, S. J., Belton, D. X., Kohn, B. P., Krochmal, M. S.,
and Brown, R. W.: Coincidence mapping – a key strategy for the automatic
counting of fission tracks in natural minerals, Geological Society, London,
Special Publications, 324, 25–36, <a href="https://doi.org/10.1144/SP324.2" target="_blank">https://doi.org/10.1144/SP324.2</a>, 2009.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib7"><label>Green(1985)</label><mixed-citation>
      
Green, P.: Comparison of zeta calibration baselines for fission-track dating of
apatite, zircon and sphene, Chemical Geology: Isotope Geoscience Section, 58,
1–22, <a href="https://doi.org/10.1016/0168-9622(85)90023-5" target="_blank">https://doi.org/10.1016/0168-9622(85)90023-5</a>, 1985.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib8"><label>Guo et al.(2025)Guo, Zhang, Lease, Malusà, Chew, Lu, Wu, Xiang,
Wang, Grasemann, and Xiao</label><mixed-citation>
      
Guo, C., Zhang, Z., Lease, R., Malusà, M. G., Chew, D., Lu, H., Wu, L.,
Xiang, D., Wang, N., Grasemann, B., and Xiao, W.: Apatite
geo-thermochronology and geochemistry constrain oligocene-miocene growth and
geodynamics of the northeastern Tibetan Plateau, Geophysical Research
Letters, 52, e2024GL113157, <a href="https://doi.org/10.1029/2024GL113157" target="_blank">https://doi.org/10.1029/2024GL113157</a>,
2025.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib9"><label>Li et al.(2022)Li, Xu, Su, and Yang</label><mixed-citation>
      
Li, R., Xu, Z., Su, C., and Yang, R.: Automatic identification of semi-tracks
on apatite and mica using a deep learning method, Computers &amp; Geosciences,
162, 105081, <a href="https://doi.org/10.1016/j.cageo.2022.105081" target="_blank">https://doi.org/10.1016/j.cageo.2022.105081</a>, 2022.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib10"><label>Miller et al.(1985)Miller, Duddy, Green, Hurford, and
Naeser</label><mixed-citation>
      
Miller, D. S., Duddy, I. R., Green, P. F., Hurford, A. J., and Naeser, C. W.:
Results of interlaboratory comparison of fission-track age standards:
fission-track workshop – 1984, Nuclear Tracks and Radiation Measurements,
10, 383–391, <a href="https://doi.org/10.1016/0735-245X(85)90127-9" target="_blank">https://doi.org/10.1016/0735-245X(85)90127-9</a>, 1985.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib11"><label>Miyakawa(2020)</label><mixed-citation>
      
Miyakawa, T.: No raw data, no science: another possible source of the
reproducibility crisis, Molecular Brain, 13, <a href="https://doi.org/10.1186/s13041-020-0552-2" target="_blank">https://doi.org/10.1186/s13041-020-0552-2</a>, 2020.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib12"><label>Nachtergaele and De Grave(2021)</label><mixed-citation>
      
Nachtergaele, S. and De Grave, J.: AI-Track-tive: open-source software for automated recognition and counting of surface semi-tracks using computer vision (artificial intelligence), Geochronology, 3, 383–394, <a href="https://doi.org/10.5194/gchron-3-383-2021" target="_blank">https://doi.org/10.5194/gchron-3-383-2021</a>, 2021.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib13"><label>Ren et al.(2023)Ren, Li, Xiao, Yang, and Wang</label><mixed-citation>
      
Ren, Z., Li, S., Xiao, P., Yang, X., and Wang, H.: Artificial intelligent
identification of apatite fission tracks based on machine learning, Machine
Learning: Science and Technology, 4, 045039,
<a href="https://doi.org/10.1088/2632-2153/ad0e17" target="_blank">https://doi.org/10.1088/2632-2153/ad0e17</a>, 2023.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib14"><label>Still(2006)</label><mixed-citation>
      
Still, M.: The Definitive Guide to ImageMagick,
1st edn., Springer, ISBN 978-1-59059-590-9, 2006.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib15"><label>Tamer et al.(2025)Tamer, Chung, Ketcham, and Gleadow</label><mixed-citation>
      
Tamer, M. T., Chung, L., Ketcham, R. A., and Gleadow, A. J. W.: The need for fission-track data transparency and sharing, Geochronology, 7, 45–58, <a href="https://doi.org/10.5194/gchron-7-45-2025" target="_blank">https://doi.org/10.5194/gchron-7-45-2025</a>, 2025.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib16"><label>Van Ranst et al.(2020)Van Ranst, Baert, Fernandes, and
De Grave</label><mixed-citation>
      
Van Ranst, G., Baert, P., Fernandes, A. C., and De Grave, J.: Technical note: Nikon–TRACKFlow, a new versatile microscope system for fission track analysis, Geochronology, 2, 93–99, <a href="https://doi.org/10.5194/gchron-2-93-2020" target="_blank">https://doi.org/10.5194/gchron-2-93-2020</a>, 2020.


    </mixed-citation></ref-html>
<ref-html id="bib1.bib17"><label>Vermeesch(2018a)</label><mixed-citation>
      
Vermeesch, P.: <span style="" class="text typewriter">IsoplotR</span>: a free and open toolbox for geochronology,
Geoscience Frontiers, 9, 1479–1493, <a href="https://doi.org/10.1016/j.gsf.2018.04.001" target="_blank">https://doi.org/10.1016/j.gsf.2018.04.001</a>,
2018a.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib18"><label>Vermeesch(2018b)</label><mixed-citation>
      
Vermeesch, P.: Statistics for fission-track thermochronology, in: Fission track
thermochronology and its application to geology, edited by: Malusá, M. and
Fitzgerald, P., chap. 6, Springer, <a href="https://doi.org/10.1007/978-3-319-89421-8_6" target="_blank">https://doi.org/10.1007/978-3-319-89421-8_6</a>,
2018b.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib19"><label>Vermeesch(2026a)</label><mixed-citation>
      
Vermeesch, P.: pvermees/GaHa: v.2, Zenodo [data set],
<a href="https://doi.org/10.5281/zenodo.18672351" target="_blank">https://doi.org/10.5281/zenodo.18672351</a>, 2026a.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib20"><label>Vermeesch et al.(2026b)</label><mixed-citation>
      
Vermeesch, P.: pvermees/supplements/geochron@home, Zenodo [data set], <a href="https://doi.org/10.5281/zenodo.18672428" target="_blank">https://doi.org/10.5281/zenodo.18672428</a>, 2026b.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib21"><label>Vermeesch et al.(2026)</label><mixed-citation>
      
Vermeesch, P., Band, T., and He, J.: pvermees/geochron-at-home: 1.0, Zenodo [software],
<a href="https://doi.org/10.5281/zenodo.18166196" target="_blank">https://doi.org/10.5281/zenodo.18166196</a>, 2026.

    </mixed-citation></ref-html>
<ref-html id="bib1.bib22"><label>Wilkinson et al.(2016)</label><mixed-citation>
      
Wilkinson, M. D., Dumontier, M., Aalbersberg, I. J., et al.: The FAIR Guiding Principles for scientific
data management and stewardship, Scientific data, 3, 1–9,
<a href="https://doi.org/10.1038/sdata.2016.18" target="_blank">https://doi.org/10.1038/sdata.2016.18</a>, 2016.

    </mixed-citation></ref-html>--></article>
