Changes between Version 74 and Version 75 of DataTakingMainPage


Ignore:
Timestamp:
03/02/16 07:00:52 (10 years ago)
Author:
dneise
Comment:

merging Datataking sub points 3 and 4, as proposed by DD.

Legend:

Unmodified
Added
Removed
Modified

  • DataTakingMainPage

    v74 v75  
    106106 - dimctrl --quit --command ".js scripts/updateSchedule.js" (javascript via command)
    107107 - dimctrl --quit --command "DRIVE_CONTROL/UNLOCK" (single command)
    108 - Monitor the system and in special the currents
    109  - limits for the currents are defined in the DatatakingLimits
    110  - if the limits for the currents are exceeded you have to stop datataking:
    111  - stop the script (dimctrl --stop from a bash)
    112  - stop Trigger (MCP/STOP or FTM_CONTROL/STOP_TRIGGER
    113  - ramp down the voltage (BIAS_CONTROL/SET_ZERO_VOLTAGE)
    114  - close open files (FAD_CONTROL/CLOSE_OPEN_FILES)
    115  - adapt your schedule (edit ~/operation/scripts/schedule.js) and update the schedule (dimctrl --quit --cmd ".js scripts/updateSchedule.js") Note, that only entries which are schedules for *now* or the future are transferred to the database. All previous entries stay like they are.
    116  - you can write also your own schedule file and transfer its content to the database by given the filepath to the command: (dimctrl --quit --cmd ".js scripts/updateSchedule.js file=<!pathToScheduleFile>")
    117 - Be aware of all other DatatakingLimits
     108- Monitor the system be aware of the DatatakingLimits
    118109- 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
    119110- To control the hardware remotely, please have a look at RemoteControlHardware