ConductScience Rotarod Test Analyzer: method and validation record
The calculation behind ConductScience's free rotarod test analyzer, with five 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 Rotarod Test Analyzer at conductscience.com/tools/rotarod-test-analyzer. From latencies to fall, the tool computes daily means and learning curves, the rod speed at fall on an accelerating rod (per trial, then averaged), the area under each animal's learning curve (AUC) and each animal's longest latency. Five hand-worked examples, on the accelerating rod described by Deacon (2013), cover the speed at a fall mid-ramp, a daily mean from two trials with one past the ramp, a three-day AUC, a single day of testing, which has no AUC, and an uploaded latency above the trial cutoff. 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 5 rows
| id | title | source_type | expected | pass |
|---|---|---|---|---|
| hand-worked-rpm-at-fall | Rod speed at a fall halfway through a 4-40 RPM, 300 s ramp | hand-worked | {"rpmAtFall":22} | true |
| hand-worked-mean-rpm | Daily RPM at fall from two trials, one past the end of the ramp | hand-worked | {"meanRpmAtFall":31} | true |
| hand-worked-auc | Area under a three-day learning curve | hand-worked | {"auc":180} | true |
| edge-single-day | An animal tested on one day | hand-worked | {"auc":null} | true |
| edge-cutoff | An uploaded latency longer than the trial cutoff | hand-worked | {"latency":300} | true |
Read the columns
Data dictionary
cases.csvOne row per worked example.7 entries
| Name | Type | Units or values | Meaning |
|---|---|---|---|
| id | string | e.g. hand-worked-rpm-at-fall | Case identifier; edge cases start with "edge-" |
| title | string | What the case checks | |
| source_type | string | hand-worked | 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/rotarod-metrics.ts
Calculation source (MIT). Latency to fall with the trial cutoff, rod speed at fall, and learning-curve AUC.
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/rotarod-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-rotarod-test-analyzer-record-1.0.0.zip
12.8 kBComplete frozen release: 14 source-manifest files plus MANIFEST.json.
SHA-256 4bbeba72e5586530516238f83d2d946e5e156168ca8d75334921f1100cb0e430
cases.csv
1.7 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 35a16544253274c58b5aae7c0486a51be2aa1eaed69229d4db0a2f617388f15a
cases.json
4.0 kBThe worked examples in full: inputs, expected outputs, tolerances, source passage and the arithmetic behind each expected answer.
SHA-256 be36684882d9968c86d3064b1760cf26e6159477207c3fc184443b31db644f1c
validation-report.json
1.8 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 c499341912bf04e3d5733ef269ff27f014b0d75015696ae3a9f5a4d6739199af
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 5d3937a10659eaf38832ec8120a65766848905f52ad74391903094eb283be870
METHODS.md
2.3 kBFormulas, input rules, conventions, references and what changed on the tool page.
SHA-256 5132dbd4477cf2be4fd741fcd2759f5409b22b9820ee39417753c64a8af1b3c4
MANIFEST.json
2.1 kBByte count and SHA-256 for every file in the source release.
SHA-256 fb780b5887428747217291edb40949821aefad13c491912a730d3e79043194b1
CITATION.cff
407 bytesCitation metadata.
SHA-256 78fe493060bb6f7619d803832d6d2d64a1d9f04b87236e97f27b3c598b9723ee
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 d93939f1b8819107ad0c447f4331bc65625a376773b8445772964c214aa17860
How it was made
Methods
- 1
Worked examples: each of the five cases gives its inputs, the expected outputs, the source and passage behind the expected answer, and the arithmetic. Expected answers are worked by hand from the published method, or from the tool's own rule where METHODS.md labels it a convention. 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 five 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 ea833f7a98c1.