Dépôts renommés avec le préfixe aimsight- : chemins et noms mis à jour

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
maximeandClaude Opus 5.5 committed 2026-11-16 14:56:41 +01:00
1 parent 1d1ce142ec
commit d2146af0e8
6 files changed
+29 -29

No files matched your search

+9 -9
View File
@@ -1,4 +1,4 @@
# Diagnostic-app
# aimsight-app
The control station of the AIMsight diagnostic: see, analyze, launch. The Data page shows the curves, the camera images, the labels and the detectors' events; its Analysis tab launches, by `claude -p`, processes whose code lives in the other repositories:
@@ -18,19 +18,19 @@ And six links, ignored by git, to the neighbouring repositories (a single copy o
| Link | Repository | What the app does with it |
|---|---|---|
| `data/` | `~/aimsight-data/data` | reads the data of the stations (outside git) |
| `labeling/` | `~/labeling` | reads and writes the labels; the analyses go in `labeling/auto/analyses/` |
| `detectors/` | `~/detectors` | reads the detectors' events (`scripts/categories.py`) |
| `tools/` | `~/tools` | reads the data through `tools/scripts/data.py`; the analyst uses it, the upgrader writes in it (Optimizer) |
| `agents/` | `~/agents` | the plugin of the agents (`--plugin-dir agents`, `--agent agents:analyst`) |
| `optimizer/` | `~/Optimizer` | launches `/optimize` there; reads the summaries in `optimizer/sessions/` |
| `labeling/` | `~/aimsight-labeling` | reads and writes the labels; the analyses go in `labeling/auto/analyses/` |
| `detectors/` | `~/aimsight-detectors` | reads the detectors' events (`scripts/categories.py`) |
| `tools/` | `~/aimsight-tools` | reads the data through `tools/scripts/data.py`; the analyst uses it, the upgrader writes in it (Optimizer) |
| `agents/` | `~/aimsight-agents` | the plugin of the agents (`--plugin-dir agents`, `--agent agents:analyst`) |
| `optimizer/` | `~/aimsight-optimizer` | launches `/optimize` there; reads the summaries in `optimizer/sessions/` |
Each thing is committed in its own repository: the labels in `~/labeling`, the detectors in `~/detectors` (the optimization session does it, without pushing), the tools in `~/tools` (the same session, through the upgrader).
Each thing is committed in its own repository: the labels in `~/aimsight-labeling`, the detectors in `~/aimsight-detectors` (the optimization session does it, without pushing), the tools in `~/aimsight-tools` (the same session, through the upgrader).
## Install and launch
```bash
ln -s ~/aimsight-data/data data && ln -s ~/labeling labeling && ln -s ~/detectors detectors
ln -s ~/tools tools && ln -s ~/agents agents && ln -s ~/Optimizer optimizer
ln -s ~/aimsight-data/data data && ln -s ~/aimsight-labeling labeling && ln -s ~/aimsight-detectors detectors
ln -s ~/aimsight-tools tools && ln -s ~/aimsight-agents agents && ln -s ~/aimsight-optimizer optimizer
```
The VS Code task **Run app** creates `.venv` and builds the front end if they are missing, then launches the server. By hand: