Ignore:
Timestamp:
03/26/12 03:00:38 (13 years ago)
Author:
Jens Buss
Message:
added check if bias, feedback, drive and fad are in the correct state to write data
File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/FACT++/ScriptsForDimCtrl/ResumeDataTaking

    r13186 r13218  
    1414
    1515#Data Taking with Full Trigger Area (4x5min)
    16 
     16.x ScriptsForDimCtrl/IsReadyForDataTaking
    1717.! echo `date -u`  "taking Data:FullTriggerArea 5min Run 1 ..." >> ~/FACT++/ScriptsForDimCtrl/DataTaking.log
    1818MCP/START 300 -1 data
    … …  
    2121.! echo `date -u`  "... done" >> ~/FACT++/ScriptsForDimCtrl/DataTaking.log
    2222
     23.x ScriptsForDimCtrl/IsReadyForDataTaking
    2324.! echo `date -u`  "taking Data:FullTriggerArea 5min Run 2 ..." >> ~/FACT++/ScriptsForDimCtrl/DataTaking.log
    2425MCP/START 300 -1 data
    … …  
    2728.! echo `date -u`  "... done" >> ~/FACT++/ScriptsForDimCtrl/DataTaking.log
    2829
     30.x ScriptsForDimCtrl/IsReadyForDataTaking
    2931.! echo `date -u`  "taking Data:FullTriggerArea 5min Run 3 ..." >> ~/FACT++/ScriptsForDimCtrl/DataTaking.log
    3032MCP/START 300 -1 data
    … …  
    3335.! echo `date -u`  "... done" >> ~/FACT++/ScriptsForDimCtrl/DataTaking.log
    3436
     37.x ScriptsForDimCtrl/IsReadyForDataTaking
    3538.! echo `date -u`  "taking Data:FullTriggerArea 5min Run 4 ..." >> ~/FACT++/ScriptsForDimCtrl/DataTaking.log
    3639MCP/START 300 -1 data
Note: See TracChangeset for help on using the changeset viewer.