wiki:DataTakingMainPage

Version 19 (modified by ftemme, 12 years ago) ( diff )

--

Data Taking Procedure - Main Page

Remarks

  • This is just a short introduction/summary for doing a shift. For more informations (and for becoming an expert) follow the links!!
  • There are always changes to the system. Therefore please check this pages and the ​shift forum regularly.
  • The system is being automatized more and more, but this doesn't mean that there is nothing to do anymore. Monitoring the system is very important.

Datataking Check List

DataTakingCheckList: Check List for a whole shift. Be aware that you have to read the following points also, not only the Check list!

Preparation

Preparation before going on shift:

Preparation before nightly shift

  • read ALL ​logbook and ​shift forum entries
  • start well in advance so that you still have time to contact the experts in case of problems or questions

Datataking entries

General remarks:

  • please fill the logbook in realtime, i.e. the entries should have the correct time stamps for better traceability of problems - otherwise, please note the time stamp when something happened
  • problems / information for single runs have to be inserted in the ​run-comment DB
    • these are for example:
    • fad losses
    • tracking stops
    • car flash
  • make a single entry for every measurement you do (one entry for every source, for every technical measurement ...)
  • insert following informations
    • weather: skybrightness, clouds, calima, ... i.e. any information that cannot be retrieved from the auxiliary files
    • write down how long what take and how much time you loose by treating problems
    • any problem with hardware or software, therefore write down exactly what you did
    • please report also mistakes or missing information in the manuals so that they can be fixed/added

TemplateNormalDatatakingSet

TemplateQuotingLogFiles

You can find the list of the taken runs at: ​https://www.fact-project.org/smartfact/#observations

Startup

Shift summary

The shift summary (first entry) has to contain the following information:

  • contact details
  • planned schedule
  • achieved schedule
  • problems
  • ORM alerts

See Template for Shift Summary

Schedule

  • edit ~/operation/scripts/schedule.js
    • you can find the formate of the schedule in the ScheduleTemplate
    • don't forget to change the date of the observation tasks
    • you can add several task to one observation, for example a ratescan following by normal datataking
    • if you specify the coordinate, notice: ra is in decimal hours and dec in decimal degree

Planning the schedule:

  • fill the schedule according to the thread "observations (month JJJJ)" in the ​shift forum
  • use the ​visibility and current prediction plots to plan the sources to observe
  • for finding a good position for a ratescan, you can use software planetariums like stellarium or KStars
    • good position for a ratescan: zd < 10°, no bright star in the field of view

Remark: When there is not first-drs-calib until the start of astronomical twilight, please skip it (i.e. the single pe run), as data taking has first priority.

Startup procedure:

  • start dimctrl client in any terminal: /home/fact/operation/dimctrl
    • PWR_CONTROL/TOGGLE_DRIVE
    • DRIVE_CONTROL/UNLOCK
    • stop dimctrl: .q
  • insert schedule to database: in /home/fact/operation : dimctrl --quit --cmd ".js scripts/updateSchedule.js"
  • Start TPoint-camera
    • visit the page 10.0.100.230 from the La Palma Network
    • Login and start the TPoint Camera
  • Check status of the Telescope in the TPoint Camera and the ​IR Camera
  • All other task of the startup are performed by the Main.js script (see first point of Datataking)

Datataking

  • start Datataking script from a bash with following command in ~/operation:
    • dimctrl --start scripts/Main.js
  • don't forget to write the corresponding logbook entries and the comments in the run-comment DB
  • if you have to start a dim-script for yourself, call it with following command from a bash:
    • dimctrl --batch ScriptsForDimCtrl/<scriptname>.dim
  • Be aware of the DatatakingLimits
  • If you have to track manually (the script sends the tracking commands, so the manually tracking is not needed normally), have a look at the CurrentPointingPositions
  • To control the hardware remotely, please have a look at RemoteControlHardware
  • For details of the different procedures of the datataking, see the DatatakingProcedures
    • be aware that all steps mentioned there are currently proceeded by the scripts and it is not needed to perform them manually.

Remark: Please have in mind that datataking has first priority, i.e. first restart the script, then do the logbook entry.

Trouble Shooting

  • never stop a not hanging program with ctrl+c
    • when a restart of the program is really necessary use .q instead
    • restarting a program is in most cases not a solution and only increase the risk to trigger more problems. So avoid restarting programs as long as possible
  • TroubleShooting

Most common problems:

Shutdown

  • After the shutdown task in the schedule was proceeded you have to do the the following task to finish the shutdown:
  • stop datataking script with following command from a bash:
    • dimctrl --stop
  • make sure that
    • no script is running
    • the bias is off
    • the trigger is off
    • the lid is closed
      • check TPoint Camera
      • stop TPoint Camera after check (via the page 10.0.100.230 from the internal network)
    • the telescope is parked
    • biasctrl disconnected
    • all logbook entries are finished
  • stop the drive by:
    • in dimctrl: PWR_CONTROL/TOGGLE_DRIVE
Note: See TracWiki for help on using the wiki.