Cen A (reservation 749302, T32) completed at 11:16 UTC, 34 minutes early
because the plan finished, not because of a fault: NGC5128 images are on
t32.itelescope.net:8032 and transaction 851344 billed 160 points. Balance
is now 2,097 of the original 2,638.
That second bill settles the billing question the 20 Jul note left open.
T32 billed 160 for a 120 min plan (2.00 h x 80) and T59 billed 381 for a
180 min plan (3.00 h x 127); both land exactly on the plan's exposure
total and neither lands on wall-clock time. So billing is per imaging
minute as originally documented, and the x1.6 wall-clock multiplier is
withdrawn from CAMPAIGN.md, TODO.md and NOTES.md. What is actually wrong
is the rate card's per-scope numbers, so each scope's rate now has to be
derived from its first real bill. The practical consequence is the
opposite of the old warning: the campaign is now heading to UNDER-spend
by roughly 800 points, so later planning sessions should add or lengthen
runs rather than trim them.
Queue #2 (Corona Australis on T8) is booked at last. The original
01:35-04:35 slot was confirmed dead by probing New.aspx, which answered
"Conflicting reservation. Start time must be later than 2:25 AM" (user
hajo's reservation 749207, exactly as the previous session predicted).
Rather than take the leftover 02:30-05:30, where the target sits 3.5 to
6.5 hours past the meridian, the run moved to the next night's evening,
2026-07-22 21:45 to 2026-07-23 00:45 SSO local, which brackets the ~22:30
culmination so all 115 minutes of imaging happen near the zenith. This is
the geometry of the previously rejected option (c) on the night of option
(b): (c) was only rejected because Cen A held the reservation quota, and
that expired when Cen A completed. Verified via Reservation/MySummary.aspx;
quota now 6:50 of 8:00.
The New.aspx probe is documented in plans/README.md as the way to test a
slot for conflicts, since the DayPilot grid renders client-side and shows
nothing to a plain HTTP fetch.
The Reservations Pilot app at reservations.itelescope.net is now mapped and
driven end to end: three-step WebForms flow (form GET, Refresh Plans
postback with plan+times selected which enables Confirm, then Confirm),
observatory-local times, 4-hour maximum, plan attachment causing iTelescope
to auto-start the run at reservation start, and the reschedule flag that
rebooks weather losses on the next free night. Crucial gotcha recorded: the
confirm modal returns OK even when nothing was created (first attempt
silently failed on the 4-hour rule), so verification against the grid is
mandatory.
Live reservations: 749227 (T59, NGC 6744, 00:05-03:45 SSO local 20 Jul),
749228 (T33, 47 Tuc test, 00:05-00:50 same night), 749229 (T33, NGC 6752,
00:05-00:50 following night). Ledger corrected: T59 moon discount is 0%
until 21 Jul (the earlier 25% figure came from a Utah scope's grid), so the
NGC 6744 estimate returns to ~240 pts. Monitoring crons replace the old
starter crons since the scheduler now fires the plans itself.
plans/ngc104-test.txt is the ACP observing plan for the free 30-minute proof
run on T33: NGC 104 / 47 Tucanae, L 4x120s + RGB 2x90s at Bin2 (~17 min
exposure, ~24 min with overhead), modelled on the account's previous
one-click plan format (decimal-hours RA, decimal-degrees dec, #shutdown at
end). Already uploaded to the scope's /plans/qisback/ folder and verified to
round-trip byte-identical.
plans/README.md is the runbook: the T33 ACP endpoint map (status JSON,
console read, scope connect, plan upload/run, logs), the verified upload
procedure, the not-yet-exercised acquire POST with its Windows-path plan
value, the 47 Tuc run window (second half of the SSO night, ~14:00-19:30
UTC), and the step-by-step session procedure including the open questions a
first live run must answer (scope-connect requirement, abort control).
state/TODO.md tracks the test as in progress.
