Skip to content

Main content

Random Waterfall Change Dataset Generator

Generate bounded signed changes with cumulative opening/closing reconciliation and explicit subtotal bars.

Loading tool…

Description

Generate bounded signed changes with cumulative opening/closing reconciliation and explicit subtotal bars.

A chart dataset contains values plus the labels, grouping, totals, or missing-value conventions needed to interpret them. Separating the numeric construction from plotting makes conservation rules and deliberate edge cases visible before a chart is rendered.

Generate bounded signed changes with cumulative opening/closing reconciliation and explicit subtotal bars.

When to use this tool

Use this generator to create reproducible waterfall change dataset 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 opening, minimumChange, maximumChange, count, subtotalAfter 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 changes, closing, bars. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Draw signed integer changes, check every cumulative total using exact integer arithmetic, and delegate cumulative sums beginning at opening. Emit one from/to change bar per draw and zero-based subtotal bars after the requested one-based change positions.1

Delegated operations used for this result: cumulative sum. Their calculation or parsing conventions apply to the corresponding result fields.2

Input fieldMeaning and unitsAccepted input
openingOpeningRequired. Safe integer.
minimumChangeMinimum ChangeRequired. Safe integer.
maximumChangeMaximum ChangeRequired. Safe integer.
countRequested count; the mechanics explain whether one draw expands into several returned records.Required. Safe integer; minimum 1; maximum 32.
subtotalAfterSubtotal AfterRequired. Array of Safe integer; minimum 1; maximum 32.; minimum items 0; maximum items 32.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
changesChangesRequired. Array of Safe integer.; minimum items 1; maximum items 32.
closingClosingRequired. Safe integer.
barsBarsRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 64.
bars[].kindKindRequired. Text; one of "change", "subtotal".
bars[].afterAfterRequired. Safe integer.
bars[].fromFromRequired. Safe integer.
bars[].toToRequired. Safe integer.
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": {
    "opening": 10,
    "minimumChange": -2,
    "maximumChange": 3,
    "count": 2,
    "subtotalAfter": [
      2
    ],
    "seed": 42
  },
  "output": {
    "changes": [
      1,
      0
    ],
    "closing": 11,
    "bars": [
      {
        "kind": "change",
        "after": 1,
        "from": 10,
        "to": 11
      },
      {
        "kind": "change",
        "after": 2,
        "from": 11,
        "to": 11
      },
      {
        "kind": "subtotal",
        "after": 2,
        "from": 0,
        "to": 11
      }
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • Subtotal positions are distinct and cannot exceed the change count. Values share a caller-chosen numeric scale and have no implied financial meaning; chart geometry and formatting remain with the renderer.
  • 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 Waterfall Change Dataset Generator — tool.io

  2. Calculation or validation: list/cumulative-sum — tool.io

Similar or alternative tools