Viewing is open to everyone. Downloading and starring need a GitHub sign-in.
Sign in with GitHub
FT-06.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-06: Damage |
| 2 | |
| 3 | <!-- Generated from field-tests/suite.json by tools/field_tests.py. Edit the JSON, not this file. --> |
| 4 | |
| 5 | **Category:** Damage · **Time:** about 20 minutes · **Run it and see results:** [https://openckey.org/tests/test?id=FT-06](https://openckey.org/tests/test?id=FT-06) |
| 6 | |
| 7 | ## What it checks |
| 8 | |
| 9 | Error correction lets a CKey read through marks, a covered patch and creasing, with more damage tolerated at higher levels. |
| 10 | |
| 11 | ## Why |
| 12 | |
| 13 | Reed–Solomon correction and the scrambled layout are meant to spread damage thinly across many bytes. This is the plainest way to see whether level H buys what it costs. |
| 14 | |
| 15 | ## Test codes |
| 16 | |
| 17 | Print or open the sheet at [https://openckey.org/tests/sheet?id=FT-06](https://openckey.org/tests/sheet?id=FT-06). It is drawn by the CKey web SDK from the values below. |
| 18 | |
| 19 | | Code | Size | Version | Level | Layout | Style | Holds | |
| 20 | |---|---|---|---|---|---|---| |
| 21 | | A | 2.0 in | smallest that fits | M | standard | plain | `https://openckey.org/t/FT06-A` | |
| 22 | | B | 2.0 in | smallest that fits | H | standard | plain | `https://openckey.org/t/FT06-B` | |
| 23 | |
| 24 | ## Set up |
| 25 | |
| 26 | 1. Print the test sheet twice at 100% scale; each code is 2.0 inches wide. Code A is level M and code B is level H. |
| 27 | 2. Keep the first copy clean for comparison. |
| 28 | |
| 29 | ## Steps |
| 30 | |
| 31 | 1. On the second copy, damage both codes the same way, one step at a time, testing after each step: |
| 32 | 2. 1. Draw one pen line, about 2 mm wide, straight across the middle. |
| 33 | 3. 2. Cover the bottom-right corner area with a sticky note about 1/8 of the code's width. |
| 34 | 4. 3. Crumple the sheet into a ball, then flatten it. |
| 35 | 5. Allow up to 5 seconds each and record whether each code read. |
| 36 | |
| 37 | ## What to record |
| 38 | |
| 39 | - **Code A (level M) read**, boolean, required. For each of: Clean, Pen line, Covered corner, Crumpled. |
| 40 | - **Code B (level H) read**, boolean, required. For each of: Clean, Pen line, Covered corner, Crumpled. |
| 41 | |
| 42 | Every report also records the device, operating system, reader and its version, and the printer or screen. |
| 43 | |
| 44 | ## How to grade it |
| 45 | |
| 46 | - **Pass:** Code B read after every step. |
| 47 | - **Partial:** Both read clean and after the pen line, but code B failed a later step. |
| 48 | - **Fail:** Code B did not read after the pen line. |
| 49 | |
| 50 | ## Report a result |
| 51 | |
| 52 | - On openckey.org: [https://openckey.org/tests/test?id=FT-06](https://openckey.org/tests/test?id=FT-06), with optional photos. |
| 53 | - On GitHub: [open a field-test report](https://github.com/clearkeysolutions/ckey/issues/new?template=field-test-report.yml&title=%5BFT-06%5D+) and choose FT-06. |
| 54 | |
| 55 | 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). |