Laurence
cd3de71361
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.
4.2 KiB
4.2 KiB
TODO
The current state of play. Keep it honest and current; this is what the next session reads to know what to do. Move items between sections as they progress.
Done
- 2026-07-17: repo created on git.discworld.casa, Default Workflow scaffold copied in.
- 2026-07-17: specs sheet snapshotted to data/itelescope-telescopes.csv (24 scopes).
- 2026-07-17: TELESCOPES.md written: per-scope reviews for all 23 active telescopes plus a choosing guide (T74 noted as in commissioning, no specs published).
- 2026-07-18: TARGETS.md written: southern targets invisible from the UK (dec tiers from lat 51.5°N), matched to Q62/X07 scopes, seasonal booking calendar, and a July-August starter campaign (T33 free, T71 narrowband, T73 galaxy, T8 LMC later).
Done (recent)
- 2026-07-20: NGC 6744 on T59 SUCCEEDED (reservation 749227, txn 851148): full LRGB dataset on the scope server (L 15x300s BIN1, RGB 7x300s each BIN2), previews verified clean. Billed 381 pts (est was ~240: see the rate correction in NOTES.md). Balance now 2,257. Ledger updated in CAMPAIGN.md.
Done (recent)
- 2026-07-21 ~08:55 UTC: free T33 47 Tuc retry booked as reservation 749314 (grid-verified), third attempt at the first-light test, runs 14:05-14:50 UTC 21 Jul, costs 0.
Done (recent)
- 2026-07-21 11:40 UTC: Cen A on T32 verified COMPLETE (billed 160, NGC5128 images on the scope server), and queue #2 (Corona Australis on T8) booked for the night of 22 Jul, 21:45-00:45 SSO local, which brackets the target's culmination instead of chasing it down the western sky. Rate model rebuilt from two actual bills. Details in the CAMPAIGN.md session note.
In progress
- T33 first-light test on its THIRD booking (749314), which had NOT yet run as of 11:40 UTC 21 Jul: it starts 14:05 UTC. Verify after 14:50 UTC (images and logs on t33.itelescope.net:8033 were still empty/stale at 11:40, as expected). The two prior free reservations (749228, 749229) expired unused with reschedule=No; if 749314 also fails to run, stop rebooking and either walk it in (POST plan.asp per plans/README.md) or drop the free objective.
- CrA on T8 runs 11:45-14:45 UTC 22 Jul. Verify after 14:45 UTC: images under /images/qisback/T8/ on t8.itelescope.net:8008, then the actual bill from account/history.aspx into the ledger. This is the first T8 bill, so it also fixes T8's effective rate (card says 130/hr; trust nothing until observed).
- DRAIN CAMPAIGN ACTIVE (see CAMPAIGN.md): spend the full balance by 10 Aug, then cancel before the 12 Aug renewal (user confirmation required for the cancel itself). 541 of 2,638 spent; 2,097 remain. The x1.6 estimate multiplier is WITHDRAWN: billing is on plan imaging minutes, and per-scope rates must come from actual bills (T59 127/hr, T32 80/hr observed; the NOTES rate card is unreliable). On current numbers the campaign UNDER-spends by ~800: plan extra or longer runs, do not trim. Reschedule flag never sticks (grid always shows No): treat every reservation as one-shot and verify the morning after. Download the NGC 6744 and NGC 5128 data from data.itelescope.net before the 10 Aug cancellation sweep. Update the CAMPAIGN.md ledger after every session from account/history.aspx.
Pending
-
Automation: map the ACP web endpoints on a per-scope server (start with free T33) for plan submission and status; explore lookup.itelescope.online (the new planner); enumerate more /DataService.svc methods. Recon notes in NOTES.md.
-
Campaign impact (status seen 2026-07-18): T71 and T73 are offline (development/mount testing), as are T2, T17, T18, T20, T25, T30, T72, T74, T75, T80. T8, T33, T32, T59 at Siding Spring are operational. Re-plan the July-August campaign around T33 free time and Siding Spring scopes until the Chile rebuild finishes; re-check status before any booking.
-
Fill in T74 when iTelescope publishes its specs.
-
Reconcile the retired scopes (T9, T19, T31, T69): the support article still lists them but the maintained sheet does not; confirm status and note it.
-
Optional: per-telescope detail pages on support.itelescope.net (links in DECISIONS.md) hold photos and operational history if deeper entries are ever wanted.
-
Periodic refresh: re-export the Google Sheet and diff against data/ to catch new or changed systems.