Explorer: derived radar loop windows for event replay #140
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot#140
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent: #22. #22 asks for "derived radar-loop windows with configurable padding."
Depends on the capture-cadence decision in the radar snapshot issue: a loop needs more than one frame per event, and today
_radar_snapshot_filenameis deterministic per lifecycle so re-fires overwrite rather than accumulate.Tasks
app/services/radar.pyalready assembles multi-frame GIFs for SPC (spc_gif_*cache entries) — reuse that machinery rather than writing a second assembler.Picking this up, stacked on the event timeline (#139, PR #172). Per the task list: loop window = event member span + configurable padding; frames from the #130 capture (
alert_radar_frames, keyed per dashboard SentAlert — accumulating, so the "deterministic filename overwrite" concern predates #130 and no longer applies); assembly reusesradar.py's existing SPC GIF machinery; served through the media storage abstraction (#131); built lazily on first view and cached, per the issue's own recommendation; partial/no-frame coverage degrades visibly (coverage span labeled on the player, explicit "no frames captured" state) rather than implying a complete window.