Supported files¶
Detection uses the contents and header shape, not a vendor name in the filename.
| Layout | Extensions | Support | Time basis | Meaning |
|---|---|---|---|---|
| ClockLab seven-line AWD | .awd |
Native | Header date, time, and interval | Activity counts; negative values become missing |
| Timestamped table, including MotionWatch text export | .csv, .tsv, .txt |
Exported text | Timestamp column or separate date/time | Activity plus numeric channels; labels and inferred units retained |
| BioDare2 table | .csv, .tsv |
Exported text | Elapsed hours | One series per column; synthetic calendar origin declared |
| Wide plate/region table | .csv, .tsv |
Exported text | Increasing elapsed hours | One well, region, or channel per column |
| Excel first sheet | .xlsx |
Optional dependency | Any supported table shape | Requires openpyxl; the detected inner layout is reported |
Not parsed without a specimen¶
ActiGraph .agd, GENEActiv .bin, Actiwatch proprietary files, VitalView proprietary files, Trikinetics folder or proprietary layouts, LumiCycle proprietary files, and Incucyte proprietary files are unsupported because no permitted representative specimen is present. Export a single timestamped or elapsed-hours text table instead.
The first two are worth naming separately, because their layouts are not secret. An .agd file is a SQLite database and a .bin file is a text header over hex-encoded pages; either could be read from the published description alone. A parser written from a description and never run against a file the device actually wrote is a parser nobody has tested, and the failure it produces is not a crash — it is a recording with the wrong epoch length, or an off-wrist stretch read as an hour of stillness. So they wait for a genuine export like everything else on this list.
This is deliberate. A vendor product name can cover incompatible format generations, so the workbench will not guess a parser from an extension. A new parser requires a deidentified or redistribution-approved specimen, a written format signature, a near-neighbour rejection test, and all importer invariants.
Invariants¶
Every accepted recording has sorted unique timestamps, a positive inferred interval, non-negative observed activity, and NaN for missing activity. Source labels, units, aggregation, and whether the calendar origin was synthetic remain in the recording metadata.