Description
Populate an explicit half-open calendar interval with synthetic counts from supplied ISO-weekday ranges and calendar positions without choosing display bins or colors.
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.
Populate an explicit half-open calendar interval with synthetic counts from supplied ISO-weekday ranges and calendar positions without choosing display bins or colors.
When to use this tool
Use this generator to create reproducible activity heatmap calendar 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, endDateExclusive, weekdayRanges 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, totalCount, activeDays, maximumCount. Use the conventions below. Keep answer-bearing fields separate when presenting an exercise.
Generate every date in the supplied half-open window, delegate ISO weekday and year-calendar placement, and draw an inclusive count from that weekday's range. Return month/week-of-month positions, total, active days, and maximum count.1
Delegated operations used for this result: iso weekday; year calendar. 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. |
| endDateExclusive | End Date Exclusive | Required. Text. |
| weekdayRanges | Weekday Ranges | Required. Array of Object; no unknown keys.; minimum items 7; maximum items 7. |
| weekdayRanges[].minimum | Minimum | Required. Safe integer; minimum 0. |
| weekdayRanges[].maximum | Maximum | Required. Safe integer; minimum 0. |
| 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 366. |
| days[].date | Date | Required. Text. |
| days[].isoWeekday | Iso Weekday | Required. Safe integer; minimum 1; maximum 7. |
| days[].month | Month | Required. Safe integer; minimum 1; maximum 12. |
| days[].weekOfMonth | Week Of Month | Required. Safe integer; minimum 1; maximum 6. |
| days[].count | Count | Required. Safe integer; minimum 0. |
| totalCount | Total Count | Required. Safe integer; minimum 0. |
| activeDays | Active Days | Required. Safe integer. |
| maximumCount | Maximum Count | Required. Safe integer; minimum 0. |
| 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": "2024-02-28",
"endDateExclusive": "2024-03-02",
"weekdayRanges": [
{
"minimum": 0,
"maximum": 2
},
{
"minimum": 1,
"maximum": 3
},
{
"minimum": 2,
"maximum": 4
},
{
"minimum": 0,
"maximum": 1
},
{
"minimum": 4,
"maximum": 6
},
{
"minimum": 0,
"maximum": 0
},
{
"minimum": 0,
"maximum": 0
}
],
"seed": 42
},
"output": {
"days": [
{
"date": "2024-02-28",
"isoWeekday": 3,
"month": 2,
"weekOfMonth": 5,
"count": 3
},
{
"date": "2024-02-29",
"isoWeekday": 4,
"month": 2,
"weekOfMonth": 5,
"count": 0
},
{
"date": "2024-03-01",
"isoWeekday": 5,
"month": 3,
"weekOfMonth": 1,
"count": 6
}
],
"totalCount": 9,
"activeDays": 2,
"maximumCount": 6,
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- Weekday ranges align Monday through Sunday and the window is at most 366 days. Counts are synthetic rather than observed activity and no calendar or heatmap is rendered.
- 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 Calendar Seasonal Intensity Dataset Generator
Generate date-specific synthetic intensity ledgers from explicit weekly or periodic offsets, baseline and nonnegative integer noise.
- Random Bubble Size Scale Dataset Generator
Sample supplied values into explicit radius or area encodings with zero support and a declared negative-value policy.