wiki:DataTakingMainPage

Version 3 (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 Information (and for becoming an expert) follow the links!!
  • There are always changes to the system. Therefore please check this pages and the [shift](</logbook/forumdisplay.php?fid=5> "shift-forum") forum regularly.
  • The system is being automatized more and more, but this doesn't mean that there is nothing to do anymore.<br> 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 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

Logbook entries

Shift summary

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

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

TemplateShiftSummary

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

[spoiler="Template for a normal Datataking Set"] [code="html"] Crab

| Wobble Position | runs | comments | Clouds and all sky pictures | |:----:|:---:|:-------:|:--------:| | 1 | | | | | 2 | | | | | 1 | | | | | 2 | | | | | 1 | | | | | 2 | | | | | 1 | | | | | 2 | | | |

[u]Problemsu

  • problem 1
    • details
    • solution
  • problem 2
  • ...

code spoiler

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

[spoiler="Template for quoting logfiles"] [code="html"] [quote='program/log file'] ~ this is an example for log file text which will be nicely formated with the three tildes around ~ quote code spoiler

Startup

the following steps are not really needed anymore: (you might just need it in case of problems)

  • connect to the screen session on newdaq. See ScreenSessionHelpfulCommands for a list of helpful commands for screen sessions)
  • open VNC-session :04 on gui and VNC-session :02 on aux
    • start GUI (if not already running): FACT++/factGL

Schedule

  • edit ~/FACT++/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

[spoiler="Template for schedule.js"]

[code="cpp"] var observations = [

{ date:"2013-03-13 19:44 UTC", observations:

[

{ task:'startup' }

]

},

{ date:"2013-03-13 19:50 UTC", observations:

[

{ task:'data', source:'Crab' }

]

},

{ date:"2013-03-13 23:58 UTC", observations:

[

{ task:'ratescan', ra:9.438888, dec:29.0 }, { task:'data', source:'Crab' }

]

},

{ date:"2013-03-14 00:45 UTC", observations:

[

{ task:'ratescan', ra:11.26888888, dec:28.4477777 }, { source:'Mrk 421'}

]

},

{ date:"2013-03-14 03:30 UTC", observations:

[

{ source:'Mrk 501'}

]

},

{ date:"2013-03-14 06:30 UTC", observations:

[

{ task:'shutdown'}

]

},

];

code

spoiler

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: [i]/home/fact/operation/[b]dimctrlbi
    • 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

Datataking

  • start Datataking script from a bash with following command in FACT++:
    • 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:
  • For details of the different steps of the datataking, see the datatakingdetails datataking details
    • be aware that all steps mentioned in the datataking details are currently proceeded by the scripts
    • the datataking details contain the archive of the datataking procedures

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

Trouble Shooting

  • [b]neverb 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
  • in dimctrl: PWR_CONTROL/TOGGLE_DRIVE
  • make sure that
    • the bias is off and disconnected
    • the trigger is off
    • the lid is closed
    • the telescope is parked
    • all parts of the ShutdownProcedure are proceeded correctly
Note: See TracWiki for help on using the wiki.