Changes between Version 76 and Version 77 of DataTakingMainPage


Ignore:
Timestamp:
05/24/16 15:12:38 (9 years ago)
Author:
smueller
Comment:

update on observation schedule policy and procedure

Legend:

Unmodified
Added
Removed
Modified
  • DataTakingMainPage

    v76 v77  
    6161=== Schedule ===
    6262
    63 - fill the schedule according to the thread "observations (month yyyy)" in the [[https://www.fact-project.org/logbook/forumdisplay.php?fid=5|shift]] forum
    64 - use the [[https://fact-project.org/scheduling/scheduling.php|visibility and current prediction plots]] to plan the sources to observe
    65 - for finding a good position for a [[SpecialRatescans|ratescan]], you can use software planetariums like stellarium or KStars
    66  - good position for a [[SpecialRatescans|ratescan]]: zd < 10°, no bright star in the field of view
    67  - a tutorial for choosing a position with xephem can be found in this [[https://www.fact-project.org/logbook/showthread.php?tid=1771|thread]] in the shift forum
    68  - A detailed explanation of the different ratescan-types that can be scheduled is given [[SpecialRatescans|here]]
    69 - edit ~/operation/scripts/schedule.js
    70  - you can find the formate of the schedule in the ScheduleTemplate
    71  - don't forget to change the date of the observation tasks
    72  - schedule the startup ~10 minutes before start of astronomical twilight, the first source observation 1 minute after start of astronomical twilight and the shutdown ~8 minutes before end of astronomical twilight
    73  - you can find the start and end of the astronomical twilight in smartfact->weather->sun
    74  - you can add several tasks to one observation, for example a [[SpecialRatescans|ratescan]] following by normal datataking
    75  - if you specify the coordinate, notice: ra is in decimal hours and dec in decimal degree
     63The observation schedule is filled on the [[http://www.fact-project.org/schedule/|shedule web site]]. A automatic observation scheduler fills in a first educated guess for each night.
     64The reasoning of the automated observation scheduler can be found [[http://www.fact-project.org/dch/scheduling.php|here]], by pressing the '+' sign next to 'Suggested Schedule'.
    7665
    77 **Remark**: When there is no time left for a first-drs-calib until the start of astronomical twilight, please skip it (i.e. the single pe run), as data taking has first priority.
     66- We take a look at the suggested schedule and report and modify the schedule in case the automatic observation scheduler obviously fails.
    7867
    79 6. insert schedule to database either from https://www.fact-project.org/schedule/ or with dimctrl: in /home/fact/operation : dimctrl --quit --cmd ".js scripts/updateSchedule.js"
    80 0. Check status of the Telescope in the TPoint Camera (in cosy on aux; switchable on 10.0.1002.30 La Palma Network (-> you need vpn connection)) or Lid Camera http://fact-project.org/cam/lidcam.php and the [[https://fact-project.org/cam/index.php|IR Camera]]
     68In addition to the educated guess of the automatic observation scheduler, we need to fill in a ratescan observation.
     69
     70- We add a ratescan observation to the [[http://www.fact-project.org/schedule/|schedule]] which should take place around mid night.
     71 
     72To find a good dark patch to look at during the ratescan we use e.g. the [[https://github.com/fact-project/darkspot|darkspot]] finder.
     73To gain most out of the multi wavelength observations, we want to adopt our observation schedule to overlap with the [[http://swift.gsfc.nasa.gov/|SWIFT]] [[http://www.fact-project.org/scheduling/2016/05/24/swift.schedule.formated|observation schedule]]
     74
     75When SWIFT is observing one of our scheduled sources during FACT's observation window, then we modify the FACT observation schedule to maximize the temporal overlap of SWIFT and FACT. A short summary of SWIFT and FACT overlap can be found [[http://www.fact-project.org/dch/scheduling.php|here]] when clicking on the '+' sign next to 'from Swift Schedule'.
     76
     77- We take a look in the [[http://www.fact-project.org/scheduling/2016/05/24/swift.schedule.formated|SWIFT schedule]] and adjust the [[http://www.fact-project.org/dch/scheduling.php|FACT schedule]] to maximize observation overlap.
     78
     79Now the schedule is ready. For more details on scheduling look [[https://trac.fact-project.org/wiki/Protected/Observations|here]].
     80
     816. Check status of the Telescope in the TPoint Camera (in cosy on aux; switchable on 10.0.1002.30 La Palma Network (-> you need vpn connection)) or Lid Camera http://fact-project.org/cam/lidcam.php and the [[https://fact-project.org/cam/index.php|IR Camera]]
    81820. Check status in the container (via the program temperature or munin)
    8283 - if the temperature in the container exceed 40°C don't start the drive