LCO Schedule — MuSCAT-db

LCO

Target & Transit Windows

Target

Planet

Ephemeris source

RA, Dec (deg) —

Range start (UTC)

Range end (UTC)

t0 (BJD) —

Period (d) —

Duration (hr) —

Pre-ingress (min)

Post-egress (min)

Include padding in obs check

Site(s)

Twilight

Max airmass

Min lunar (deg)

Show

Windows are coarse scheduling bounds. t0 is usually BJD_TDB; the ≤8 min barycentric offset is absorbed by the padding above.

Window boundaries are always rounded to 5-minute intervals. When padding is 0 the rounded window may be slightly shorter than the transit visibility (floor for start, ceil for end). Verify for critical observations.

Imaging Request

Proposal ID

Instrument

Request name

Exp count

Site

Exposure times per band:

g (s)

r (s)

i (s)

z (s)

Settings:

Exp mode

Readout mode

Narrowband filters:

IPP value

Type

Obs type

Guiding

Defocus (mm)

Exp time (s)

Readout

Test budget (s)

These scheduling inputs are separate from the archive page.

Split Request (two-site relay)

Leg A site (ingress)

Leg B site (egress)

Each leg is an independent LCO booking. "Submit both" is not atomic — if leg B fails after leg A is booked, leg A stays booked (see the warning above); use "Submit Leg B only" to retry it. There is no automatic cancellation.

Single site request

Submitted Request Monitoring

Accepted requests are checked after their observing window. Final BANZAI products are downloaded incrementally; scan and database ingestion start after every raw frame has a level-91 counterpart.

Request	Target	Instrument	LCO state	Pipeline	Frames	Last update	Detail
Loading…

Chat …

No messages yet — say hello. Type @here to share this page, @name to notify someone, or @test for a message that isn't saved.