Telescope Trigger

While the Ranking task is intended to order candidates in priority order based on different criteria, the Trigger task makes sure this information is correctly made available to each follow-up facility. The format will vary between each telescope: For the SEDM we might ideally log directly into a target database and inject criteria, for SNIFS we generate a correctly formatted list that can be red e.g. by the SNIFS Warehouse scheduler. Other telescopes, like NOT and LCO, might intrinsically require manual input through call someone or logging in through a web interface. Most telescopes will want to have access to finding charts.

Someone also needs to consider adjusting priorities based on e.g. current weather. If the SEDM has been snowed out for a week, should we beg ePESSTO to target a SN even though it is not ideally suited for their position? Should we trigger LCO? This division between Ranking and Trigger is somewhat arbitrary, and could be changed, but for now that responsibility is put here.

Potential tools

• Find the best option to display visibility+weather for potential sites (Japanese Growth Group?, Warehouse?)
• Format candidate list according to telescope specifications.
• A clear way to motivate manual priority changes.

Can we create it this way?

-- JakobNordin - 13 Nov 2017