Description
Advance two fictional moon phases under fixed periods.
Story planning separates the order of telling from fictional chronology, continuity records and practical writing budgets. Explicit labels, counts and invented calendar rules can make a local convention consistent without deciding narrative quality or inferring facts from manuscript prose.
Advance two fictional moon phases under fixed periods.
When to use this tool
Use Fictional Calendar Two Moon Phase Offset when checking a supplied story-continuity, chronology, calendar or drafting-budget convention.
How to use the tool and how it works
- Enter elapsedDays, firstPeriod, secondPeriod, firstInitialPhase, secondInitialPhase. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read firstPhase, secondPhase, separation. Use the output convention below.
Advance two fictional moon phases under fixed periods. Require positive periods and initial phases in [0,1); each phase wraps initial+elapsedDays/period modulo one, and separation wraps second-minus-first.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| elapsedDays | Elapsed Days | Required. Finite number. |
| firstPeriod | First Period | Required. Finite number; strictly above 0. |
| secondPeriod | Second Period | Required. Finite number; strictly above 0. |
| firstInitialPhase | First Initial Phase | Required. Finite number; minimum 0; strictly below 1. |
| secondInitialPhase | Second Initial Phase | Required. Finite number; minimum 0; strictly below 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| firstPhase | First Phase | Required. Finite number. |
| secondPhase | Second Phase | Required. Finite number. |
| separation | Separation | Required. Finite number. |
{
"input": {
"elapsedDays": 6,
"firstPeriod": 12,
"secondPeriod": 24,
"firstInitialPhase": 0,
"secondInitialPhase": 0
},
"output": {
"firstPhase": 0.5,
"secondPhase": 0.25,
"separation": 0.75
}
}Limitations and assumptions
- Phases are cycle fractions and days must match periods; this is a fictional periodic model, not astronomical ephemerides.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use the manuscript, scene outline and the chosen style/calendar policy for a complete editorial review; interpret numerical budgets in their narrative context.
References
Similar or alternative tools
- Fictional Calendar Cycle Phase Token
Return a fictional calendar's cycle and nonnegative phase.
- Fictional Calendar Leap Rule Step
Apply a caller-defined fictional leap-year divisibility rule.