burstfile /rotse/run/etc/burst.conf # Burst data logfile
live_days 3 # Number of days to follow up burst
fup_priority 10 # Priority of follow-ups
fup_trigger follow_up # imaging sequence for follow-ups
fup_sunel -15.0 # Max Sun elev. for follow-ups
powerlaw -1.5 # Assumed powerlaw for image intervals
fup_frac_change 0.1 # Predicted flux change to schedule followup
photfile /rotse/run/etc/landoltfields.conf # List of photometry fields
Each burst alert that is received is logged to the burstfile. For more information on the format of this file please see Section 4.5.
The scheduler will plan follow-ups for live_days after a burst. After that it is ignored in the burst file. The imaging sequence for a follow-up is described by the fup_trigger keyword. Currently set to 30 long exposures, see Section 4.4.1 for information on how to change this.
The timing of the follow-ups is based on an assumption of a power-law decay of index powerlaw. We only plan to image a burst when the counterpart has a chance to fade significantly. The minimum fractional change of the flux can be set with fup_frac_change.
After every burst response and burst follow-up, the telescope automatically takes an image of a photometry check field on the equator with a large number of Landolt standard stars. These fields are described in the photfile file. The photometry trigger sequence is described in Section 4.4.1.