Film the flash-family effects on the roofline controller to verify the photosensitivity table #168
Labels
No labels
area/ai
area/backend
area/frontend
area/infra
area/scheduler
area/wled
good-first-issue
priority/high
priority/low
priority/medium
security
type/bug
type/chore
type/ci-cd
type/docs
type/feature
type/qa
v1.0.0
v1.1.0
v1.2.0
v2.0.0
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/Iris-WLED#168
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?
Why
The photosensitivity guard (#150 / #167) enforces limits taken from
backend/app/data/flash_safety.json. That table was derived from WLED 16.0.0's firmware source (wled00/FX.cppat commit4374f01), not measured, and it carriesverified_on_hardware: false. The derivation assumes the worst-case frame time and uses conservative judgement. It still needs one real measurement, the same way #21 measuredtransitionwrap on the device instead of trusting the documentation.Method (also in
docs/photosensitivity.md)sx238 (the limit) and 239. Expect about 2.9/s and about 3.1/s.sx247 and 248./json/info→fps). Limits were computed at the 2 ms worst case. If the real frame rate is much lower, record that too, but don't loosen the table on the strength of one controller's frame rate.Done when
docs/photosensitivity.md(effect,sx, measured flashes per second, date, firmware).verified_on_hardwareis set totrue, per row or for the whole table.