Changes between Version 8 and Version 9 of DataTakingMainPage

Timestamp:

07/16/13 23:19:39 (11 years ago)

Author:

ftemme

Comment:

--

DataTakingMainPage

@@ -47 +47 @@
 
 - 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]]__
+- **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
@@ -104 +104 @@
 Startup procedure:
 
-- start dimctrl client in any terminal: [i]/home/fact/operation/[b]dimctrl[/b][/i]
+- start dimctrl client in any terminal: ''/home/fact/operation/**dimctrl**''
    - PWR_CONTROL/TOGGLE_DRIVE
    - DRIVE_CONTROL/UNLOCK
@@ -122 +122 @@
 - 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 datataking details]]
+ - 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
@@ -133 +133 @@
 == Trouble Shooting ==
 
-- [b]never[/b] stop a not hanging program with ctrl+c
+- **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 
@@ -155 +155 @@
  - 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