30 lines
2.6 KiB
Markdown
30 lines
2.6 KiB
Markdown
# Tools: NORDEND_2026-11-05T0600_2026-11-05T1200
|
|
|
|
**Tools modified**: none
|
|
**data.py**: unchanged
|
|
|
|
## What the analyst used
|
|
- `inventory.py` on the range: references kept at each instant, rejections of CTR01 and PR09.
|
|
- `overview.py --min 1` (widened window from 04:00 to 14:00), then `--rigid 2026-11-05T06:00Z --follow … --residuals no`: the pose and the table by step dated the jolt of 12:00 (rotation, tilt, raw positions); the residual PNGs showed the drift of the right edge.
|
|
- `ranges.py --columns corr_x,corr_y --rolling 4 --instants 3`: under the thermal drift, it returned only two instants (09:45 with 3 sensors, 12:00 with 8), with the state of the references. It is the command that grounds the label.
|
|
- `summary.py --step 15min --level window --mark` (`corr_y`, `error_value`), `metrics.py`, `plot.py --zone`, `thumbnails.py --radius 40`, the whole image of 12:00.
|
|
- The folder has no `scripts/`: the analyst wrote no script. Its "Difficulties" mention only Ollama (`labeling/precedents.py`), which does not depend on this repository. Its "Documentation" section talks about the labeling rules, not about reading.
|
|
- What was cluttering, slightly: a `| tail -22` on `summary.py` and a `| head -20` on `metrics.py`, to cut an output. `--start`/`--end` and the pipe to `grep` described in the guide already do it.
|
|
|
|
## What I decided
|
|
- All the tools used: left as they are. They showed what the analyst had to see: the one-measurement jolt under the drift (`ranges.py --rolling --instants`), the pose and the references (`overview.py`, `--rigid`). Nothing was missing for it.
|
|
- `summary.py`, `metrics.py`: left as they are. The `head`/`tail` were the analyst's choice, not a lack of the tool. The Conventions of the guide already say how to shorten an output.
|
|
- No script to bring in: `scripts/` does not exist.
|
|
|
|
## What changed
|
|
none
|
|
|
|
## Trial
|
|
No tool changed, so there was nothing new to try. I nevertheless reran, from `tools/scripts/`, the tools the report cites: the analysis ran just before commit 67c8862, which moved the tools into `scripts/`. The figures are stored in `work/`: common, multiples-error_value, residuals-corr_x/corr_y/error_value, rigid, metrics.
|
|
|
|
## Report commands rerun
|
|
5, with the `tools/scripts/` paths (`overview.py --min 1`, `metrics.py`, `ranges.py --rolling 4 --instants 3`, `overview.py --rigid 2026-11-05T06:00Z`, `inventory.py`): no failure. `ranges.py` returns the same two instants (09:45: 3 sensors; 12:00: 8 sensors) as those cited by the analyst.
|
|
|
|
## Difficulties
|
|
- The log cites the tools at their old path (`tools/inventaire.py`, `tools/ensemble.py` …). The report names them without a path. I reran with `tools/scripts/`, like the current guide.
|