administrator/rov-autonomy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: log respawn rollout across stack nodes

Browse Source
This commit is contained in:
Grant 2026-07-08 18:24:38 +02:00
parent a5e1c9930b
commit 917342a27b
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CLAUDE.md
View File

@ -373,6 +373,14 @@ entries; correct forward with a new dated entry if something needs revising.
rov_full.launch.py declares no such arg, so RECORD=false is silently ignored and rov_full.launch.py declares no such arg, so RECORD=false is silently ignored and
bags record regardless. Both deferred to a dedicated DIR-9a recorder-rework session bags record regardless. Both deferred to a dedicated DIR-9a recorder-rework session
— do NOT wire RECORD into the current DIR-9 model. — do NOT wire RECORD into the current DIR-9 model.
- 2026-07-08 — Added respawn=True/respawn_delay=5.0 to failsafe_monitor,
motion_controller, ekf_filter_node, depth_node, mission_executor. Deliberately NOT
applied to: mavros_node (respawn could mask/worsen the chronic FCU-link instability
— belongs in that investigation), recording_manager (pending DIR-9a rework),
camera_node/feature_detector (perception not operational yet), foxglove_bridge
(viz-only). NOTE: failsafe_monitor respawn has a coverage gap during the 5s respawn
delay — no failsafe assessment in that window; flagged for future design
consideration.
--- ---