Saros Cycle Eclipse Repeat Years
Saros 223 synodic-month mean timescale from explicit matched period/count, not geographic eclipse-repeat prediction or exact calendar years. Model only, not an ephemeris, measured stellar identity or observational guarantee.
Description
A repeat cycle can be represented by a number of matched synodic months.
A repeat cycle can be represented by a number of matched synodic months.1
That duration alone does not predict eclipse location, visibility or exact event timing. Use Saros Cycle Eclipse Repeat Years to evaluate the supplied inputs under the model explained below.
When to use Saros Cycle Eclipse Repeat Years
Use Saros Cycle Eclipse Repeat Years to evaluate the supplied inputs under the model explained below. Establish the units, measurement scope and model assumptions before entering values.
How to use Saros Cycle Eclipse Repeat Years and understand its results
- Establish the units, measurement scope and model assumptions before entering values.
- Enter Caller matched synodic month days, Caller cycle month count using the field table and validation rules below, then run the tool.
- Read Caller saros days, Caller saros julian years; interpret the units, signs, ordering and unknown-value placeholders described below.
- Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerMatchedSynodicMonthDays | Caller matched synodic month days | number | Required; constraints below |
| callerCycleMonthCount | Caller cycle month count | number | Required; constraints below |
Enter a positive matched synodic month duration in days and an integer month count 1–10000. Multiply for cycle days and divide by 365.25 for Julian years. No fixed 223-month cycle or eclipse ephemeris is installed.
cycleDays=monthDays×monthCount; JulianYears=cycleDays/365.25 Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| callerSarosDays | Caller saros days | number |
| callerSarosJulianYears | Caller saros julian years | number |
{
"input": {
"callerMatchedSynodicMonthDays": 29.530588853,
"callerCycleMonthCount": 223
},
"output": {
"callerSarosDays": 6585.321314219001,
"callerSarosJulianYears": 18.029627143652295
}
}Limitations and assumptions
That duration alone does not predict eclipse location, visibility or exact event timing. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use Max Central Eclipse Duration Minutes Lookup for a related task: Central-eclipse duration references depend on eclipse geometry and defined event type.
Use Planet Elongation Morning/Evening Classifier for a related task: East or west elongation gives a geometric side relative to the Sun.
References
-
Saros Cycle Eclipse Repeat Years — tool.io
Similar or alternative tools
- Max Central Eclipse Duration Minutes Lookup
Central-eclipse duration references depend on eclipse geometry and defined event type.
- Planet Elongation Morning/Evening Classifier
East or west elongation gives a geometric side relative to the Sun.