= 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:

- PreparationBeforeGoingOnShift

Preparation before nightly shift

- read ALL [[https://www.fact-project.org/logbook/forumdisplay.php?fid=2|logbook]] and [[https://www.fact-project.org/logbook/forumdisplay.php?fid=5|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 [[https://www.fact-project.org/run_db/db/run_comment.php|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 runs taken at: https://www.fact-project.org/smartfact/#observations

----

== Startup ==

- open Smartfact
- open the gtc-skycamera image and the weather station of Magic (see www.fact-project.org)
- open a ssh-connection to newdaq to submit scripts
- open the page http://www.fact-project.org/showlog/index.php (for checking the logfiles)
  - different logs can be checked by adding the name of the program, e.g. http://www.fact-project.org/showlog/?log=dimserver or https://www.fact-project.org/showlog/?log=magiclidar 
  - use your own account for this and not the fact user!
-  [[https://www.fact-project.org/logbook/showthread.php?tid=828|Introduction for a VPN session]] gives a helpful introduction for a VPN session to La Palma

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 [[https://www.fact-project.org/logbook/forumdisplay.php?fid=5|shift]] forum
- use the [[https://fact-project.org/scheduling/scheduling.php|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 [[https://fact-project.org/cam/index.php|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:
 - dimctrl --batch !ScriptsForDimCtrl/<scriptname>.dim
- For details of the different steps of the datataking, see the DatatakingDetails
 - 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 ==

- **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:

- [[troubleshooting#tsfadloss FAD losses]]
- [[troubleshooting#tsdrivectrl Drive Error ]]

----

== 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
    - check TPoint Camera
    - stop TPoint Camera after check (via the page 10.0.100.230 from the internal network)
 - the telescope is parked
   - check [[https://fact-project.org/cam/index.php|IR Camera]]
 - all parts of the ShutdownProcedure are proceeded correctly