Repository navigation
Constraints Wishlist
Brett M. Morris edited this page Aug 20, 2015
·
20 revisions
When planning observations of your favorite targets, what constraints do you consider? Note: we're only looking for constraints that can be calculated analytically, for consideration for inclusion in the astroplan package (currently in development).
- Altitude constraints (i.e. imposed by telescope)
- i.e.: above 10 deg and below 85 deg altitude
- Airmass constraints
- i.e.: observable between airmass of 1 and 2
- Horizon map
- i.e.: map obstructions to views of the sky in particular directions due to trees, buildings, other domes, for example.
- Nighttime constraints
- i.e.: between civil/nautical/astronomical (-6/-12/-18 deg) twilights
- Between local-time hours
- i.e.: between 7pm and 10pm local time for all nights in December
- In first half/second half of night
- i.e.: can I schedule this observation into a first half in September?
- Moon separation
- i.e.: Moon must be separated from target by >30 deg
- Moon illumination fraction
- i.e.: Moon illumination fraction must be <0.5
- Moon duration options – have an option that allows moon above the brightness limit for a short period of time
- i.e.: moon illumination <0.5 for at least 3 hours
- Sun separation (for non-optical observers)
- Moon-planet separation
- Use
jplephemto get coordinates for moons and planets at particular times (use case: observe Titan).
- Use
- Planet phase
- Standard star availability
- Given a catalog?
- Generalized periodic events
- Inputs: epoch (
t0), period, event duration. (can be useful for eclipsing binaries, transiting exoplanets, variable stars...) - Ability to specify constraint in terms of phase
- Inputs: epoch (
- By magnitude (store this and other metadata on
FixedTarget)