- T59 NGC 6744 (reservation 749227) ran 00:05-03:30 SSO local 20 Jul and billed
381 points (txn 851148), not the ~240 estimated. Full LRGB dataset verified on
the scope server (L 15x300s BIN1, R/G/B 7x300s each BIN2); preview JPEGs
checked: round stars, clean galaxy, no weather damage, so no refund claim.
- Rate correction in state/NOTES.md: history 'Time Used' equals wall-clock
session time (3h24m32s), and the effective rate was ~112 pts/hr wall /
~127 pts/hr exposure vs the 80/hr the UpdatePlan rate card predicted. All
existing queue estimates flagged ~1.6x low until more bills confirm the model.
- Both free T33 reservations (749228 47 Tuc, 749229 NGC 6752) expired unused:
no images, no logs; grid shows reschedule=No despite the flag being set at
booking. First-light test is still outstanding; plans remain uploaded on T33.
- Ledger, booked-reservations table and queue updated: balance verified 2,257
via GetAccountStatus; queue #1 (Cen A T32) missed its 21 Jul slot and needs a
new night.
The UpdatePlan page embeds each telescope's dark-of-moon base rate in a
data-default-rate attribute; effective rate = base x (1 - plan
AccessDiscount from DataService.svc/GetMyAvailablePlans) x (1 - moon
discount from a server-side illumination table, not yet extracted). Records
the computed Plan-40 rates for all 25 listed scopes, the billing model
(points per imaging hour, billed per minute of exposure time, overhead
unbilled), the walk-in rule (idle scopes need no reservation; the ACP flow
is identical to the free scopes with points deducting), and the Cloudflare
constraint on the reservation planner.
Records verified findings from a credentialed read-only recon of the
iTelescope portal (2026-07-18) in state/NOTES.md: the WebForms login flow,
the /DataService.svc JSON endpoints (GetAccountStatus, GetMyAvailablePlans,
ApplyPromoCode), the per-telescope ACP web servers behind HTTP auth
(tNN.itelescope.online / tNN.itelescope.net:80NN, confirmed on T33), the
Planner redirect to lookup.itelescope.online, and the per-site weather URLs.
Credentials themselves stay outside the repo.
state/TODO.md gains the next automation steps (map ACP endpoints, explore
the new planner, enumerate more DataService methods) and a campaign-impact
note: most Chile scopes plus several others are currently offline, including
recommended T71 and T73, so near-term work should target T33/T8/T32/T59 at
Siding Spring and status must be re-checked before any booking.
Adds TELESCOPES.md, a per-observatory review of every telescope on the
iTelescope.net network with a spec block and an assessment for each, a
'choosing a telescope' use-case table, and general observations (CCD to CMOS
migration, Bin2 software limits, elevation limits, network-side calibration).
Data sourcing:
- data/itelescope-telescopes.csv is a verbatim CSV export of iTelescope's
maintained specs Google Sheet (24 rows: 23 active scopes + T74 placeholder).
- The support article (Freshdesk 247371) supplied observatory groupings and
minimum elevation limits; it still lists T9/T19/T31/T69 which the sheet has
dropped - the review follows the sheet and records the discrepancy.
- go.itelescope.net is an authenticated app shell; nothing was scraped from it.
Also fills in the remaining state/ files: TODO (pending: T74 specs, retired
scope reconciliation, periodic sheet refresh), DECISIONS (source-of-truth
choice, single-document structure, no launchpad scraping), NOTES (refresh
command, CSV quirks), ARCHITECTURE (repo layout), and README.
