kskpi
and go to the data storage disk
ssh kskpi cd /u2/dataSet the $CRT variable to the correct local version
setenv CRT "/u2/DAQ/CosmicRayTelescope"Check if a run is currently going on:
ps -elafww | grep testmainIf that command does not find a running testmain, you can start a new run. Assuming that the CRT code is well-maintained on /u2/data you can use that version of the code. Otherwise you cd to your own CRT directory.
Define the scan parameters: start/end points in x and y,
number of triggers per point, step size in x/y.
You do that by editing making_todo.cpp
.
When you're happy with that file, create the run input file
g++ making_todo.cpp ./a.outThis command created a file called
todo_copy
.
Check if the contents are OK.
If so simply copy the todo_copy file
cp todo_copy todoNow check if the PERL script that starts runs is running
ps -elafww | grep plIf that command does find a running
run.pl
you're done.
If not, start a new script
perl run_new.pl >&! opfile < /dev/null &and you're done.
To avoid problems with power-outages it is a good idea to move the setup to the (0,0) location after the scan is done. When the controller is switched on after a power-outage it often "thinks" that it is located at (0,0) even though it still sits on the DIRC calibration PMT.
$CRT/ScanTests/special_cases/set_to_position.pl 0. 0.
Anytime you want to check a pad between scans, you can move the laser to a pad with the command (pad 24 in this example):
$CRT/ScanTests/special_cases/set_to_pad.pl 24
root -q -b -l $CRT/ScanTests/special_cases/execute_after_power_outage.C
Last significant update: Mar 31, 2008, | by Joe |