laurence/itelescope
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Verify Cen A, book CrA on T8 for the 22 Jul evening, rebuild the rate model #15

Merged
laurence merged 1 commit from campaign-ledger-2026-07-21 into main 2026-07-21 12:44:40 +01:00
Conversation 0 Commits 1 Files changed 4 +105 -29
laurence commented 2026-07-21 12:43:50 +01:00
Owner
Copy link

What this is

The 21 Jul drain-campaign session: verify the Centaurus A run, place the Corona Australis booking that two previous sessions had to defer, and correct the points model now that a second real bill exists.

What was achieved

Cen A verified. Reservation 749302 on T32 ran 18:50-21:16 SSO local and finished 34 minutes early because the plan completed. Images are under /images/qisback/T32/NGC5128, transaction 851344 billed 160 points, balance is now 2,097.

The rate model is rebuilt, and the previous session's warning is withdrawn. Two bills now bracket the question and both land exactly on the plan's exposure total:

Scope Plan imaging Wall time Billed Per imaging hour
T59 180 min 3h24m32s 381 127 (0% moon)
T32 120 min 2h25m55s 160 80 (25% moon)

381 = 3.00 h x 127 and 160 = 2.00 h x 80, to the point. Billing is per imaging minute after all, so the x1.6 wall-clock multiplier is gone; the rate card's per-scope numbers are what is wrong, and each scope's rate now has to be derived from its first real bill. This flips the budget conclusion: the campaign is heading to under-spend by roughly 800 points, so future sessions should add or lengthen runs, not trim them.

Queue #2 booked. Probing New.aspx confirmed the original 01:35-04:35 slot was dead ("Conflicting reservation. Start time must be later than 2:25 AM", user hajo's 749207, exactly as predicted). Instead of the leftover 02:30-05:30 window, where Corona Australis is 3.5-6.5 h past the meridian, the run went to 2026-07-22 21:45 - 2026-07-23 00:45 SSO local, which brackets the ~22:30 culmination so all 115 minutes of imaging happen near the zenith. That is the geometry of the previously rejected option (c) on the night of option (b): (c) had only been rejected because Cen A was holding the reservation quota, which freed when Cen A completed. Verified in Reservation/MySummary.aspx; quota now 6:50 / 8:00.

Tools used

PowerShell Invoke-WebRequest against the WebForms portal (login, DataService.svc/GetAccountStatus, account/history.aspx, Reservation/MySummary.aspx), the three-step New.aspx reservation POST at reservations.itelescope.net, and HTTP-auth reads of the per-scope ACP servers on T8, T32, T33 and T59 for plan folders, image folders and system status.

Also noted

  • The T33 47 Tuc retry (749314) had not run yet at the time of this session: it starts 14:05 UTC. TODO records the verification step.
  • plans/README.md now documents the New.aspx GET 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 new reservation's id was not captured: the confirm response carries only ModalStatic.result("OK") and MySummary does not print ids.
## What this is The 21 Jul drain-campaign session: verify the Centaurus A run, place the Corona Australis booking that two previous sessions had to defer, and correct the points model now that a second real bill exists. ## What was achieved **Cen A verified.** Reservation 749302 on T32 ran 18:50-21:16 SSO local and finished 34 minutes early because the plan completed. Images are under `/images/qisback/T32/NGC5128`, transaction 851344 billed **160 points**, balance is now **2,097**. **The rate model is rebuilt, and the previous session's warning is withdrawn.** Two bills now bracket the question and both land exactly on the plan's exposure total: | Scope | Plan imaging | Wall time | Billed | Per imaging hour | |---|---|---|---|---| | T59 | 180 min | 3h24m32s | 381 | 127 (0% moon) | | T32 | 120 min | 2h25m55s | 160 | 80 (25% moon) | 381 = 3.00 h x 127 and 160 = 2.00 h x 80, to the point. Billing is per imaging minute after all, so the x1.6 wall-clock multiplier is gone; the rate card's per-scope numbers are what is wrong, and each scope's rate now has to be derived from its first real bill. This flips the budget conclusion: the campaign is heading to under-spend by roughly 800 points, so future sessions should add or lengthen runs, not trim them. **Queue #2 booked.** Probing `New.aspx` confirmed the original 01:35-04:35 slot was dead ("Conflicting reservation. Start time must be later than 2:25 AM", user hajo's 749207, exactly as predicted). Instead of the leftover 02:30-05:30 window, where Corona Australis is 3.5-6.5 h past the meridian, the run went to **2026-07-22 21:45 - 2026-07-23 00:45 SSO local**, which brackets the ~22:30 culmination so all 115 minutes of imaging happen near the zenith. That is the geometry of the previously rejected option (c) on the night of option (b): (c) had only been rejected because Cen A was holding the reservation quota, which freed when Cen A completed. Verified in `Reservation/MySummary.aspx`; quota now 6:50 / 8:00. ## Tools used PowerShell `Invoke-WebRequest` against the WebForms portal (login, `DataService.svc/GetAccountStatus`, `account/history.aspx`, `Reservation/MySummary.aspx`), the three-step `New.aspx` reservation POST at `reservations.itelescope.net`, and HTTP-auth reads of the per-scope ACP servers on T8, T32, T33 and T59 for plan folders, image folders and system status. ## Also noted - The T33 47 Tuc retry (749314) had not run yet at the time of this session: it starts 14:05 UTC. TODO records the verification step. - `plans/README.md` now documents the `New.aspx` GET 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 new reservation's id was not captured: the confirm response carries only `ModalStatic.result("OK")` and MySummary does not print ids.
laurence added 1 commit 2026-07-21 12:43:50 +01:00 
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.
laurence merged commit 6ba6024192 into main 2026-07-21 12:44:40 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: laurence/itelescope#15
No description provided.
Delete branch "campaign-ledger-2026-07-21"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?