FT-04: Lighting
<!-- Generated from field-tests/suite.json by tools/field_tests.py. Edit the JSON, not this file. -->
Category: Light · Time: about 15 minutes · Run it and see results: https://openckey.org/tests/test?id=FT-04
What it checks
A printed CKey reads in daylight, ordinary indoor light, dim light and under a reflection.
Why
Low light adds noise and blur, warm light shifts colour, and glare washes out part of the code. The certification model includes noise and glare; this checks it against real rooms.
Test codes
Print or open the sheet at https://openckey.org/tests/sheet?id=FT-04. It is drawn by the CKey web SDK from the values below.
| Code | Size | Version | Level | Layout | Style | Holds |
|---|---|---|---|---|---|---|
| A | 2.0 in | smallest that fits | M | standard | plain | https://openckey.org/t/FT04-A |
Set up
- Print the test sheet at 100% scale; the code is 2.0 inches wide.
- Keep the phone about 25 cm from the sheet with the flash off.
Steps
- Try the code in each condition: outdoor daylight (not direct sun on the screen), ordinary indoor light, a dim room lit by one distant lamp, warm lamp light close by, and with a bright reflection crossing part of the code (glossy paper or a sheet protector under a lamp).
- Allow up to 5 seconds in each.
- Record whether it read, and optionally the light level from a light-meter app.
What to record
- Read within 5 seconds, boolean, required. For each of: Daylight, Indoor, Dim, Warm lamp, Reflection.
- Light level, if measured (lux), number, optional. For each of: Daylight, Indoor, Dim, Warm lamp, Reflection.
Every report also records the device, operating system, reader and its version, and the printer or screen.
How to grade it
- Pass: It read in daylight, indoor, dim and warm light.
- Partial: It read in daylight and indoor light only.
- Fail: It did not read in ordinary indoor light.
Report a result
- On openckey.org: https://openckey.org/tests/test?id=FT-04, with optional photos.
- On GitHub: open a field-test report and choose FT-04.
Both are published together at https://openckey.org/tests and as JSON at https://openckey.org/api/field/results.