Monochrome Print Suitability Checker

Audit actual independently measured monochrome hatch visibility/discrimination evidence; not colour-to-gray conversion or print certification. Actual monochrome hatch separability observations against independently verified inclusive caller bands; signed margins and missing observations retained, not conformance/authenticity.

Description

Monochrome suitability depends on measurable reproduction criteria and the chosen print process.

Monochrome suitability depends on measurable reproduction criteria and the chosen print process.1

A numeric band comparison does not inspect a rendered proof. The tool compares supplied metrics with caller-selected bands, keeping known deviations and unknown rows separate.

When to use Monochrome Print Suitability Checker

Use this tool to calculate or review the supplied observations under the stated rules. Establish the source tradition, viewing frame, coordinate units and independently annotated features.

How to use Monochrome Print Suitability Checker and understand its results

  1. Establish the source tradition, viewing frame, coordinate units and independently annotated features.
  2. Enter observedValues, callerLower, callerUpper, knownFlags, using the field meanings and rules below, then run the tool.
  3. Read result.signedKnownMargins, result.knownReviewIndices, result.unknownIndices, using the output meanings and calculation rules below. Review negative known margins and keep unknown indices separate; their zero placeholders do not establish a pass.
  4. Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
Input fieldMeaningValue typeRequirement
observedValuesObserved valueslist of numberRequired
callerLowerCaller lowerlist of numberRequired
callerUpperCaller upperlist of numberRequired
knownFlagsKnown flags; binary 1 means the matched observation is known, 0 means unknownlist of numberRequired

Use nonempty aligned finite observations, lower and upper bounds, and binary known flags. Require lower≤upper for every row. For known rows return min(observed−lower,upper−observed); strictly negative margins enter the review list. Unknown rows receive zero placeholders and appear in the separate unknown-index list. A known boundary is included; an unknown zero is not passing evidence.

margin_i=known_i?min(observed_i−lower_i,upper_i−observed_i):0

Use the matching field units and the exact boundary, ordering and reference rules above.

Output fieldMeaningValue type
resultCalculated observation or referenceobject
result.signedKnownMarginssigned Known Margins; preserve the subtraction order and sign defined in the mechanicslist
result.knownReviewIndicesknown Review Indices; zero-based positions in the relevant supplied record or adjacent-pair listlist
result.unknownIndicesunknown Indices; zero-based positions in the relevant supplied record or adjacent-pair list; unresolved records kept separate from known resultslist
json
{
  "input": {
    "observedValues": [
      2,
      5
    ],
    "callerLower": [
      1,
      1
    ],
    "callerUpper": [
      3,
      4
    ],
    "knownFlags": [
      1,
      0
    ]
  },
  "output": {
    "result": {
      "signedKnownMargins": [
        1,
        0
      ],
      "knownReviewIndices": [],
      "unknownIndices": [
        1
      ]
    }
  }
}

Limitations and assumptions

The supplied annotations, measurements and source tradition determine applicability. The tool does not independently establish identity, provenance, entitlement or heraldic acceptability.

Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above. Extremely large composite outputs are rejected.

Alternative or Complementary methods

For a related step, use Hatching System Line-Angle Tincture Encoder: Monochrome hatching represents tinctures using line directions, blank areas and stippling under a specified convention. For a complementary comparison, use Hatching Line Angle to Tincture Decoder: Decoding hatching requires both line directions and stippling because different tinctures can have no lines.

References

  1. Monochrome Print Suitability Checker — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies