L01 settings

Višnjan (Tičan) · 45.2909°N 13.74930°E 381 m · 1.0-m f/2.9 reflector + CCD

L01 Višnjan (Tičan)

Observatories

L01 Višnjan (Tičan)

+ Add an observatory…

Observatories History

Site

L01

Edited

These values come from sites/L01.toml. Anything changed here is stored as an override of that file rather than written back into it — the file is where the reasoning lives, and a form cannot write a comment. A setting marked edited can be put back to the file's value at any time.

You are reading this signed out, so nothing here can be changed. Marking targets can be done with the shared credential; a change to where the telescope may point should have a person attached to it. Sign in.

Where the telescope can point

Two different kinds of restriction live here, and collapsing them into one “minimum altitude per direction” would be the easiest mistake on this page to make. An observatory with a light dome to the north types a high number, and either its northern targets vanish or its telescope is pointed into a wall. So they are kept apart, and each entry says why it exists — which is what tells you, six months from now, whether it is safe to relax.

The mask and wedges as they are currently saved. Change a value and this redraws before anything is written.

Horizon mask — soft. Warns, never removes.

Sector	Azimuth	Prefer above	Effect	Why
N	337.5–22.5°	any altitude	warned	Trieste's light dome, 41 km away at bearing 3°
NE	22.5–67.5°	20°	warned	observer: above 20° in the south and east
E	67.5–112.5°	20°	warned	observer: above 20° in the south and east
SE	112.5–157.5°	20°	warned	observer: above 20° in the south and east
S	157.5–202.5°	20°	warned	observer: above 20° in the south and east
SW	202.5–247.5°	30°	warned	TBD: never specified, interpolated between S and W
W	247.5–292.5°	40°	warned	observer: West = 40°
NW	292.5–337.5°	40°	warned	observer: Northwest = 40°

The azimuth edges are fixed 45° sectors and are not editable: the sector lookup is arithmetic rather than a search, so a mask with different edges would quietly be read through the old ones.

Keep-out wedges — hard. Removes, with no override.

Azimuth from	to (clockwise)	Below	Why
247.5°	45.0°	70°	mount/dome collision risk

The arc runs clockwise from the first azimuth. So 248° → 45° is west through north to north-east, the northern half — not the southern one. Reading it the other way round would cut most of a night's rows rather than a tenth of them. Clear every field in a row to remove that wedge.

Flat altitude floor	15.0 °
Zenith blind spot	none
Floor asked of MPC	20.0 ° Changing this clears this site's cached ephemerides, because MPC never sent the rows below the old floor.

What gets onto the board

Faintest magnitude	21.6 V
Sun below	-15.0 °
Moon at least	20.0 °
digest2 score at least	25
Arc at least	0.0 d edited
Not seen at most	4.0 d
Moving at least	0.7 ″/min
NEO-like orbits only	True
…meaning q below	1.3 AU
…or e above	0.5
Skip what this site already shot	True

The telescope

Field of view	2600 ″
Interpolate ahead	600 s Allows for slewing and settling.

How long to shoot for

Base integration	10.0 min
…at magnitude	18.0 V
…plus per magnitude	5.0 min
Never less than	1.0 min
Frames per target	36

Moving up to	Seconds per frame
5.0″/min	30 s
25.0″/min	15 s
50.0″/min	10 s
100.0″/min	5 s
200.0″/min	2 s
faster	1 s

The speed table is not editable here yet; it is a variable-length table and wants its own form. Change it in sites/L01.toml for now.

How the list is ordered

Default order	chronological
Arc saturates at	3.0 d
Counted as bright at	15.0 V
Weight — digest2	2.0
Weight — arc	1.5
Weight — magnitude	1.5

The night

Night rolls over at	11 :00 UT
Times shown in	Europe/Zagreb

Not editable here, and why

Observatory code	L01 — MPC computes every ephemeris for it
Parallax constants	0.704742 / 0.707169 — MPC's record of where the telescope is
Longitude	13.7493° — likewise
Plan directory	`plans/` — something outside this board reads it
Sector names	N, NE, E, SE, S, SW, W, NW

These are facts about where the telescope physically is, not preferences. Editing them here would not move the dome; it would only make every ephemeris wrong. If one of them is actually incorrect, it is MPC's record that needs fixing, and then the site's file.

Feedback