Skip to content

Main content

Random SET Triple Recognition Quiz Generator

Construct distinct four-feature ternary card triples and an exact distractor count with delegated SET validity keys and no artwork.

Loading tool…

Description

Construct distinct four-feature ternary card triples and an exact distractor count with delegated SET validity keys and no artwork.

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.

Construct distinct four-feature ternary card triples and an exact distractor count with delegated SET validity keys and no artwork.

When to use this tool

Use this generator to create reproducible set triple recognition quiz 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 count, invalidCount 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 questions. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Draw two distinct four-feature ternary cards and calculate the unique third card making each feature all same or all different. For the exact requested invalid count, mutate one feature without duplicating another card. Delegate validity and feature flags, then shuffle questions.1

Delegated operations used for this result: set card all same or all different checker. Their calculation or parsing conventions apply to the corresponding result fields.2

Input fieldMeaning and unitsAccepted input
countRequested count; the mechanics explain whether one draw expands into several returned records.Required. Safe integer; minimum 1; maximum 64.
invalidCountInvalid CountRequired. Safe integer; minimum 0; maximum 64.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
questionsQuestionsRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 64.
questions[].cardsCardsRequired. Array of Array of Safe integer; minimum 0; maximum 2.; minimum items 4; maximum items 4.; minimum items 3; maximum items 3.
questions[].validSetValid SetRequired. Boolean.
questions[].featureFlagsFeature FlagsRequired. Array of Safe integer.; minimum items 4; maximum items 4.
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": {
    "count": 1,
    "invalidCount": 1,
    "seed": 42
  },
  "output": {
    "questions": [
      {
        "cards": [
          [
            1,
            2,
            1,
            0
          ],
          [
            0,
            0,
            1,
            0
          ],
          [
            2,
            1,
            1,
            1
          ]
        ],
        "validSet": false,
        "featureFlags": [
          1,
          1,
          1,
          0
        ]
      }
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • invalidCount cannot exceed count. Cards are numeric feature vectors with no artwork or rules beyond the four-feature ternary test; the answer key should be hidden during practice.
  • 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 SET Triple Recognition Quiz Generator — tool.io

  2. Calculation or validation: game/set-card-all-same-or-all-different-checker — tool.io

Similar or alternative tools