Viewing is open to everyone. Downloading and starring need a GitHub sign-in.
Sign in with GitHub
FT-01.md
v0.1.0-build.85
Latest
Commit ede38f5
Sign in with GitHub to download. Each download is recorded with your GitHub username.
| 1 | # FT-01: Smallest printed size |
| 2 | |
| 3 | <!-- Generated from field-tests/suite.json by tools/field_tests.py. Edit the JSON, not this file. --> |
| 4 | |
| 5 | **Category:** Print · **Time:** about 10 minutes · **Run it and see results:** [https://openckey.org/tests/test?id=FT-01](https://openckey.org/tests/test?id=FT-01) |
| 6 | |
| 7 | ## What it checks |
| 8 | |
| 9 | A standard-layout CKey holding a short link reads when printed at 1 inch (25 mm) wide. |
| 10 | |
| 11 | ## Why |
| 12 | |
| 13 | Print size is the first thing a designer chooses and the easiest mistake to make. The core's certification models camera photos down to a few pixels per module; this test checks that model against real printers and real cameras. |
| 14 | |
| 15 | ## Test codes |
| 16 | |
| 17 | Print or open the sheet at [https://openckey.org/tests/sheet?id=FT-01](https://openckey.org/tests/sheet?id=FT-01). It is drawn by the CKey web SDK from the values below. |
| 18 | |
| 19 | | Code | Size | Version | Level | Layout | Style | Holds | |
| 20 | |---|---|---|---|---|---|---| |
| 21 | | A | 0.4 in | smallest that fits | M | standard | plain | `https://openckey.org/t/FT01-A` | |
| 22 | | B | 0.5 in | smallest that fits | M | standard | plain | `https://openckey.org/t/FT01-B` | |
| 23 | | C | 0.75 in | smallest that fits | M | standard | plain | `https://openckey.org/t/FT01-C` | |
| 24 | | D | 1.0 in | smallest that fits | M | standard | plain | `https://openckey.org/t/FT01-D` | |
| 25 | | E | 1.5 in | smallest that fits | M | standard | plain | `https://openckey.org/t/FT01-E` | |
| 26 | | F | 2.0 in | smallest that fits | M | standard | plain | `https://openckey.org/t/FT01-F` | |
| 27 | |
| 28 | ## Set up |
| 29 | |
| 30 | 1. Print the test sheet at 100% scale (no "fit to page") on plain white paper. |
| 31 | 2. Measure code F with a ruler: it must be 2.0 inches (51 mm) wide. If it is not, your printer scaled the sheet; fix the print settings and print again. |
| 32 | 3. Hold the phone about 20 cm from the sheet in ordinary indoor light. |
| 33 | |
| 34 | ## Steps |
| 35 | |
| 36 | 1. Open the reader. |
| 37 | 2. Point it at each code from A (smallest) to F (largest), one at a time, for up to 5 seconds each. |
| 38 | 3. Record whether it read and roughly how many seconds it took. |
| 39 | |
| 40 | ## What to record |
| 41 | |
| 42 | - **Read within 5 seconds**, boolean, required. For each of: A, B, C, D, E, F. |
| 43 | - **Seconds to read** (s), number, optional. For each of: A, B, C, D, E, F. |
| 44 | |
| 45 | Every report also records the device, operating system, reader and its version, and the printer or screen. |
| 46 | |
| 47 | ## How to grade it |
| 48 | |
| 49 | - **Pass:** Code D (1 inch) and every larger code read. |
| 50 | - **Partial:** Only code E (1.5 inches) or larger read. |
| 51 | - **Fail:** Code F (2 inches) did not read. |
| 52 | |
| 53 | ## Report a result |
| 54 | |
| 55 | - On openckey.org: [https://openckey.org/tests/test?id=FT-01](https://openckey.org/tests/test?id=FT-01), with optional photos. |
| 56 | - On GitHub: [open a field-test report](https://github.com/clearkeysolutions/ckey/issues/new?template=field-test-report.yml&title=%5BFT-01%5D+) and choose FT-01. |
| 57 | |
| 58 | Both are published together at [https://openckey.org/tests](https://openckey.org/tests) and as JSON at [https://openckey.org/api/field/results](https://openckey.org/api/field/results). |