G0 Backward angle :
How To and documents.
last updated: March 12, 2007
Web page maintained by Colleen Ellis:
Please submit any updates, changes or recommendations to
cellis@jlab.org.
We are updating this
page: your comments are very welcome.
-
Shift Basics
(What to do if you can't solve a
problem)
-
G0 Data Acquisition
-
G0 Data Analysis
-
|
$G0SCRATCH/scripts/Cerenkov/cer_threshold_scan
"run_number"
-
-
30 Hz electronic
-
-
-
EPICS variables
|
|
|
Analysis
Shift Task List and Instructions
Analysis Shift Task List and Instructions Updated 1 March for 687 LD2
*****************************************
(This task list should be performed once per shift. The person who does these tasks
should make a short report in the logbook upon completion of the tasks.)
I) Check that the raw data and analysis disks have enough free space.
1) Check the amount of free space:
df -k /data1 /data2 (in gzero@gzerol3)
The automatic systems are set to try to keep 70 Gb free on /data1
and /data2 (70% used).
2) If 95% of disk space is used:
a) Check for backup errors and resolve them as well as possible
(task (I) above).
b) Run the data_deletion script, starting with a deletion age of
60 days:
./data_deletion.pl -A 60
The script will remove data files that are older than the age
specified and that have been correctly backed up to the silo
c) Check the free space on /data1 and /data2
if there is not enough free space, then run the script again with
a lower deletion age (try 50, 40, etc.)
d) Make a g0log entry describing what you have done.
II) Check the progress of the Pass1 analysis in the data tracker, and run the
"integrity" script on the Pass1 output files to look for problems not
caught by the online analysis.
1) ssh gzero@cdaql# (#=4,5,6)
cd $G0SCRATCH/rootfiles
ls -lrt *Pass1*
If the time of the latest Pass1 file is +- 15 min, this is working fine;
if it's +- 2hrs, it's not.
2) $G0SCRATCH/scripts/run_summary_online 1 ##### G0Pass1
(1 to summarize entire run, ##### is run number)
Generates summary_#####.text files in:
/home/gzero/scratch/sum.
Look at these files to check that the data looks okay (no numbers that are
orders of magnitude different from the other numbers in a given column).
III) step deleted
IV) Check the "good_for" table for the runs taken since the last analysis checklist.
Update if needed.
1) to bring up the good_for GUI:
ssh gzero@cdaql# (#=1,2,4)
cd $G0DATABASE/perl/bin/
./good_for_GUI.pl -n g0dbserver -u g0replay -d gzero_687MeV_comm2 -p
(enter password)
2) to decide how to update the good_for GUI:
Read the run lists in the shift summary reports or the run entry titles
in the electronic log book. The "good for" column can (presumably) be
decided from the titles--if the data quality is not "good" the run
lists should say otherwise. NOTE: It is okay to label a run "good" and "bad".
Use both the "good" and "bad" label when some of the data is good, but there
was a problem, i.e. PZT scan during part of the run.
V) Data accounting: how much good data did we accumulate the previous day,
or altogether. Do we have a good IN/OUT balance?
1) To bring up the goat++ GUI:
cd $G0SCRATCH/scripts/G0DBPlotter
goat++
*************When you press "Get Runs", goat++ prints out the run numbers in the terminal
from which you launched it. Please note the final run number.*****************
2) Run coulomb counter:
(Under the "Beam" tab.
Use LH2.cnd as Run Condition File and select "No" for parity cuts. The
function plots the number of Coulombs of usable data, separated into IN
and OUT states, and prints these numbers to the window from which goat++ was opened.)
Run once for the entire 687MeV run. Put the output Coulomb numbers and the
plot into the log entry. Run the counter again, using only the runs since the
last analysis checklist was performed (include the Coulomb numbers in the log entry).
**Please put this run number range in the title of your log entry so that the next
analysis person knows where to start.
VI) Beam parameter asymmetries, lumi widths and G0/G0B plots for the period since the last checklist:
(All in the goat++ GUI, under the "Beam" tab.
Use LH2.cnd as Run Condition File and select "No" for Parity Cuts
and "Fraser" for Plot Type.)
1) "Individual Beam Parameter" w/ Beam type "hc"
2) "Individual Beam Parameter" w/ Beam type "whc"
3) "Lumi Monitors" w/ Beam type "whc"
4) "G0/G0B/H00 BPMs" w/ Beam type "hc"
VII) Run Locus Output function for the period since the last checklist:
(In the goat++ GUI, under the "Coincidences" tab.
Use "e" for particle, "elastic" for locus, "all" for octant
and "rcs" for measurement type.)
Check that the plots show values around 1 for the latest runs.
VIII) If the data looks bad, and there's a comment in the log, or the good for gui is marked as
high halo, etc, mark the run as either "not_all_good" or "bad", so that our coulomb
count reflects "good" runs.
IX) Remind the shift leader to look at the coincidence matrix generated by the realtime analyzer.
Also:
Routine special analysis projects: Carried out as needed
1) Check the PMT gains (specialist Maud/Philippe/Alex)
2) Prepare beam calibration files and insert them in the DB
(specialist Juliette/Stephanie/Riad)
3) Check PITA, IA, helicity magnet response slopes and
apply changes if needed (specialist Stephanie/Riad)
-- entries in database and integrity file
4) Check deadtime corrections and linear regression
slopes (Philippe/Christophe, Stephanie)
5) Monitor Cerenkov PE calibration w/ ARS (JSR/Alex/Larry)
.cnd and Database Names
Condition filenames:
Low energy runs: LH2low.cnd and
LD2low.cnd
High energy runs: LH2high.cnd and LD2high.cnd
Database Names:
gzero_362MeV_comm2 (low energy runs; both LH2 and LD2)
gzero_687MeV_comm2 (high evergy runs; both LH2 and LD2)
Top
of pageTop
of page
Which computers are used
for what?
DAQ: cdaql3 (Xserver, Moller
DAQ, Wire chamber
DAQ, login host, realtime analyzer)
gzerol3 (G0
DAQ, online analysis)
DO NOT USE THESE MACHINES FOR
ANYTHING ELSE!!
Automated Pass1 analysis: cdaql1, cdaql2, cdaql4
Specialized analysis:
cdaql4, cdaql5, cdaql6
Database manager:
cdaql6
THESE MACHINES ARE RESERVED FOR ANALYSIS SHIFT
TAKERS unless
otherwise indicated by the local analysis coordinator. Please do any
personal running
of g0analysis from your own account on the ifarm
machines. See the ¡°Howto¡±
section on
how to run your own analysis. Generally
it¡¯s OK to run root on any of cdaql4-6 without disturbing the analysis.
Top
of page
Below is an edited version of Alex's logentry:
http://hallcweb.jlab.org/hclog/0703_archive/070302163627.html
G0DBPlotter directory :
- tmpfigures/ directory with all the .jpg .png etc files not used by goat
- BACKUPcndFiles/ directory with the condition files that don't make sense anymore
- OtherTargetscndFiles/ directory where all the unusual target cnd files are stored
- RCScndFiles --cnd files with an rcs comment in them
main directory :
LD2_362_all.cnd
LD2_362_no_pions.cnd
LD2_362_pions.cnd
LD2_687_all.cnd
LD2_687_no_pions.cnd
LD2_687_pions.cnd
LH2_362.cnd
LH2_687.cnd
all : pion & random matrix included, i.e. every production run
no_pions : random matrix
pions : usual pion matrix used
(does not apply to LH2 runs)
The current default is: LD2_687_all.cnd
Top
of page
To
Generate MPS or QRT ntuples
To generate the mps and/or qrt ntuples when analyzing a run include the
appropriate flag and the octants for which you want to generate the ntuples.
Examples:
g0analysis -r 33333 --mpsntuple 1 --qrtntuple 3:5
generates the mpsntuples for octant 1 and the qrt-ntuples for octants 3 & 5
g0analysis -r 33333 --mpsntuple all
generates the qrt-ntuples for all the octants
g0analysis -r 33333 --qrtntuple 1:3:5:7 --mpsntuple all
generates the qrt-ntuples for the North American octants and the
mps-ntuples for all the octants
NOTE: To avoid overwriting another analysis run use the command
--outputstem name_of_analysis i.e. --outputstem G0mpsntuple
Rootfile from the Fall run are stored at:
/p/hallc-gzeroback/gzero_scratch/rootfiles_fall2000
Rootfiles from the Spring run are stored in:
/work/hallc/gzeroback/G0Scratch_Official/rootfiles
and are analysed with the actual analyser.
Also,
The rootfiles from a previous analysis
are on this work disk:
/work/hallc/gzeroback/gzero_scratch/rootfiles_spring2006/
I have moved the G0Scripts directory in the gzero account which we had
been using during the spring running period to the location:
/home/gzero/G0Analysis/G0Scripts_spring2006
I
have created a tar file of the contents
as of yesterday and put it at:
/home/gzero/G0Analysis/G0Scripts_spring2006_ORIG.tgz
The
current G0Scripts directory has been
freshly checked out from
CVS, is linked from $G0SCRATCH/scripts, and is located at:
/home/gzero/G0Analysis/G0Scripts
Top
of page
Problems can occur accessing the database when
the database server on wmg0 gets jammed up by zombie queries
and it can't keep up processing the new data being filled to
the primary database.
If you
have a goat process crash out, or if you kill a goat process,
please check to see if you have left a zombie query on the
database
server:
- mysql -h wmg0 -u g0 -p gzero_687MeV_comm2
- show processlist;
- The "show processlist" command will give you a list of commands
being run from the different machines trying to access the database.
You want to look for a process owned by the user "g0" with the host
being the machine you were using, and which has a command of "Query", a
state of "statistics", and a time which looks like it started about the
time that you started the action which got locked up. You may see some
other queries in "statistics" also. Depending on how old they are, they
may be other zombie processes; if you're sure they are, you could kill
them too. Almost nothing that the "g0" user can do is capable of
permanently messing up the database, so the only thing you need worry
about is killing someone elses analysis job.
- To kill a zombie query from the mysql prompt:
kill ####;
Where #### should be the query "Id" that you see in the processlist.
- In some rare cases, a particularly strong zombie will resist your
attempts to kill it. In these cases, contact a DAQ or DB expert who
will be able to kill the process from the admin or system level.
(Aren't you impressed that I was able to avoid making a joke about
fleeing for your life? Or at least I was until now?)
The problems in accessing the database for runs after 31401 (log entry
124158) were because
the database server on wmg0 had gotten jammed up by a few zombie
queries
and it wasn't able to keep up processing the new data being filled to
the primary database.
The two zombie queries look like they were from a defunct "goat"
process
on ifarml3. They had a running time of about 69541 and 61349 seconds,
so the first process would have been started at about 14:40 yesterday.
How
to stage raw data files
To do the analysis in your account on the
ifarm machines,
you will have to stage the raw data files, do:
jcache -g hallc
/mss/hallc/gzeroback/raw/filename.dat.0
where filename.dat.0 is the name of the
raw data file stored
in the Silo.
The jcache command will complete after a
while, you will receive
an email from jasmin telling you your file is ready.
Then you have to do:
/group/gzero/G0Analysis/bin/update_cache_links.pl
-S
/cache/mss/hallc/gzeroback/raw
to update your $G0SCRATCH/data directory with all the links. After
that you can just analyze the data.
Top
of page
Prescales can only be
changed from
gzerol3. Other accounts do not have permission to modify the
prescale files,
or any of the other configuration files.
To use g0daq_config.pl, you should do the
following:
ssh gzero@gzerol
~/SCRIPTS/g0daq_config.pl
Whenever you try to change the
prescales
and you think it isn't working,
you should push the "Revert" button. That button will refresh the
display with the current values in the prescale file, so you will be
able to tell if your changes are going through.
If that doesn't work, you have other
problems and should contact a DAQ
expert.
How to
do analysis during your shift
During your shift :
- For each run:
- Regularly:
How to look at
data Real Time (as the data is aken)
What
to look for during the Summer 2006 Run
If you have questions.....
For a definition of realtime analysis
compared to other sort of analysis : read
this.
There are two sorts of realtime analysis : feedback and event display.
Both of them are automatic so you don't have to do anything but just
check that the automatic processes are going on and look at the data
(also take apropriate actions when needed !). The automation is managed
by the
analysisminder.
It does usually run of the cdaqs1 screen (at the right of the daq
machine).
- The system is up and running if :
- the ET system is connected and its heartbeat is updating
- the realtime analysis running time is updating
- the feedback analysis running time is updating
- the G0 realtime monitor is launched (upcoming : a sample a
standard plots)
- If
you need to restart the analysis minder : follow
those instructions very very carefully. The
analysis
minder is under gzero@cdaql3:SCRIPTS/analysis_minder.pl. After
finishing the last step in the instructions ("launch the real time
analyzer"),log in to the gzero account on cdaql3. From there,
run: SCRIPTS/analysis_minder.pl
HOW TO LOOK AT
DATA ONLINE (Just after the data have been taken)
For a definition of online analysis compared to other sort of
analysis : read this.
After 50K event are acquiered in the run in progress, an automatic
replay is launched (with the option --hists). The code output a
rootfile under:
/home/gzero/scratch/rootfiles/G0Online.#####.root
, where #### is the run number. A script analyzes this file and
produces a ascii file with some important infos concerning the health
of the data taking. The file is under :
/home/gzero/scratch/tmp/G0Integrity.#####.dat
Troubleshooting:
- If the text file shows a lot of NULL data and tells you that the
beam intensity is null but you know it was not, it is probable that the
events don't go through the beam cuts : the beam is too low (less than
5uA), the beam is at the bad position, or the data flow is corrupted
(most likely). If the beam intensity is larger than 5uA and the beam is
at nominal position, your best bet is to restart CODA and analysis
processes in order (do
this).
- You can also look at the same
analysis on the full run. The data are automatically replayed at the
end of the run. The root files are /home/gzero/scratch/rootfiles/G0Pass1.#####.root to
produce the integrity file, go to /home/gzero/scratch/scripts, type run_summary_online 1 ##### G0Pass1. THe code will tell you where the file
is written.
Future of this analysis:
When we will be in a production mode, this script will compare the data
to golden values. This is not done yet...
HOW TO BRING
UP THE STRIP TOOL
Login as cvxwrks@cdaqs3 (no need for password if you are running
from SLOW CONTOL)
TYPE: cd MEDM/GO
TYPE:
StripCharts.sh
--Everything for shift summary snapshots should appear!
If you like to play with StripTools type "striptool" at MEDM/GO
directory. The display will plot your variable from the time you start
the GUI. With this method, you cannot retrieve values that are older
than
the time at which you start the GUI. If you use these charts, you
can change the vertical scale by increasing/decreasing the size of the
strip tool chart--for more precision, see the last paragraph of this
section.
Default place for saving predefined configurations of global
interests is
~/MEDM/G0/stripdir.
NOTE: "striptool" is able to run only on SUN environment!. Default
extension should be strip, but it is obsolate.
See StripCharts.sh to get idea how start StripTool in batch mode!
Also--another location for many G0 strip charts (and one that allows
easy change of y-axis scale:
logged as cvxwrks@cdaqs3 (note, can be any "s" machine, i.e.
cdaqs3)
cd /MEDM/beam
type: striptool
The desired directory is:
/net/cdaqfs/home/cvxwrks/users/willy
Then load the file you would like to see.
To change the y-axis scale, use the strip control tool that opens
automatically after the file is loaded. Select the tab labeled
"curves". Then selected the "modify" button. This allows
you to select the min and max values of the y-axis.
HOW TO
DO DISPLAY THE BEAM TRAJECTORY THROUGH THE HALL
logged as cvxwrks@cdaqs1:
cd g0beampos
type: paw
at the prompt, hit return
type: exec plot_traj
This display reads the current epics values and display them.
HOW TO
DO SPECIAL ANALYSIS
How
to analyze a Fastbus run
Analyze
harps scan data
Scripts that uses the g0 histograms:
all the common scripts are under : /home/gzero/scratch/scripts
most of them need a replay of the data with the option --hists
- Scales_Viewer.C
: scalers, coincidence matrix, multihit for one run, one octant
DisplayOctant(const
int NumRun, const int NumOctant, TString replay="G0Pass1",Bool_t
knorm=kTRUE)
if knorm=kFALSE, no normalization is done
display
example
- Scaler_mult_octant.C :
for one run, all the octants, displays cerenkov or direct or
non-conditioned scaler or elec coincidence or pion coincidence,
electron matrix, pion matrix.
All either for CED or FPD
display(Int_t
run, TString opt, TString type,TString replay, Int_t logy=0)
-opt is : cer, d (for direct), ncd
(non-conditional direct), ecd (electron conditionned), picd (pion
conditionned), ematrix, pimatrix
-type is : CED or FPD (if opt is
cer, ematrix or pimatrix, type is ignored)
-replay is the name of the
rootfile (GOOnline,GoReplay, G0Scaler..)
-logy=0 diplays linear, 1 displays
logarithmic.
display
example
- locus.C : for
one run, one octant displays the electron or pion
matrix as well as the counts for each CED as a function of the FPDs.
locus(Int_t
runnumber, Int_t octant,
TString type, TString name="")
- type is "e" or "pi".
- name is the name of the rootfile
(GOOnline,GoReplay,
G0Scaler..)
display
example
- Fastbus viewers :
author P.Pillot. Under /home/gzero/scratch/scripts/G0Analyse
CED_ADC_Viewer.C :CED_ADC_Viewer(const int NumRun = -1,
int NumOctant = -1, int MaxNbEvent = -1, int DFC_Threshold = 0, int
MT_Threshold = 0)
CED_TDC_Viewer.C
: CED_TDC_Viewer(const int
NumRun = -1, int NumOctant = -1, int MaxNbEvent = -1)
CED_MT_Viewer.C
:CED_MT_Viewer(const int NumRun =
-1, int NumOctant = -1, int MaxNbEvent = -1)
FPD_ADC_Viewer.C :
FPD_ADC_Viewer(const int NumRun =
-1, int NumOctant = -1, int MaxNbEvent = -1, int DFC_Threshold = 0, int
MT_Threshold = 0)
FPD_TDC_Viewer.C
: FPD_TDC_Viewer(const int
NumRun = -1, int NumOctant = -1, int MaxNbEvent = -1)
FPD_MT_Viewer.C
: FPD_MT_Viewer(const int NumRun
= -1, int NumOctant = -1, int MaxNbEvent = -1)
Cer_ADC_Viewer.C
: Cer_ADC_Viewer(const int
NumRun = -1, int NumOctant = -1, int MaxNbEvent = -1)
Cer_TDC_Viewer.C : Cer_TDC_Viewer(const
int NumRun = -1, int NumOctant = -1, int MaxNbEvent = -1)
- Beam Parameter vs Run number: author C. Ellis Under
/home/gzero/scratch/scripts/beam_vs_runnumber
Open the script using emacs.
Input the run numbers you are interested in,
i.e.
Int_t runnum [NUMRUN]={23988,
23999. 24005, 24006};
Change the constant NUMRUNS to the
number of runs you've entered, i.e
const Int_t
NUMRUNS = 4;
In line 173, put the names of the histogram parameters you're
interested
in, i.e.
TString
name[3]={"diff_x_targ","diff_y_targ","qrtave_q_targ"};
in root, load the script .L beam_vs_runnumber
type all() and you'll get your graphs.
Display example
HOW TO ENTER
THE RUN PURPOSE (in the database)
To start the GUI:
Log as gzero@cdaql*
cd $G0DATABASE/perl/bin
./good_for_GUI.pl -n g0dbserver -u g0replay -d gzero_687MeV_comm2 -p
(passwd on the white board)
To use the GUI:
- Press the "Update Runs" button to
update the list of available runs. The largest run number is
automatically selected at this point. This must be done after the run
has started on the RunControl in order to get the current run number
into the database.
- Select the run number to update from the left most column by clicking
on it.
- Select one or more values of goo_for values from the right most
column.
- Press the "Submit Changes" button to update the database. A given run
can be updated as often as needed.
DATABASE
The data base is the primary tool used to look at data fuly
replayed (offline). This is still under development.
name: gzero_687MeV_comm2
server: g0dbserver (if you have the g0 environement setuped), wmg0 or
uiuc2
user:g0user
maps : backanglenew, slowcontrol
How to run your own version of
g0analysis
What
is your own version of g0analysis compared to the one performed on the
gzero account ?
Anything
not replayed
automatically is your own g0analysis. During the run routinely,
three type of analysis are automatically taking
place : realtime (run from gzerol3, no root file output), Online (run
from gzerol3, root files under
gzero@cdaql*:$G0_ROOTFILES_DIR/G0Online.XXXX.root option --hists),
Pass1 (or Offline, run on gzero@cdaql1-2-3, root files under
gzero@cdaql*:$G0_ROOTFILES_DIR/G0Pass1.XXXX.root, option --hists).
If you decide to run your own replay as gzero@cdaql*, you
better
make sure that it is a VERY short replay (so it doesn't interfere with
the automatic replays), you also better make sure that you do not
overwrite an automatic replay. To do so, add the option "--outputstem
YYYY" when running g0analysis, that will produce a root file named
YYYY.XXXX.root, XXXX is the
run number. Failure to comply,
can hurt the experiment (by using too
much CPU) and create confusion (by mixing up file names) : so don't do
it.
How to run your own analysis.
To replay the data you can use
any machines (but cdaql* and
gzerol3), you can also use the ifarml* machines (just remember that job
longer than 30 min are niced) or the scientific computing farm
(actually
this is the best choice, for more info read
this)
. Following are simple steps
to take to run your own replays.
Option
A : using the already
compiled group g0analysis version.
- Setup a directory for outputs (you should have
to do this only once).
- at the location of your choice create a
directory : mkdir
G0Scratch
- set up your environment variables :
include the
following commands in your ~/.login file. Don't forget to source your
login before the next step.
setenv
G0SCRATCH your_directory_absolute_path
source
/group/gzero/G0Analysis/Linux/G0Analysis_pro/SetupFiles/SET_ME_UP.csh
- The root files are large files and they can be recreated
easily. So it is a good idea to redirect those files to the work disk
(very large files).
cd
/work/hallc/gzero
mkdir your_username
mkdir your_username/rootfiles
cd $G0SCRATCH
rmdir rootfiles
ln -s /work/hallc/gzero/your_username/rootfiles rootfiles
- You probably want to do the same thing
for the raw data file.
Moreover, it is suggested to redirect the data file directory to a
place known by the whole collaboration, so the raw data file can be
used by every one in the collaboration
cd
$G0SCRATCH
rmdir data
ln -s /work/hallc/gzero/g0analysis/datafiles data
- Finally, in order to be able to retrieve the raw data
from
the silo and use the farm machine. If the file
~/.jlab.scicomp/jlab.scicomp.keystore exist on your account you are
good to go. If not : open your browser and go to:
jasmine.jlab.org/scicomp/secure/secret.jsp
- Replay the data.
There are several
scripts to get data files from tape and submit batch jobs. In all case
you need to be a register user of the scientific computing farms (see
above). All scripts have
help files accessible using "-h".
cd
/group/gzero/G0Analysis/common/bin
then choose one of the
following:
- update_cache_links.pl
: This makes data files
links in your data directory of all the files currently on the
cache disks.
- g0cache_by_run.pl
: This retrieves the
data files from tape and has them put on the cache disks. You will have
to wait while the raw data file are downloaded. The system will send
you an email to signal the completion of the command. when this is
done, rerun update_cache_link.pl
- g0batchsub.pl
: This submits an analysis
job to the batch farm using your currently configured analyzer
version and the option list specified by -O "............". If you
decide not to use the farm machines, you skip this command and just run
g0analysis at the command line.
If you do a lot of replays, it can
become tedious to wait for the files to be downloaded before running
g0analysis. There is a tool for your that does that automatically : the
batchman. Read this
document starting page 33.
Option B : using your
own version of g0analysis.
Read
this
starting page 9.
STANDARD
RUNNING CONDITIONS
-Raster
size (03-19-06, 11am) : the default raster size to tell MCC
should be
1.8 x 1.8 mm (= 2. x 2. mm in reality), check that the raster
mode is Gzero and not hall C
-Beam
position (03-20-06, 6pm) : the beam should be at the position 0,0
on both G0 and G0B. The tolerance is +/- 0.2 mm.
-Nominal threshold settings
: 100 mV.
-Nominal fastbus configuration
: ps4=1000, nofastclear
-Herbert's paddle reading
: 50 to 70 nA per ua of beam current (whith lh2 target)
--Halo
rates : All
halo
monitors should be turned on. The following are rates we saw under
good beam conditions with 40 uA on April 5, 2006; these results
correspond to a halo that is < 0.25 ppm outside a 3 mm radius which
is less than
our spec limit of 1 ppm.
monitor
|
no halo
target [Hz/uA]
|
11mm halo
target [Hz/uA]
|
6mm halo
target [Hz/uA]
|
halo 3
|
5
|
8
|
25
|
halo 4
|
4
|
7
|
25
|
halo 5
|
5
|
9
|
90
|
halo 6
|
3
|
7
|
68
|
halo 7
|
0.1
|
0.5
|
9
|
halo 8
|
0.3
|
1.7
|
26
|
-Magnet current setting
(epics reading) : 3296.98 A
-Beam energy (epics
reading) : 687 MeV
HOW TO BRING
UP THE ION CHAMBER PAGE
Bring up Monticello . Choose
RadCon,
hallC ion chamber.
HOW TO CHECK THAT
THE RASTER IS ON
Bring up Monticello. Choose HallC,
HallC Raster fast. Check that the readback values (the yellow box on
the bottom left) are not zero and that the raster
mode is gzero and not hallc. You can also check the size of the
raster with the scope : see
how
HOW TO BRING UP
THE BCM/BPM DISPLAY
as cvxwrks@cdaql* :
open a terminal
type:
medm -x MEDM/beam/G0bpm.adl
IOC used by G0
This is far from being complete. Please let us know if you know of
ioc that G0 use and are not listed here.
*iocg01 -> Target
*G0FSD -> target FSD
*g0iocsms -> sms
*iochc10 -> Moller fryo, target
*Molcol -> Moller collimators
iocse14, iocse17, iocse18, iocse19, iocse20 -> BPM, BCM
To reboot the ioc which name are preceeded by * :
> ssh cdaq@cdaql*
> rebootpanel
or on the screen right from the DAQ console, use the the pulldown menu
(put your mouse on eth background us the middle button of the mouse)
G0
beamline components
This is the songsheet for the G0
beam line as of March 16,06.
According to the preliminary results of the final survey of the
beam line
name
|
type
|
distance to
hall center (m)
|
IPM3H00H
|
bpm
|
-3.25
|
IHA3H00
|
harp
|
-3.01
|
IPM3H00AA
|
bpm
|
-2.31
|
IPM3H00B
|
bpm
|
-2.04
|
ITV3H00
|
viewer
|
-1.81
|
IHA3H00A
|
harp
|
-1.60
|
IPM3H00C
|
bpm
|
-0.18
|
IHM3HG0
|
halo target
|
10.72
|
IBCHG0Z
|
bcm
|
12.2
|
IPM3HG0A
|
bpm
|
13.21
|
IHA3HG0
|
harp
|
13.46
|
IOR3HG0
|
otr
|
15.26
|
IHA3HG0A
|
harp
|
15.5
|
IPM3HG0B
|
bpm
|
15.75
|
|
|
|
How bring up the
Beam Time accounting page
From the Sun workstation, use the
pull down menu (with your left finger). From any other machines
type : "ssh cdaq@jlabs1
/group/accsft/bta/btaCUE.csh c".
Do not forget to bring up the aid table (so far you can only do that
from the un pulldown menu). The Aid is used to set the minimum beam
intensity acceptable for the experiment.
How to take an
harps scan
MCC should be able to both take the
data and analyze them. Make sure that the operator posts the results in
their logbook. This standard hall C
howto
discuss the uses of the super harps for hall C.
Connect to
the archiver.
Only a subset of the available EPICS variables are archived, to have
your favorite one archived you need to ask.
How to reset the
HV snipper? What to do if the HV won't turn on.
An HV protection circuit board (also
called snipper) will shutdown the HV crates when conditions that might
lead to a very large PMT anode current are present. If you are trying
to turn on the HV but they won't come up or they keep on going down,
you
might have to reset the snipper. This
document
tells you how and also explain how the board works.
Another reason why the HV won't come on line is because of low SMS
current. There is a power supply (PS) current low interlock that
prevents the detector HV'sfrom being re-established at low magnet
current. To reset this, go the the SMS control screen and look
under Alarm Control, 5311 Power Supply Current Low.
Logged as cvxwrks@cdaqs3, go to
MEDM/beam . Type "striptool". The
display will plot your variable from the time you start the Gui. With
this method, you
cannot retrieve values that are older than the time at which you start
the GUI.
- Here
is a list of important phone numbers in order to reach system experts.
- Call Run coordinator
Cell phone: 876-1791. Generic pager: 584-0120, but the RC might have
his own pager, see white board.
To start Monticello, log
in as cvxwrks@cdaql5. Use the
right-most mouse button to click on the workspace background.
Select
"Run Program... and in the pop up window type "edm". A
version of
Monticello pops up.
For the duration of the run, we are
using the Hall C logbook. Here is
the
Hall C Logbook, here
is the manual for the
Hall C
Logbook.
1.
How to Enter logs:
- From a web browser : goto the hall C logbook, click on the "Make an
entry" link at the top left of the main page.
- From an xterm and any CUE machine. Go to
/group/hallc/hclog/src/, type hclogentry.
2. How To Scan Into the logbook.
To scan the check list pages, follow
these steps:
1) Open a terminal on cdaql4 (to left of SMS control screen) logged
in to
cvxwrks. This process should work on any of the linux machines, I
think,
but I know it works on cdaql4.
2) Run "xsane" (just type xsane).
3) The xsane control gui should eventually appear. Also you should
get a
"preview" screen. If the preview screen doesn't appear, then open it by
clicking on "Show Preview" from the View pulldown menu at the top of
the
control GUI.
4) Put the first page of the check list in the scanner (face down,
top of
page near the hinge of the scanner cover).
5) Click the "Acquire preview" button at the bottom of the preview
window. A preview of the full page should appear in the preview window.
6) Drag a box in the preview window around the interesting part of
the
preview image (no use saving all of the white space around the check
list).
7) On the control GUI, select "Save" for the "XSane Mode". Then
select
"Color" in the list below "Save" and "Full color range" in the list
below
"Color". Enter a file name in the next box (or you can browse for a
file
name by clicking the icon that looks like a floppy disk next to the
file
name box). If "Step" is +1, the file name will be "incremented" by 1
for
the next scan. Be sure that "Type" is set to PNG and that the
resolution
(next to icon with dots of various sizes) is set to 150.
8) Press the "Scan" button on the control GUI.
9) Repeat the process for the second page of the check list.
How to get a
copy of the COO, the RSAD and the ESADs
Every collaborator should read these
documents before their first shift. There should be a copy in the
counting house. Remember to sign
them before the start of your first
shift. A copy of each document is located here :
COO,
G0
ESAD,
HALLC
ESAD,
RSAD.
How
to
Run/Restart CODA
for G0
To keep the ET system
happy working, do the following when
restarting CODA:
1) When you kill CODA, also kill the realtime and beam feedback analyzers
2) Restart CODA, and download the run type.
3) Begin a run.
4) Launch the beamfeedback run forever. Wait about 1 minute.
5) Launch the realtime analyzer.
6) Start the analysis minder if needed (~/SCRIPTS/analysis_minder.pl)
Trouble shooting:
- when you get error messages from ER3 : try that.
- problems
with pink screens: try this
Manuals:
This
is the manual that you should use for the backward angle (author : F.
Benmokhtar)
Also : here
is the manual we used for the forward angle run :
- DAQ and Electronics Configuration
- ASCS: the Analysis and Silo Copying System
- Ways to look at the data stream
- Rebooting the crates
How to change
the
IHWP
The suggested procedure for changing the state of the HWP is:
end the run
stop charge feedback
ask MCC to change the state of the HWP
ask MCC to set the x-stage properly
restart charge feedback
start a new run
...and then you may have to let the mean charge asymmetry get back to
zero and then start a new run.
For IHWP=IN (updated 19 March 2007), we want the following optimal conditions: - RHWP angle = 170
degrees (8500) - PC +HV = 6.212 PC -HV = 3.776 - PC x-stage = 20 PC y-stage = 70
For IHWP=OUT (updated March 2007), we want the following optimal conditions: - RHWP angle = 170
degrees (8500) - PC +HV = 6.212 PC -HV = 3.776 - PC x-stage = 55 PC y-stage = 105
So the only thing that changes when changing the IHWP is the PC x-stage.
To change the PC x-stage (MCC will do this): Next to "Gun/Laser" click on "!" and select Pockels
Cell Helper. Type 0 for IN or 70 for OUT in XStage and press "Go", the PC will
move to the new position.
How to change the
IHWP status if allowed to change the x-stage (not valid as of 3/7/01)
The suggested procedure for changing the state of the HWP is:
end the run
stop charge feedback
ask MCC to change the state of the HWP
set the x-stage properly
restart charge feedback
start a new run
...and then you may have to let the mean charge asymmetry get back to
zero and then start a new run.
The way to change the x-stage settings is:
For IHWP=IN, we have the following optimal conditions: - RHWP angle = 170
degrees (8500) - PC +HV = 5.712 PC -HV = 4.276 - PC x-stage = 0 PC y-stage = 90
For IHWP=OUT, we have the following optimal conditions: - RHWP angle = 170
degrees (8500) - PC +HV = 5.712 PC -HV = 4.276 - PC x-stage = 70 PC y-stage =
90
So the only thing that changes when changing the IHWP is the PC x-stage.
To change the PC x-srage: Next to "Gun/Laser" click on "!" and select Pockels
Cell Helper. Type 0 for IN or 70 for OUT in XStage and press "Go", the PC will
move to the new position.
Check that the GUI is not already up on a terminal. If not: launch a
terminal window, then
- ssh cvxwrks@cdaqs2
- enter the password: see white board
- cd $EPG0HV/tk
- hv.tcl
To restore an HV file:
- From the "File" pull down menu select Backup.
- Make a comment describing the file you're backing up
- Select "Perform Backup"
- Once the backup is complete, select "quit" from the file pulldown
menu
- Select restore from the "Temp HV Controls" file pulldown menu
- Select "file"
- Choose "select restore file"
- Pick your file, then press "ok"
- Select "Perform Restore"
- Select "ok" from the red screen--you're done.
To bring up the HV GUI for
the Wire Chambers, Lumis and Halo's
- The same as above, except the directory is $EPTEMPHV
Also see this web
page for some more info about the GUI and perl scripts to change
the high voltage settings.
The Analysis and Silo Copying System (ASCS) is the set of processes
which copy the data file from the DAQ machine to the silo and perform a
full replay of the data.
To check that the ASCS is
working:
Launch a terminal on cdaql1,cdaql2,cdaql4,cdaql5,cdaql6
- ssh gzero@gzerol3
- ps -ef | grep reap
- If you do not see a "happyreaper" running, you need to start one
- to start the "happyreaper" :
- cd g0backward/backup/FOREVER
- runforever ForeverFile
Using the ASCS database to
locate runs:
Launch a terminal then:
- ssh gzero@gzerol3
- g0backward/backup/data_tracker.pl
- choose your search parameters
- press the "Query" button to find the runs which match your chosen
parameters
How to perfom a
BPM/BCM calibration
Contact : Riad (last update 10-13--06)
There are two sets of instructions
here. The first set is to calibrate the BPMs and BCMs in Hall C. The
second set is to calibrate the BPMs in the injector. Only Stephanie,
Riad, or another beam expert will need to use the second set of
instructions. If you are a shift worker, then you will follow the first
set of instructions for the hall.
///////////////////////////////////
To calibrate the BPMs and BCMs in the ***HALL***: any shift taker can follow those instructions.
1. Turn off coil modulation and G0 charge feedback.
2. Set the beam to maximum current (60 uA).
3. Open the BPM SEE Diagnostics (monticello.adl -> BPM -> BPM Diagnostics - SEE).
4.
The Hall BPMs are located in
multiple IOCs (iocse14, iocse17, iocse18, iocse20). We must choose
XGAIN and YGAIN settings for each IOC. Let's consider here iocse11.
Click on "Live Displays" next to iocse11. We are in Auto Gain, so the
values listed in the XGAIN and YGAIN columns fluctuate. Check that this
is true.
For each IOC, we
want to choose the XGAIN and YGAIN of the BPM of special
interest. This is the underlined BPM in this list.
iocse18: 3C07A, 3C17
iocse14: 3C08, 3C12, 3C16
iocse17: 3C20A, 3H00, 3H00A, 3H00B, 3H00C
iocse20: 3HG0, 3HG0B
Make a table with your XGAIN and YGAIN settings and make an elog entry of the table:
IOC XGAIN YGAIN
iocse14
iocse17
iocse18
iocse20
5.
Call MCC and instruct them to
change the gain mode for the Hall C BPMs (iocse14, iocse17, iocse18,
iocse20) from "Auto Gain" to "Forced Gain". Tell them the XGAIN and
YGAIN settings for each IOC from your table in step 3.
6. Ask MCC to turn off all feedback loops (like LOCK PID) because all
positions will be reading zero once we are in Forced Gain.
7.
Ask for the currents specified in
the sequence below, remaining at each setting for 5 minutes. As soon as
you get 0 uA from MCC for the first current in the sequence below, you
should start a run. Each time you ask for 0 uA, tell MCC to close the
Hall C slit to prevent leakage from other halls.
0, 10, 0, 20, 0, 30, 0, 40, 0, 50, 0, 60, 0, 55, 0, 45, 0, 35, 0, 25,
0, 15, 0, 5, 0 uA
8. End the run.
9.
Call MCC and ask them to put all
of the IOCs back into Auto Gain. This is your last step. Stephanie
Bailey or another beam expert will analyze the data and enter the new
calibrations into the database according to the steps below.
***** Instructions for Stephanie Bailey or another beam expert *****
8. Analyze the run:
> ssh gzero@cdaql5
cdaql5.jlab.org> g0analysis -r ##### --beamntuple --outputstem BCMCalib
9. To obtain the new beam calibrations:
ssh gzero@cdaql6
cdaql6.jlab.org> cd /home/gzero/G0Analysis/G0Scripts
cdaql6.jlab.org> ./beam_monitor_calib
You will be prompted to enter the run number. This script creates a file named "beam_scaler_calib_#####.out" in the following directory: /home/gzero/scratch/calib
10. To copy the output file to the Databse directory:
cdaql6.jlab.org> cp /home/gzero/scratch/calib/
beam_scaler_calib_#####.out $G0DATABASE/inputfiles
Note: also copy all of the injector BCMs from the previous calibration list. These pedestals are all of the one's listed after the halo pedestals, and most begin with "IPM".
11. To insert the calibrations into the Database:
cdaql6.jlab.org> cd $G0DATABASE/perl/bin
cdaql6.jlab.org> monitor_calibration_fill.pl -s ##### -f ##### -l 999999
-d gzero_687MeV_comm2 -n g0dbserver -u g0replay -p ../../inputfiles/
beam_scaler_calib_#####.out
Answer yes to any questions.
////////////////////////////////////
To calibrate the BPMs and BCMs in the ***INJECTOR*** : Only beam experts should execute this procedure.
1. Set the beam to maximum current (60 uA).
2. Open the BPM SEE Diagnostics (monticello.adl -> BPM -> BPM Diagnostics - SEE).
3. The Injector BPMs are located in two IOCs (iocse14 and iocse19). We must choose XGAIN and YGAIN settings for each IOC. Click on "Live Displays" next to iocse14. We are in Auto Gain, so the values listed in the XGAIN and YGAIN columns fluctuate. Check that this is true. Suppose you read the following:
BPM XGAIN YGAIN
1I02 1000 2000
1I04 1100 2100
1I06 900 2050
0I02 950 950
0I05 1150 2000
0I02A 1000 2050
In this example, I would choose XGAIN=1000 and YGAIN=2000 because 1000 looks like the average of the XGAIN values and 2000 looks like the average of the YGAIN values. A bad choice would be 500 for the XGAIN or 1000 for the YGAIN. Repeat this process for the other IOCs:
iocse11: all except 2D00
iocse19: all except 0R06
Make a table with your XGAIN and YGAIN settings and make an elog entry of the table:
IOC XGAIN YGAIN
iocse11
iocse19
4. Instruct MCC to change the gain mode for the Injector BPMs (iocse11 and iocse19) from "Auto Gain" to "Forced Gain". Tell them the XGAIN and YGAIN settings for each IOC from your table in step 3.
5. Type the following:
> ssh gzero@gzerol3
> greenmonster
A green window titled "Configuration Utility" should pop up. Left click the second tab labeled "ScanUtil".
6. In greenmonster, click "NOT CLEAN"
and type "60" in both "Set Point 1" and "Set Point 2". Click the "Set
Values" button. Ask MCC for 60 uA and start a run. When MCC informs you
that you have 60 uA, click "CLEAN" in greenmonster.
7. In five minutes, click "NOT CLEAN" on greenmonster. This means that
the data you are now taking is garbage. Ask MCC for 50 uA. Enter "50"
in "Set Point 1" and "Set Point 2" and click the "Set Values" button on
Greenmonster. When MCC informs you that you have 50 uA, click "CLEAN"
in greenmonster. This means that the data you are now taking is good
data. In other words, the current is stationary. It is not going up or
down.
8. Ask for the currents specified in the sequence below, remaining at
each setting for 5 minutes. At this point, you have already done the
first two currents (60 and 50 uA). Your next current will be 40uA.
Follow the instructions in step 7 word for word, in the exact
order.
60, 50, 40, 30, 20, 10 uA
9. End the run.
10. Call MCC and ask them to put all of the IOCs back into Auto Gain.
This is your last step. Stephanie Bailey or another beam expert will
analyze the data and enter the new calibrations into the database
according to the steps below.
***** Instructions for Stephanie Bailey or another beam expert
*****
11. To obtain the new injector calibrations:
cdaql6.jlab.org> cd /home/gzero/G0Analysis/G0Scripts
cdaql6.jlab.org> root
root [#] .x open.macro(#####)
root [#] .x inj_bpmPed_loop.C(#####)
Enter run number : #####
Here, you will see lots of windows flash before your eyes, too quick to
see what is on them. Wait for this to finish. When the script finishes,
quit root.
root [#] .q
This script creates a file named "beam_scaler_calib_#####.out" in the
following directory: /home/gzero/scratch/calib. If you want to retain
the calibrations for the hall BPMS and BCMs
(and you usually do), then you need to copy the most recent hall
calibrations into this file.
12. To copy the output file to the Databse directory:
cdaql6.jlab.org> cp /home/gzero/scratch/calib/
beam_scaler_calib_#####.out $G0DATABASE/inputfiles
13. To insert the calibrations into the Database:
cdaql2.jlab.org> cd $G0DATABASE/perl/bin
cdaql2.jlab.org> monitor_calibration_fill.pl -s ##### -f ##### -l
999999
-d gzero_687MeV_comm2 -n g0dbserver -u g0replay -p ../../inputfiles/
beam_scaler_calib_#####.out
Answer yes to any questions.
Realtime,
Online or Offline ??? : What it meant during the forward data taking.
This describe how thing were done
during the forward data taking,
it is not really appropriate for the pre-beam period. This
document
is the manual for basic analysis on shift during the forward data
taking. In summary :
All base analysis processes are performed by the
g0analysis
code. Various supporting auxillary codes allow displays, they are just
listed here but a more complete description can be found in the linked
document. The available tools for the forward standard analysis were:
- Realtime tools:
they are designed to run parallel with the data taking process and
give a prompt evaluation of the data. For speed concerns, those
processes will only perform a very minimal analysis on some events of
the runs (grabbed on the Event Transfer (ET) memory buffer and fill
predefined histograms in a mapped memory buffers. Those tools are : beamfeedback processes, G0Realtime & G0Realtimemonitor
(for a list of the forward realtime histograms see the linked document
page 18 to 33), G0ACM
(estimates the PMT anode
current). The analysis_minder.pl
is the wrapper code that
automates the start, stop etc.. of those tools.
- Online tools:
they
are designed for a more detailed second stage analysis. They
access the CODA disk files (by opposition to the ET for realtime
analysis). Note that it is possible to read the beginning of a file
while the end of the file is being written. The standard analysis fills
a set of predefined histograms (a more numerous and more complex set
than the
realtime, for the list of forward histograms see linked document page
35 to 49) and
output them to a ROOT file. A script reads those output files and
produce a one page summary of the data in plain text, it does also
compare the result of the analysis against golden values. CODA
starts the online replay when 50k events have been taken (even if the
run is still going on). It is also possible to setup (for a
while) the online process such that it produces the fastbus ntuple if
needed (although the analysis will be somewhat slower).
The online ROOT files can be opened in an interactive ROOT
session.
- Offline
tools:
they are designed for a full blown analysis (deadtime correction,
linear regression etc..). The outputs are histograms (the same than the
online version) and ntuples (mps, quartet, fastbus, beam). This version
does also output results to the database. When a run is ended, the CODA
disk files are copied from the DAQ machine (gzerol3) to the analysis
machines (cdaql*) where
the run is analyzed. This is necessary to ensure a good CPU
availability for the DAQ and the realtime and online processes. ASCS
is the wrapper that insures an automated copy and replay of this stage
of the analysis. The copying and analysis takes some time (~ 1 hour for
a 1 h run once the run is ended) such the
offline analysis is not the primary tool for on shift analysis. Goat++ is the standard GUI that
allow to query the database and do analysis involving many runs at
once. Of course, the offline ROOT files can
be opened in an interactive ROOT session.
How to perform a PITA scan
Contact : S. Bailey, last update
04-23-06.
1. Restart CODA with the ts_Fullinj
configuration. Reboot the G0inj crate to be sure to load the new
libraries. To do this, find the
terminal called "ROC31", push "enter" and then write
"reboot".
2. Type the following:
> ssh gzero@gzerol3
> greenmonster
A green window titled "Configuration Utility" should pop up. Left click
the second tab labeled "ScanUtil".
3. Open the window titled "Laser Polarization & Parity Controls".
If it is not already open, go to the Accelerator Main Menu (aka
Monticello). Left click the middle button next to Gun/Laser. In the
drop-down menu, click Hall Parity Controls. Look for "Gun2: PC (PITA)
Pos" and "Gun2: PC (PITA) Neg". They are green in color and near the
top of the window. The blue box in the same row as "Gun2: PC (PITA)
Pos" is where you will set the positive voltage of the Pockels Cell.
The blue box in the same row as "Gun2: PC (PITA) Neg" is where you will
set the negative voltage of the Pockels Cell. What are the positive and
negative voltages now? Record these numbers. Let's pretend the positive
high voltage is 6.440 DAC Volts and the negative high voltage is 5.325
DAC Volts.
4. You are going to vary the positive
and negative voltages of the Pockels Cell. (1 DAC Volt is equivalent to
60 real volts.) Make the following table. The second column is the DAC
Volts that you will set the positive high voltage to. You should start
with the current setting of the positive high voltage that you recorded
in step 3. The third column is the DAC Volts that you will set the
negative high voltage to. You should start with the current setting of
the negative high voltage that you recorded in step 3. The first column
corresponds to the real voltage. The third column is where you will
keep track of the number of events.
Delta(HV)(Set Point 1) +HV -HV event started
0 6.44 5.325
-90 4.94 6.825
-180 3.44 8.325
90 7.94 3.825
180 9.44 2.325
In step 3, I asked you to pretend
that the positive high voltage is 6.44 DAC Volts. In the second
column, I enter this number in the same row as 0. I subtract 1.5 from
this number and enter it in the same row as -90. I subtract 3 from the
original number and enter it in the same row as -180. Now, I add
1.5
to the original number and enter it in the same row as 90. I add
3 to
the original number and enter it in the same row as 180.
In step 3, I asked you to pretend
that the negative high voltage is 5.325 DAC Volts. In the third
column, I enter this number in the same row as 0. I add 1.5 to this
number and enter it
in the same row as -90. I add 3 to the original number and enter it in
the same row as -180. Now, I subtract 1.5 from the original
number and enter it in the same row as 90. I subtract 3
from the original number and enter it in the same row as 180.
Ok. Pretend is over. Take your values
for the positive and negative voltages and make a table just as we did
for the pretend values above.
5. Let's get started. In
greenmonster, click "NOT CLEAN" and type "0" in "Set Point 1" and "Set
Point 2". Click the "Set Values" button. Start a run. When you have
accumulated more than 50 events, click "CLEAN" in greenmonster. Write
in the third column the number of events at the time you clicked
"CLEAN".
6. In three minutes, click "NOT
CLEAN" on greenmonster. This means that the data you are now taking is
garbage. Enter "-90" in "Set Point 1" and "Set Point 2" and click the
"Set Values" button on Greenmonster. Set the positive high voltage to
the second value in column 2 in the "Laser Polarization & Parity
Controls". Set the negative high voltage to the second value in column
3 in the "Laser Polarization & Parity Controls". Click "CLEAN" in
greenmonster and record the number of events in the third column. This
means that the data you are now taking is good data.
7. Up to this point, you have done
the first two points in the table above. Repeat step 6 for the
remaining five points in the table, remaining at each voltage for three
minutes.
8. End the run.
9. Make an elog entry with the table from step 4.
10. Restart CODA with the ts_Full configuration for regular running.
11. Analyze the run:
> ssh gzero@cdaql5
cdaql5.jlab.org> g0analysis -r ##### --beamntuple
--qrtntuple 1
12. Run the "pita_bcm.C" analysis script. You will be prompted to enter
the run number, the
state of the IHWP,
the angle of the RHWP, and the detector. When you are prompted for the
detector,
enter "2" for BCM2.
> ssh gzero@cdaql5
cdaql5.jlab.org> cd
/home/gzero/G0Analysis/G0Scripts
cdaql5.jlab.org> root
root [0] .x pita_bcm.C
Enter run number : #####
ROOT file is
/home/gzero/scratch/rootfiles/G0Scaler.#####.root
Enter IHWP state (IN or OUT):
Enter IHWP angle (8000 or 1500):
Enter detector:
BCM1 (enter 1), BCM2 (enter 2)
2
root [1] .q
This script creates a plot named
"pita_#####_BCM2.gif" in the following
directory:
/home/gzero/scratch/pita_plots
13. Run the "pita_bpm.C" analysis script. Again, you will be prompted
to enter the run number, the
state of the
IHWP, the angle of the RHWP, and the
detector. When you are prompted for the detector, enter
"26" for
G0B.
> ssh gzero@cdaql5
cdaql5.jlab.org> cd
/home/gzero/G0Analysis/G0Scripts
cdaql5.jlab.org> root
root [0] .x pita_bpm.C
Enter run number : #####
ROOT file is
/home/gzero/scratch/rootfiles/G0Scaler.#####.root
Enter IHWP state (IN or OUT):
Enter IHWP angle (8000 or 1500):
Enter detector:
IPM1I02 (enter 1), IPM1I04 (enter 2), IPM1I06 (enter
3)
IPM0I02 (enter 4), IPM0I02A (enter 5), IPM0I05
(enter 6)
IPM0L01 (enter 7), IPM0L02 (enter 8), BCM0L02 (enter
9)
IPM0L03 (enter 10), IPM0L04 (enter 11), IPM0L05
(enter 12)
IPM0L06 (enter 13), IPM0R05 (enter 14), C07A (enter
15)
C08 (enter 16), C12 (enter 17), C16 (enter 18)
C17 (enter 19), C20A (enter 20), H00 (enter 21),
H00A (enter 22)
H00B (enter 23), H00C (enter 24), G0 (enter 25), G0B
(enter 26)
26
This script creates a plot named
"pita_#####_G0B.gif" in the following
directory:
/home/gzero/scratch/pita_plots
root [1] .q
How
to grab a screen photo
- Type "ksnapshot" in a terminal in the same directory as your
internet logbook
- Set the delay depending on how quick you are--this allows you to
click on "New Snapshot" and then place your cursor on the screen you
want the photo of (instead of getting a shot of the entire desktop).
- Save this photo to the tmp file using .png as an extension.
- Attach it the log entry--it will show as a photo when the log
entry is selected, not as an attachment.
How to perform an
IA scan
Contact : S. Bailey, last update 04-22-06
1. Restart CODA with the ts_Fullinj
configuration. Reboot the G0inj crate to be sure to load the new
libraries. To do this, find the
terminal called "ROC31", push "enter" and then write
"reboot".
2. Type the following:
> ssh gzero@gzerol3
> greenmonster
A green window titled "Configuration
Utility" should pop up. Left click the second tab labeled "ScanUtil".
3. Open the window titled "Laser
Polarization & Parity Controls". If it is not already open, go to
the Accelerator Main Menu (aka Monticello). Left click the middle
button next to Gun/Laser. In the drop-down menu, click Hall Parity
Controls. Look for "Hall C : IA". It is grey in color and near the
bottom of the window. The first box in the same row as "Hall C : IA" is
where you will set the voltage of the IA cell. The second box is the
read back of the IA voltage. What is the IA voltage read back now?
Record this number. You will need it at the end.
4. You are going to vary the voltage
of the IA cell from 1 DAC Volt to 9 DAC Volts. 1 DAC Volt is equivalent
to 60 real volts. Make the following table. The second column are the
DAC Volts that you will set the IA cell to. The first column
corresponds to the real voltage. The third column is where you will
keep track of the number of events.
Delta (HV) (Set Point
1) IA
Voltage (Set Point
2) event started
-240
1
-120
3
0
5
120
7
240
9
5. Let's get started. In
greenmonster, click "NOT CLEAN" and type "-240" in "Set Point 1" and
"1" in "Set Point 2". Click the "Set Values" button. Set the IA voltage
to "1" in the "Laser Polarization & Parity Controls". Make sure
that the read back of the IA cell reads "1" as well. Start a run. When
you have accumulated more than 50 events, click "CLEAN" in
greenmonster. Write in the third column the number of events at the
time you clicked "CLEAN".
6. In three minutes, click "NOT
CLEAN" on greenmonster. This means that the data you are now taking is
garbage. Enter "-120" in "Set Point 1" and "3" in "Set Point 2" and
click the "Set Values" button on Greenmonster. Set the IA voltage to
"3" in the "Laser Polarization & Parity Controls". Make sure that
the read back of the IA cell reads "3" as well. Click "CLEAN" in
greenmonster and record the number of events in the third column. This
means that the data you are now taking is good data.
7. Up to this point, you have done
the first two points in the table above. Repeat step 5 for the
remaining three points in the table, remaining at each voltage for
three minutes.
8. End the run.
9. Set the IA voltage back to its original voltage. You wrote this
number down in step 2.
10. Make an elog entry with the table from step 3.
11. Restart CODA with the ts_Full configuration for regular running.
12. Analyze the run:
> ssh gzero@cdaql5
cdaql5.jlab.org> g0analysis -r ##### --beamntuple
--qrtntuple 1
13. Run the "ia_bcm.C" You will be prompted to enter the run number,
the
state of the IHWP, the angle of the
RHWP, and the detector. When you are
prompted for the detector, enter
"2" for BCM2.
> ssh gzero@cdaql5
cdaql5.jlab.org> cd
/home/gzero/G0Analysis/G0Scripts
cdaql5.jlab.org> root
root [0] .x ia_bcm.C
Enter run number : #####
ROOT file is
/home/gzero/scratch/rootfiles/G0Scaler.#####.root
Enter IHWP state (IN or OUT):
Enter IHWP angle (8000 or 1500):
Enter detector:
BCM1 (enter 1), BCM2 (enter 2)
2
This script creates a plot named "ia_#####_BCM2.gif"
in the following
directory:
/home/gzero/scratch/ia_plots
From this plot, take the slope. For example, suppose
the slope is 6 ppm/real V. To convert the slope from real
Volts to DAC
Volts, multiply it by (60 real V / 1 DAC V). Then, enter this number in
the
"g0beamfeedback.adl"
GUI in the "IA Calibration Const (ppm/V)" field.
14. Run the "ia_bpm.C" analysis script. Again, you will be prompted to
enter the run number, the
state of the
IHWP, the angle of the RHWP, and the
detector. When you are prompted for the detector, enter
"26" for
G0B.
> ssh gzero@cdaql5
cdaql5.jlab.org> cd
/home/gzero/G0Analysis/G0Scripts
cdaql5.jlab.org> root
root [0] .x ia_bpm.C
Enter run number : #####
ROOT file is
/home/gzero/scratch/rootfiles/G0Scaler.#####.root
Enter IHWP state (IN or OUT):
Enter IHWP angle (8000 or 1500):
Enter detector:
IPM1I02 (enter 1), IPM1I04 (enter 2), IPM1I06 (enter
3)
IPM0I02 (enter 4), IPM0I02A (enter 5), IPM0I05
(enter 6)
IPM0L01 (enter 7), IPM0L02 (enter 8), BCM0L02 (enter
9)
IPM0L03 (enter 10), IPM0L04 (enter 11), IPM0L05
(enter 12)
IPM0L06 (enter 13), IPM0R05 (enter 14), C07A (enter
15)
C08 (enter 16), C12 (enter 17), C16 (enter 18)
C17 (enter 19), C20A (enter 20), H00 (enter 21),
H00A (enter 22)
H00B (enter 23), H00C (enter 24), G0 (enter 25), G0B
(enter 26)
26
This script creates a plot named "ia_#####_G0B.gif"
in the following
directory:
/home/gzero/scratch/ia_plots
root [1] .q
How to for the
beam feedback.
The feedback is a realtime process, it is active when a run is in
progress, its "feedback mode" analysis is in progress and the variables
modifying the laser table are updated.
- To start the run see this.
- If needed : start the feedback analysis (read this). Be very
carefull if you need to restart coda on the order you execute those
command : read this). Usually
this is already up and running on caqds1 (screen right of the daq
screen)
- If needed start the feedback MEDM screen (that modify the setting
of the laser table) : do this
, This screens looks like that.
Usually this screen is up and running on the screen left of the magnet
machine.
Troubleshooting:
- If the realtime display about beam parity quality does not update,
the feedback probably doesn't work. Your best bet is to kill the
analysis minder and CODA and restart every thing IN THE RIGHT ORDER !!!!
- If the time stamp for the last update in the feedback MEDM screen
append more than 15 mn and you are taking data above 5uA, the feedback
is not working : start it !.
- At this time (04-04-06), we are only feeback on the charge and not
the position. In the MEDM feedback screen , the position feedback is on
but the calib constants are 0.
Top of page
How to Reset
Large Beam Current Display (betabrite)
Log onto cdaql6 as cvxwrks
cd BETABRITE/bcm
./bcm_pss.pl &
And that should make it work.
Top of page
Turning
beam &HV audio alert on or off
For the HV alert:
Using cdaql5,
> ssh cvxwrks@cdaql5
> cd ~/users/willy
> ./checkbeamAndHV.bash
For the beam alert:
Using cdaql5, open a terminal as
cvxwrks. At the prompt command ">" , type the following:
> cd ~/users/willy
> ./checkbeam.bash
Top of page
SMS Ramping
Instructions
Ramping the SMS is a simple 2 Step Process
Screen shot
1) From the Power Supply page on the SMS GUI press the Enable button.
The red indicator light to the left of the button should turn
green.
2) Click on the Current Target text field and enter the desired current
in the pop-up. Acknowledge your selection. The ramp status should turn
from "Stopped" to "Ramp up/down in MM:SS". Once the requested current
is reach the ramp status will return to "Stopped" and the Ramp Enable
indicator will return to red.
Notes:
Performing steps 1 and 2 in reverse order will only Enable a ramp but
will not start the SMS ramping. The value entered in the Current Target
box must change once ramping is enable or nothing will
happen.
When ramping from 0A one should first ramp to 4A before proceeding to
the goal current.
Well's Plot
- Turn Hall C Charge Feedback OFF
- Turn Coil Modulation OFF
- Set Hall C IA to 1.0 V
- Take 3 one-hour runs
- Set Hall C IA to 5.0 V
- Turn Hall C Charge Feedback ON
- Turn Coil Modulation ON
- Take 3 one-hour runs
- Turn Hall C Charge Feedback OFF
- Turn Coil Modulation OFF
- Set Hall C IA to 9.0 V
- Take 3 one-hour runs
Top of page
Target
Checklist Instructions
Target Shift
Checklist Instructions
These are places
where the target checklist information can be found. Almost all of
this information can be found in more than one place. Places to
begin to locate information (screen or monitor names, gas shed) are
in bold. Button names are in parentheses followed by arrows
that point to the names of the screens they produce in quotes. The
names of the fields where one finds the values to enter are
italicized.
The Monticello screen can be
found either on the Slow Controls display or on cdaql5
(next to the printer)--start from monticello.adl window; RHS
refers to the monitor to the right of the Slow Controls display.
BEAM PROPERTIES:
Beam Energy
Monticello:
(comfort screens)/GEGeneral CEBAF overview-> ¡°GEN_O_overview.adl¡±
-Set Energy,
Hall C
Beam Current
Top
red digital display
Halo Monitor
Signal
Monticello:
(HallC button 2)/G0 Halo Monitor-> ¡°HLC_O_G0_halomon.adl¡±
-Halo 3,Halo 4, lower,
normalized, numbers
RunControl up?
Data
Acquisition: ¡°Run Control¡±-running?
BPM G0 Girder
(x/y)
Monticello: ?-> ¡°G0bpm.adl¡± -IPM3HG0B, X/Y
Fast Raster
Rmax,Ix,Iy
Monticello:
(Hall C button 1)/Hall C Raster, Fast-> ¡°raster_hlc_FR.adl¡±
-Set Magnet Current, Width,
Height
Check Raster
Pattern
Raster
oscilloscope inside electronics room-nice and square?
Coil Pulsing
Target
computer: g0target-main.adl/(G0 Main Screen)->
¡°G0.adl¡±-Beamline (top right), coil pulsing
Position
Feedback
Slow
Controls: Charge Feedback window/g0beamfeedback.adl-position
feedback (bottom half)
Intensity
Feedback
Slow
Controls: Charge Feedback window/g0beamfeedback.adl-charge
feedback (top half)
Half Wave Plate
Slow
Controls: Charge Feedback window/g0beamfeedback.adl-insertable
1/2 wave (top)
Charge Asymmetry
Slow
Controls: Charge Feedback window/g0beamfeedback.adl-charge
asymmetry (top)
Position
Asymmetry
Slow
Controls: Charge Feedback window/g0beamfeedback.adl-X position
diff/Y position diff
Unser Temperature
Temperature monitor inside
electronics room
SMS
Helium Reservoir Level
Nitrogen Reservoir Level
Magnet Current
Lead Flow
Avg. Temp. of Coils
Avg. Temp. of Collimators
Vacuum Bayonet
Vacuum Cryovessel
all on RHS:
LookoutDirect-smscntrl/Main/(Shift Check List)-> ¡°SMS Shift
Checklist Items¡±
TARGET
Target
Temperature
