Changes between Version 34 and Version 35 of DataTakingMainPage

Timestamp:

11/14/13 02:19:59 (11 years ago)

Author:

ftemme

Comment:

--

DataTakingMainPage

@@ -39 +39 @@
 0.  [[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
 0. connect to the screen session on newdaq. See ScreenSessionHelpfulCommands for a list of helpful commands for screen sessions
-0. open VNC-session :04 on gui and VNC-session :02 on aux
+0. 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
 0. start the Shiftsummary in the logbook:
@@ -69 +69 @@
  - if you specify the coordinate, notice: ra is in decimal hours and dec in decimal degree
 
-**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. 
+**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. 
 
 10. start dimctrl client in any terminal: ''/home/fact/operation/**dimctrl**''
@@ -82 +82 @@
    - Login and start the TPoint Camera
 0. Check status of the Telescope in the TPoint Camera and the [[https://fact-project.org/cam/index.php|IR Camera]]
+0. 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
 0. All other task of the startup are performed by the Main.js script (see first point of Datataking)
  - The list of the ManuallyStartup is currently **not** needed
@@ -93 +95 @@
 - 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
+- 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