Review and reference of iTelescope.net remote telescopes
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. |
||
|---|---|---|
| data | ||
| docs | ||
| plans | ||
| state | ||
| .gitignore | ||
| CAMPAIGN.md | ||
| CLAUDE.md | ||
| README.md | ||
| TARGETS.md | ||
| TELESCOPES.md | ||
itelescope
Reference and review of the iTelescope.net remote telescope network: every telescope, its specs, what it is good at, and which one to book for a given target.
- TELESCOPES.md: the full review, grouped by observatory, with a "choosing a telescope" guide at the end.
- TARGETS.md: southern-sky targets invisible from the UK, matched to scopes and to the time of year to book them.
- data/itelescope-telescopes.csv: snapshot of the network's maintained specs sheet (source of truth for the numbers).
- state/: project state under the Default Workflow.
Sources: the iTelescope support article (telescope summary) and the network's maintained Google Sheet. The launchpad at go.itelescope.net is login-only.