Skip to content

Main content

Random Fictional Moon Illumination Calendar Generator

Generate dated fictional moon illumination from a sampled initial oriented phase and fixed cycle, folding elongation for the distant-Sun core.

Loading tool…

Description

Generate dated fictional moon illumination from a sampled initial oriented phase and fixed cycle, folding elongation for the distant-Sun core.

A physical-model fixture draws inputs under explicit units and delegates a stated idealized calculation. Computed values follow that model; they are separate from measurements, calibration, and environmental effects omitted by the assumptions.

Generate dated fictional moon illumination from a sampled initial oriented phase and fixed cycle, folding elongation for the distant-Sun core.

When to use this tool

Use this generator to create reproducible fictional moon illumination calendar 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 startDate, count, stepDays, initialPhaseDegrees, cycleDays 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 initialPhaseDegrees, cycleDays, dates. Use the conventions below. Keep answer-bearing fields separate when presenting an exercise.

Draw an initial oriented phase and cycle length, advance phase linearly with elapsed calendar days, fold phase to elongation from zero to 180 degrees, and delegate distant-Sun illuminated percentage. Label waxing, waning, or exact turning phases.1

Delegated operations used for this result: lunar phase illumination percent. Their calculation or parsing conventions apply to the corresponding result fields.2

Input fieldMeaning and unitsAccepted input
startDateStart DateRequired. Text; minimum UTF-16 length 10; maximum UTF-16 length 10.
countCountRequired. Safe integer; minimum 1; maximum 128.
stepDaysStep DaysRequired. Safe integer; minimum 1.
initialPhaseDegreesInitial Phase DegreesRequired. Object; no unknown keys.
initialPhaseDegrees.minimumMinimumRequired. Finite number; minimum 0; maximum 360.
initialPhaseDegrees.maximumMaximumRequired. Finite number; minimum 0; maximum 360.
cycleDaysCycle DaysRequired. Object; no unknown keys.
cycleDays.minimumMinimumRequired. Finite number; strictly above 0.
cycleDays.maximumMaximumRequired. Finite number; strictly above 0.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
initialPhaseDegreesInitial Phase DegreesRequired. Finite number; minimum 0; strictly below 360.
cycleDaysCycle DaysRequired. Finite number; strictly above 0.
datesDatesRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 128.
dates[].dateDateRequired. Text; minimum UTF-16 length 10; maximum UTF-16 length 10.
dates[].dayOffsetDay OffsetRequired. Safe integer; minimum 0.
dates[].orientedPhaseDegreesOriented Phase DegreesRequired. Finite number; minimum 0; strictly below 360.
dates[].elongationDegreesElongation DegreesRequired. Finite number; minimum 0; maximum 180.
dates[].directionDirectionRequired. Text; one of "waxing", "waning", "turning".
dates[].illuminationPercentIllumination PercentRequired. Finite number; minimum 0; maximum 100.
randomnessReplay source and normalized 32-bit seed, or null seed for an advancing context source.Required. Object; no unknown keys.
randomness.seedOptional safe-integer 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": {
    "startDate": "2024-02-01",
    "count": 5,
    "stepDays": 7,
    "initialPhaseDegrees": {
      "minimum": 0,
      "maximum": 0
    },
    "cycleDays": {
      "minimum": 28,
      "maximum": 28
    },
    "seed": 42
  },
  "output": {
    "initialPhaseDegrees": 0,
    "cycleDays": 28,
    "dates": [
      {
        "date": "2024-02-01",
        "dayOffset": 0,
        "orientedPhaseDegrees": 0,
        "elongationDegrees": 0,
        "direction": "turning",
        "illuminationPercent": 0
      },
      {
        "date": "2024-02-08",
        "dayOffset": 7,
        "orientedPhaseDegrees": 90,
        "elongationDegrees": 90,
        "direction": "waxing",
        "illuminationPercent": 49.99999999999999
      },
      {
        "date": "2024-02-15",
        "dayOffset": 14,
        "orientedPhaseDegrees": 180,
        "elongationDegrees": 180,
        "direction": "turning",
        "illuminationPercent": 100
      },
      {
        "date": "2024-02-22",
        "dayOffset": 21,
        "orientedPhaseDegrees": 270,
        "elongationDegrees": 90,
        "direction": "waning",
        "illuminationPercent": 49.99999999999999
      },
      {
        "date": "2024-02-29",
        "dayOffset": 28,
        "orientedPhaseDegrees": 0,
        "elongationDegrees": 0,
        "direction": "turning",
        "illuminationPercent": 0
      }
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • Dates are plain dates and this is a fictional constant-cycle model, not a lunar ephemeris, observing prediction, or local visibility estimate. Exact turning labels use exact numeric comparisons.
  • 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

  1. Tool behavior and example: Random Fictional Moon Illumination Calendar Generator — tool.io

  2. Calculation or validation: astronomy/lunar-phase-illumination-percent — tool.io

Similar or alternative tools