wiki:DataTakingMainPage

Version 35 (modified by ftemme, 11 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

Startup

  1. open Smartfact
  2. open the gtc-skycamera image and the weather station of Magic (see ​https://fact-project.org/). Also very helpful is the ING infrared skycam: ​http://catserver.ing.iac.es/weather/archive/concam/index.php
  3. open a ssh-connection to newdaq to submit scripts
  4. open the page ​http://www.fact-project.org/showlog/index.php (for checking the logfiles)
  5. ​Introduction for a VPN session gives a helpful introduction for a VPN session to La Palma
  6. connect to the screen session on newdaq. See ScreenSessionHelpfulCommands for a list of helpful commands for screen sessions
  7. open VNC-session on gui (address: 10.0.100.24,currently port :4) and VNC-session on aux (address: 10.0.100.22,currently port :1)
    • start GUI (if not already running): ~/operations/factGL
  8. start the Shiftsummary in the logbook:

Logbook - 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

  1. plan the schedule:

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
  • 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

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.

  1. start dimctrl client in any terminal: /home/fact/operation/dimctrl
    • Power Drive:
      • PWR_CONTROL/TOGGLE_DRIVE
    • unlock Drive:
      • DRIVE_CONTROL/UNLOCK
    • stop dimctrl: .q
  2. insert schedule to database: in /home/fact/operation : dimctrl --quit --cmd ".js scripts/updateSchedule.js"
  3. Start TPoint-camera
    • visit the page 10.0.100.230 from the La Palma Network
    • Login and start the TPoint Camera
  4. Check status of the Telescope in the TPoint Camera and the ​IR Camera
  5. Check weather conditions, by checking the informations from the magicweatherstation, from the tng dust measurement and from the GTC allsky camera
    • insert the informations (including the image from the allsky cam) in the logbook entry
  6. 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
  • if you have to start a dim-script for yourself, call it with following command from a bash:
    • dimctrl --batch ScriptsForDimCtrl/<scriptname>.dim
  • Monitor the system and in special the currents
    • limits for the currents are defined in the DatatakingLimits
    • if necessary you have to adapt the schedule
  • Be aware of all other 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.
  • You can find the list of the taken runs at: ​https://www.fact-project.org/smartfact/#observations
  • Monitor the ​ QLA-website and give an alert in case of high excess rates
  • don't forget to write the corresponding logbook entries and the comments in the run-comment DB:

Logbook - Datataking entries

General remarks:

  • Datataking has first priority, so first solve an occuring problem, then write the logbook entries
  • please fill the logbook as soon as possible (so first Problem solving, then immediatly logbook entries), so that the timestamp of the entries are correct
  • 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
    • please report also mistakes or missing information in the manuals so that they can be fixed/added
  • if a problem occurs, please write down following:
    • what happens, please do not only post the error message, but also some lines above
    • what you did, to solve the problem
    • how log you need to solve the problem

TemplateNormalDatatakingSet

TemplateQuotingLogFiles

Run comment DB - Entries

  • problems / information for single runs have to be inserted in the ​run-comment DB
    • these are for example:
    • fad losses
    • tracking stops
    • car flash

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

  1. After the shutdown task in the schedule was proceeded you have to do the the following task to finish the shutdown:
  2. stop datataking script with following command from a bash:
    • dimctrl --stop
  3. 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
  4. stop the drive by:
    • in dimctrl: PWR_CONTROL/TOGGLE_DRIVE

If you have to shutdown the hardware on the island, please look at HardwareManuallyShutdown

Note: See TracWiki for help on using the wiki.