Viewing is open to everyone. Downloading and starring need a GitHub sign-in. Sign in with GitHub

FT-08.md

v0.1.0-build.85 Latest Commit ede38f5

Size
2.4 KB
Lines
56
Language
Markdown
SHA-256
7b47156efa6b…
View on GitHub

Sign in with GitHub to download. Each download is recorded with your GitHub username.

FT-08: Density

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

Category: Capacity · Time: about 10 minutes · Run it and see results: https://openckey.org/tests/test?id=FT-08

What it checks

At a fixed 2-inch print size, denser versions need a closer, steadier camera; version 10 still reads.

Why

More data means smaller marks at the same size. This shows where, for an ordinary phone, a code should be printed larger to carry more.

Test codes

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

Code Size Version Level Layout Style Holds
A 2.0 in 1 L standard plain https://openckey.org/t/FT08-A
B 2.0 in 5 M standard plain https://openckey.org/t/FT08-B
C 2.0 in 10 M standard plain https://openckey.org/t/FT08-C
D 2.0 in 15 M standard plain https://openckey.org/t/FT08-D
E 2.0 in 20 M standard plain https://openckey.org/t/FT08-E

Set up

  1. Print the test sheet at 100% scale; each code is 2.0 inches wide.
  2. Use ordinary indoor light.

Steps

  1. Try each code, A (version 1) to E (version 20), from about 20 cm, moving closer if needed.
  2. Allow up to 8 seconds each.
  3. Record whether it read and the closest distance you needed.

What to record

  • Read within 8 seconds, boolean, required. For each of: v1, v5, v10, v15, v20.
  • Distance needed (cm), number, optional. For each of: v1, v5, v10, v15, v20.

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

How to grade it

  • Pass: Versions 1, 5 and 10 read.
  • Partial: Versions 1 and 5 read but not 10.
  • Fail: Version 5 did not read.

Report a result

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