The record

A project records where its data came from and how every result was made, so that a methods section can be written from it and the results made again. This page says what is kept, and where.

The project

The project saves itself to the library as you work; Open a saved project (⇧⌘O) lists them. Undo and redo cover every change. History and log (the status bar, or ⌘J) lists what was done to the project, and the session's messages. A project records its datasets by their files' paths and fingerprints, never the data themselves; their annotation, filters and definitions; and the results kept.

Results and jobs

Each analysis runs as a job in the program, shown in the Jobs view with its progress and log; a job that a stop interrupted can be resumed. Its result is kept as an artifact with its lineage: the dataset it was made from, the definition, filter and settings (with their defaults written out), the method and its version, the seed, ClonoLoom's version, and the SHA-256 of every file. The artifact's ID is made from what it measured, so asking again answers the kept result, and changing anything makes another.

Every release saves a project with its data and results, and every later release must open it and make its results again, with the same IDs and values. Results are the same, bit for bit, on every processor: a result made on a Mac with Apple silicon is the same file on an Intel Linux server.

The methods paragraph

A methods paragraph with numbered references, ready to copyA methods paragraph with numbered references, ready to copy
A dataset's methods paragraph, with its references.

Methods paragraph (a dataset's menu or the inspector) writes a paragraph for a manuscript from the project's record: the data's source and license, how ClonoLoom read and checked them, the unit, a table's mapped columns, the filter with what it kept, the clonotype definition, the diversity measured, the rarefaction and the levels the samples were compared at, the genes and junctions counted, the overlap measured, B-cell family thresholds, reference hashes, mutation denominators, lineage uncertainty, observed isotypes, and ClonoLoom's version, with numbered references. Only what was done is said, and the same record gives the same text. Copy takes it with its references.

Where things are kept

WhatmacOSLinuxWindows
The library: projects, results, jobs, example data~/Library/Application Support/ClonoLoom~/.config/ClonoLoom%AppData%\ClonoLoom
The cache of tables read~/Library/Caches/clonoloom~/.cache/clonoloom%LocalAppData%\clonoloom

--data-dir, --examples-dir and --cache-dir put them elsewhere. Your repertoire files are never copied into the library, moved or changed: projects refer to them where they are. Deleted projects are first moved to the library's trash folder. The cache stays within 10 GB (--cache-limit), removing what was used least recently, and can be deleted at any time; the Jobs view shows it and clears it.