Description
Generate date-specific synthetic intensity ledgers from explicit weekly or periodic offsets, baseline and nonnegative integer noise.
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 date-specific synthetic intensity ledgers from explicit weekly or periodic offsets, baseline and nonnegative integer noise.
When to use this tool
Use this generator to create reproducible calendar seasonal intensity 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
- Supply startDate, count, pattern, offsets, baseline, noise in the field shapes below. Set seed when you need an explicit replay.
- 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.
- Read days. Use the conventions below. Keep answer-bearing fields separate when presenting an exercise.
Generate consecutive plain dates and combine baseline, a weekly weekday-indexed or repeating offset, and inclusive nonnegative integer noise. Delegate ISO weekdays and retain each contribution beside intensity.1
Delegated operations used for this result: add days; iso weekday. Their calculation or parsing conventions apply to the corresponding result fields.2, 3
| Input field | Meaning and units | Accepted input |
|---|---|---|
| startDate | Start Date | Required. Text; minimum UTF-16 length 10; maximum UTF-16 length 10. |
| count | Count | Required. Safe integer; minimum 1; maximum 128. |
| pattern | Pattern | Required. Text; one of "weekly", "periodic". |
| offsets | Offsets | Required. Array of Safe integer; minimum 0.; minimum items 1; maximum items 32. |
| baseline | Baseline | Required. Safe integer; minimum 0. |
| noise | Noise | Required. Safe integer; minimum 0; maximum 1000000. |
| seed | Optional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed. | Optional. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| days | Days | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 128. |
| days[].date | Date | Required. Text; minimum UTF-16 length 10; maximum UTF-16 length 10. |
| days[].weekday | Weekday | Required. Safe integer; minimum 1; maximum 7. |
| days[].baseline | Baseline | Required. Safe integer. |
| days[].seasonal | Seasonal | Required. Safe integer. |
| days[].noise | Noise | Required. Safe integer. |
| days[].intensity | Intensity | Required. Safe integer. |
| randomness | Replay source and normalized 32-bit seed, or null seed for an advancing context source. | Required. Object; no unknown keys. |
| randomness.seed | Optional safe-integer replay seed; normalization and precedence are explained below. | Required. Safe integer. or Null. |
| randomness.source | Source | Required. 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.
{
"input": {
"startDate": "2026-10-19",
"count": 2,
"pattern": "weekly",
"offsets": [
2,
0,
0,
0,
0,
0,
0
],
"baseline": 3,
"noise": 1,
"seed": 42
},
"output": {
"days": [
{
"date": "2026-10-19",
"weekday": 1,
"baseline": 3,
"seasonal": 2,
"noise": 1,
"intensity": 6
},
{
"date": "2026-10-20",
"weekday": 2,
"baseline": 3,
"seasonal": 0,
"noise": 0,
"intensity": 3
}
],
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- Weekly offsets need exactly seven values indexed Monday through Sunday. Noise is one-sided from zero through noise, not centered Gaussian noise; the dataset is synthetic rather than a forecast of seasonal activity.
- A replay requires the same complete input and implementation. The stated sampling convention applies within its eligible space. A finite draw does not exhaust all possible outputs; repeats remain possible unless a distinct-selection rule is explicit.
- 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
Similar or alternative tools
- Random Activity Heatmap Calendar Dataset Generator
Populate an explicit half-open calendar interval with synthetic counts from supplied ISO-weekday ranges and calendar positions without choosing display bins or colors.
- Random Bubble Size Scale Dataset Generator
Sample supplied values into explicit radius or area encodings with zero support and a declared negative-value policy.