FT-10: Time to read
<!-- Generated from field-tests/suite.json by tools/field_tests.py. Edit the JSON, not this file. -->
Category: Speed · Time: about 10 minutes · Run it and see results: https://openckey.org/tests/test?id=FT-10
What it checks
In ordinary conditions a CKey reads in under 2 seconds from pointing the camera.
Why
Speed decides whether people keep using a code. The decoder's speed on real phones has not been measured yet; this collects the first numbers.
Test codes
Print or open the sheet at https://openckey.org/tests/sheet?id=FT-10. 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/FT10-A |
Set up
- Print the test sheet at 100% scale; the code is 2.0 inches wide.
- Use ordinary indoor light. Open the reader and leave it on the camera view.
- Use a stopwatch, or a second person to time.
Steps
- Point away from the code, then start the stopwatch as you point at it from about 20 cm.
- Stop it when the result appears.
- Repeat 10 times and record each time.
What to record
- Seconds to result (s), number, required. For each of: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10.
Every report also records the device, operating system, reader and its version, and the printer or screen.
How to grade it
- Pass: The median of the ten times is under 2 seconds.
- Partial: The median is 2 to 5 seconds.
- Fail: The median is over 5 seconds, or some attempts never read.
Report a result
- On openckey.org: https://openckey.org/tests/test?id=FT-10, with optional photos.
- On GitHub: open a field-test report and choose FT-10.
Both are published together at https://openckey.org/tests and as JSON at https://openckey.org/api/field/results.