calculating sun seasons dates, solstice, equinox, as in the 17th century.
- User
calculating sun seasons dates, solstice, equinox, as in the 17th century.
- Assistant
Below is a 17th-century style recipe for finding the Sun’s solstices and equinoxes. In that era (roughly 1600–1700 AD) astronomers such as Kepler and G.D. Cassini used planetary tables (e.g. Kepler’s Rudolphine Tables, 1627) and the condition “Sun’s true ecliptic longitude λ = 0°, 90°, 180°, 270°.” One would:
- Pick an initial guess for the date.
- Compute the Sun’s mean longitude L₀.
- Compute the Sun’s equation of center C (elliptical correction).
- Form true longitude λ = L₀ + C.
- Adjust the date by Δt ≈ −(λ – λ_target)/(dλ/dt) and iterate.
Below is a worked-out outline (with modern constants for clarity) that reproduces the style of a 17th-c. computation.
1. Key definitions
Season start
• March (Vernal) Equinox: λ_target = 0°
• June (Summer) Solstice: λ_target = 90°
• Sept (Autumnal) Equinox: λ_target = 180°
• Dec (Winter) Solstice: λ_target = 270°Mean motion of Sun ≈ 360°/365.2422 ≈ 0.985647°/day
Epochs & calendars
• Catholic Europe used the Gregorian calendar (1582 AD onward).
• Protestant England (and colonies) stuck to the Julian calendar until 1752.
2. The algorithm (one target λ_target)
-
Initial guess
Choose a date near your expected solstice. E.g. for the March equinox use ~ March 21. -
Compute days since standard epoch
In modern form one might take
T = (JD – 2451545.0) / 36525
but 17th-c. tables often used an epoch like “Jan 1 1600 Julian” or the 1582 Gregorian reckoning. -
Mean longitude L₀
L₀ = L₀,epoch + 360 °·(d / 365.2422)
where d = days since epoch, and L₀,epoch ≈ 280° 41′ (for a J2000‐like epoch). -
Mean anomaly M
M = M₀ + n·d
with n ≈ 360°/365.2564 and M₀ set so that M = 0 at perihelion. -
Equation of center C
C ≈ (360°/π)·[ e·sin M + (e²/2)·sin 2M ]
with e ≈ 0.0167. -
True longitude
λ = L₀ + C (reduce modulo 360°) -
Correction
λ is a little off from λ_target. Since dλ/dt ≈ 0.9856°/day,
Δt ≈ − (λ – λ_target) / 0.9856 days
Add Δt to your date, and go back to step 2. After 2–3 iterations you converge to within minutes.
3. Example: March Equinox in 1650 (Gregorian)
- Guess: March 21 1650
- Compute d: days from epoch → ~18 736 days
- Mean longitude L₀: ≈ 280.46° + 360×(18736/365.2422) ≈ 359.2°
- Mean anomaly M: ≈ 357° (mod 360)
- Center C: ≈ (360/π)[0.0167·sin 357° + 0.00014·sin 714°] ≈ –1.8°
- λ = 359.2° – 1.8° = 357.4°
We want λ_target = 0°, so (357.4°→360°) we’re 2.6° too early. - Δt ≈ –(357.4–360)/0.9856 ≈ +2.6 days
New date ≈ March 23.6 1650. Iterate once more:
– Recompute L₀, M, C for March 23.6 → λ ≈ –0.4°
– Δt ≈ –(–0.4–0)/0.9856 ≈ +0.4 daysFinal ≈ March 24.0 1650 (UTC). In the 17th c., refinement via better tables would give about March 23 11 h UT.
4. Historical notes
• Before Kepler’s Tables (1627) one used Ptolemaic epicycles (e.g. Prutenic or Alphonsine Tables).
• Accuracy improved from ≈½ day down to minutes by the end of the 17th c.
• Local longitude and equation of time (diurnal parallax, refraction) were applied for local civil dates.
In practice today
If you simply need 17th-century equinox/solstice dates (Gregorian)
you’ll find that they still fall around:• March 20–21
• June 21
• Sept 22–23
• Dec 21–22…with drift of a few hours from year to year.
But to reproduce a 17th-c. astronomer’s workflow, you follow the steps above, using the tables and constants current at that time.
Feel free to let me know if you want:
– A worked example for another year (e.g. 1666).
– The full interpolation procedure with original epicycle tables.
– Calendar conversions (Julian ↔ Gregorian).
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.