ConductScience Open Field Test Analyzer: method and validation record
The calculation behind ConductScience's free open field test analyzer, with three worked examples that check it.
ConductScience
- Published
- September 28, 2026
- Version
- 1.0.0
- Files
- 11 release files
About this dataset
Overview
Method and validation record for the free Open Field Test Analyzer at conductscience.com/tools/open-field-test-analyzer. From tracked positions in a square, rectangular or round arena, the tool computes distance travelled, mean velocity, center time and entries, and a thigmotaxis index (% of time near the walls), for the session and in time bins. Three examples, on the measures described by Seibenhener and Wooten (2015), cover a straight run across a 40 × 40 cm arena, a position exactly on the center boundary, and a single tracked position, which is left out of the analysis. The record holds the calculation source files, the worked examples, a validation report with each file's SHA-256, and what changed on the tool page when the record was written.
Inspect before download
Data preview
cases.csv · first 3 rows
| id | title | source_type | expected | pass |
|---|---|---|---|---|
| analytic-straight-track | A straight run across a 40 × 40 cm arena at one position per second | analytic | {"totalDistance":36,"meanVelocity":9,"centerTime":2,"centerPct":50,"centerEntries":1,"thigmotaxisIndex":25} | true |
| analytic-center-edge | A position exactly on the center boundary | analytic | {"totalDistance":16,"centerTime":1,"centerPct":50,"centerEntries":1,"thigmotaxisIndex":50} | true |
| edge-single-position | An animal with a single tracked position | analytic | {"included":false} | true |
Read the columns
Data dictionary
cases.csvOne row per worked example.7 entries
| Name | Type | Units or values | Meaning |
|---|---|---|---|
| id | string | e.g. analytic-straight-track | Case identifier; edge cases start with "edge-" |
| title | string | What the case checks | |
| source_type | string | analytic | Where the expected answer comes from: published, hand-worked, analytic or cross-check |
| citation | string | Source of the method or the expected answer | |
| locator | string | Section, formula or table of the source that the case relies on | |
| expected | JSON object | null: not computable | Expected outputs as JSON; null means not computable |
| pass | boolean | true, false | true when every expected output matched the engine within the stated tolerance |
cases.json
The worked examples in full: inputs, expected outputs, tolerances, source passage and the arithmetic behind each expected answer.
validation-report.json
The engine's output for every case, pass or fail, with the byte count and SHA-256 of each calculation and harness file.
engine/behavioral/open-field-metrics.ts
Calculation source (MIT). Distance, velocity, center time and entries, and the thigmotaxis index.
engine/behavioral/types.ts
Calculation source (MIT). Shared types, and group statistics that leave out values that are not computable.
engine/pilot-tools.ts
Harness source (MIT). Slugs of the ten tools with validation records; the check accepts only these.
engine/validation/run.ts
Harness source (MIT). Runs one case: passes its inputs to the tool's adapter and compares each output with the expected value within the tolerance.
engine/validation/tools/open-field-test-analyzer.ts
Harness source (MIT). Adapter from a case's inputs to this tool's calculation, returning the outputs the cases check.
engine/validation/types.ts
Harness source (MIT). Types for cases, tolerances and results.
Files
tool-open-field-test-analyzer-record-1.0.0.zip
14.1 kBComplete frozen release: 15 source-manifest files plus MANIFEST.json.
SHA-256 afcfee83016870bdda86dfd00b3726c19241be0ff941363db17fb7b8c26ee040
cases.csv
1.2 kBThe worked examples, one row each: what the case checks, the source of the expected answer, the expected outputs and whether the engine matched them.
SHA-256 88388ae653c71e1422a14892cbb11a5b3a4fe7f915e02ee3bbd4e50cfed8a417
cases.json
4.1 kBThe worked examples in full: inputs, expected outputs, tolerances, source passage and the arithmetic behind each expected answer.
SHA-256 e2efcdb9ce9ac9f426ea6099868e2289eef14f0db3b9ee97accee0cc4ea3341c
validation-report.json
2.1 kBThe engine's output for every case, pass or fail, with the byte count and SHA-256 of each calculation and harness file.
SHA-256 3842298149ff84c3b8ef18912189962da976ad1957dce9c1d395f51a318eb3af
data_dictionary.csv
472 bytesColumns of cases.csv.
SHA-256 96b57ee5185ffcccc5397d98673c42bbc53ff77cc7f676fe5789ef04a7648090
README.md
1.7 kBWhat the tool computes, the files, and how to cite the record.
SHA-256 222680e06f062e5b6afdce5ebccc277d60bff86da5359753d0f70f535f9d2317
METHODS.md
2.5 kBFormulas, input rules, conventions, references and what changed on the tool page.
SHA-256 749d089a4e40dc57407afc8b1a5ec68e32a003b1a1e7f6020a40e6e1bfb60ae6
MANIFEST.json
2.3 kBByte count and SHA-256 for every file in the source release.
SHA-256 e31a034d78e31f32246b744fb95baca01be72d94705233bdbe0cfb5bf4777e3d
CITATION.cff
415 bytesCitation metadata.
SHA-256 fdc9a00cfbaf8a99376c76c30f1e142e03f56eb64d9951562618805421babbcb
LICENSE
1.3 kBMIT License for the calculation source files; CC BY 4.0 for everything else.
SHA-256 d2dca2297cc985f3577b9376fbf5a72231ac88be401776098486f6d1e8a4d87a
deposit-receipt.json
3.0 kBConductScience verification and packaging receipt.
SHA-256 d4d0b9b995df7db1e1bc2d1c22113262f3c35f84fb74dbf3af5521bdc11a2805
How it was made
Methods
- 1
Worked examples: each of the three cases gives its inputs, the expected outputs, the source and passage behind the expected answer, and the arithmetic. Expected answers follow from the geometry of tracks built for the purpose, under the rules METHODS.md states. Cases whose ids start with edge- test inputs at the limits of the method.
- 2
Check: each case was run in Node.js 24 through the tool's calculation source files, and every output was compared with its expected value, exactly or within the tolerance the case states. All three cases pass (validation-report.json), and ConductScience's test suite runs the same cases whenever the tool changes.
- 3
Fingerprint: the validation report gives the byte count and SHA-256 of each calculation file and of the files that ran the check, and engine/ holds those files, so anyone can rerun the cases and tell whether a later version of the calculation differs from this one.
Version history
Version 1.0.0 · current
Published September 28, 2026 from source tag v1.0.0 at commit 9f89d4309310.