Skip to content

Main content

Random Nonogram Line Completion Puzzle Generator

Generate a binary Nonogram line with hidden cells and exact bounded completion counts and forced-cell answers.

Loading tool…

Description

Generate a binary Nonogram line with hidden cells and exact bounded completion counts and forced-cell answers.

A generated practice exercise contains a prompt and an answer key under a specific rule set. A planted answer establishes one possible solution; only an explicit enumeration or uniqueness check establishes whether alternatives exist.

Generate a binary Nonogram line with hidden cells and exact bounded completion counts and forced-cell answers.

When to use this tool

Use this generator to create reproducible nonogram line completion puzzle cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.

How to use the tool and how it works

  1. Supply length, hiddenCount in the field shapes below. Set seed when you need an explicit replay.
  2. Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
  3. Read puzzle, answer, feasibility. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Draw a binary line, calculate filled-run clues, and hide distinct cells. Exhaustively enumerate all bounded-length binary lines agreeing with visible cells and clues, reporting completionCount, uniqueness, and cells shared by every completion.1

Delegated operations used for this result: nonogram clue sum plus gaps length checker. Their calculation or parsing conventions apply to the corresponding result fields.2

Input fieldMeaning and unitsAccepted input
lengthLengthRequired. Safe integer; minimum 1; maximum 16.
hiddenCountHidden CountRequired. Safe integer; minimum 0; maximum 16.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
puzzlePuzzleRequired. Object; no unknown keys.
puzzle.cluesCluesRequired. Array of Safe integer.; minimum items 0; maximum items 16.
puzzle.cellsCellsRequired. Array of Safe integer; minimum 0; maximum 1. or Null.; minimum items 0; maximum items 16.
answerAnswerRequired. Object; no unknown keys.
answer.solutionSolutionRequired. Array of Safe integer; minimum 0; maximum 1.; minimum items 0; maximum items 16.
answer.completionCountCompletion CountRequired. Safe integer.
answer.uniqueUniqueRequired. Boolean.
answer.forcedCellsForced CellsRequired. Array of Safe integer; minimum 0; maximum 1. or Null.; minimum items 0; maximum items 16.
feasibilityFeasibilityRequired. Object; no unknown keys.
feasibility.minimumRequiredLineCellsMinimum Required Line CellsRequired. Safe integer.
feasibility.signedRemainingSlackCellsSigned Remaining Slack CellsRequired. Safe integer.
feasibility.lineLengthFeasibleLine Length FeasibleRequired. Boolean.
randomnessReplay metadata: source is seed or context; seed is the normalized 32-bit seed or null for a context source.Required. Object; no unknown keys.
randomness.seedOptional numeric replay seed; normalization and precedence are explained below.Required. Safe integer. or Null.
randomness.sourceSourceRequired. Text; one of "context", "seed".

An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.

json
{
  "input": {
    "length": 6,
    "hiddenCount": 2,
    "seed": 42
  },
  "output": {
    "puzzle": {
      "clues": [
        1,
        2,
        1
      ],
      "cells": [
        1,
        null,
        1,
        null,
        0,
        1
      ]
    },
    "answer": {
      "solution": [
        1,
        0,
        1,
        1,
        0,
        1
      ],
      "completionCount": 1,
      "unique": true,
      "forcedCells": [
        1,
        0,
        1,
        1,
        0,
        1
      ]
    },
    "feasibility": {
      "minimumRequiredLineCells": 6,
      "signedRemainingSlackCells": 0,
      "lineLengthFeasible": true
    },
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • Null in the puzzle means hidden and null in forcedCells means not forced. A planted solution is always retained but uniqueness is not guaranteed. Exhaustive enumeration is intentionally limited to short lines.
  • A replay requires the same complete input and implementation. Randomized construction does not guarantee uniform coverage of every feasible output; finite samples can repeat unless a distinct-selection rule is explicitly stated.
  • The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.

Alternative or Complementary methods

For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.

References

  1. Tool behavior and example: Random Nonogram Line Completion Puzzle Generator — tool.io

  2. Calculation or validation: game/nonogram-clue-sum-plus-gaps-length-checker — tool.io

Similar or alternative tools