FT-06: Damage

<!-- Generated from field-tests/suite.json by tools/field_tests.py. Edit the JSON, not this file. -->

Category: Damage · Time: about 20 minutes · Run it and see results: https://openckey.org/tests/test?id=FT-06

What it checks

Error correction lets a CKey read through marks, a covered patch and creasing, with more damage tolerated at higher levels.

Why

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.

Test codes

Print or open the sheet at https://openckey.org/tests/sheet?id=FT-06. It is drawn by the CKey web SDK from the values below.

Set up

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.
2. Keep the first copy clean for comparison.

Steps

1. On the second copy, damage both codes the same way, one step at a time, testing after each step:
2. 1. Draw one pen line, about 2 mm wide, straight across the middle.
3. 2. Cover the bottom-right corner area with a sticky note about 1/8 of the code's width.
4. 3. Crumple the sheet into a ball, then flatten it.
5. Allow up to 5 seconds each and record whether each code read.

What to record

• Code A (level M) read, boolean, required. For each of: Clean, Pen line, Covered corner, Crumpled.
• Code B (level H) read, boolean, required. For each of: Clean, Pen line, Covered corner, Crumpled.

Every report also records the device, operating system, reader and its version, and the printer or screen.

How to grade it

• Pass: Code B read after every step.
• Partial: Both read clean and after the pen line, but code B failed a later step.
• Fail: Code B did not read after the pen line.

Report a result

• On openckey.org: https://openckey.org/tests/test?id=FT-06, with optional photos.
• On GitHub: open a field-test report and choose FT-06.

Both are published together at https://openckey.org/tests and as JSON at https://openckey.org/api/field/results.