Short write-up on On-line 89-033 Replay

General Introduction

The on-line replay will be done on adaqh1 or adaqh2 . The data-taking will be run on adaqs1 . Type goespace_fpp to get to the directory /adaq/users/adaq/e89033/twoarm/espace_fpp for doing replay. Type espace_fpp to run the analysis code. The kumac files for ESPACE are in the espace_kumac subdirectory of the replay directory. The kumac files for PAW++ are in the paw_kumac subdirectory.

If you would like to test out the kumacs copy the directory /home/jones/stable . It has the following files:

db_coin_new	fpp_toffset_crude.calib	paw.metafile
detmap.config	fpp_toffset_ref.calib	paw.ps
emiss_pmiss_elas.dat	hbook	paw_kumac
espace_kumac	hdr_coin_1h	s_1_2_cut.dat
fpp_alignment_front.dat	last.kumac	ytg1.dat
fpp_alignment_rear.dat	last.kumacold	ytg2.dat
fpp_demux_cuts.dat	p_1_2_cut.dat	ytg3.dat
fpp_drift_dist_fits.dat	p_3_2_cut.dat

and three directories

hbook with files:
- fpp_1746.hbook
- fpp_1746.hbook.kumac
paw_kumac with files:
- beam_pos.kumac
- fpp_det.kumac
- fpp_test.kumac
- gauss_fit.kumac
espace_kumac with file:
- fpp_online.kumac

General task list for on-line replay

If angle change replay, follow instructions in angle change section .
If steady-state replay, follow instructions in the online steps section .
On runsheet circle if replay good or bad.
Make scalar output for run and fill in scalar summary. Follow instructions in Instructions for scalers. Write in the List of Runs sheet the total number of triggers and the sum of the triggers for this kinematics.
Run software to read EPICS data of bpm positions and current during run by following instructions in the document Monitoring the beam position. In the Executive Window of PAW++ the average and RMS for the bpms and current are written after the kumac is finished Write mean and RMS of the B3x and B3y positions in the List of Runs sheet. Write the $\mu$A-hours in the List of Runs sheet by using the time from the scaler sheet and the average current from the output of the bpm kumac.

Changes to online replay for each angle change

Edit header file to reflect current kinematics. Already there are four header files made : hdr_coin_1h , hdr_coin_85 , hdr_coin\140 , and hdr_coin_200 . The lines to edit are:

spece r 5 7.9266 +23.36 0.0 0.030 0.060
spech r 5 3.6795 -53.29 0.0 0.030 0.060
spece_offset r 3 -3.0e-3 0.0 1.3e-3
spech_offset r 3 -2.5e-3 0.0 -3.3e-3

In the spece line the first real number is the average field in the e-arm and the 2nd real number is the lab angle. In the spech line the first real number is the low field in the h-arm and the 2nd real number is the lab angle. The real numbers on lines spece_offset and spech_offset are the offsets in x, y, and z of the spectrometers from the nominal Hall A center. If survey numbers available then these can be changed, otherwise not critical.

Edit fpp_online.kumac: Change name of header file in line: set/file/header hdr_coin_1h

Replay at least 20,000 events.

Open hbook file in PAW++.

Execute paw kumac fpp_pol_#.hbook.kumac in hbook directory.

Set gates on missing energy versus missing momentum by running the paw em_pm_cut.kumac.

Set gates on e-arm y-target vs. h-arm y-target by running eytg_hytg_cut.kumac.

Replay again for at least 20,000 events, follow instructions in the online steps section and make printouts of all histograms.

Steps to take for online replay

The following steps assume you are replaying, and turning paw++ on, while in the directory e89033/twoarm/espace_fpp .
Run espace_fpp for at least 20,000 events with the espace kumac file espace_kumac/fpp_online
Open the hbook file hbook/fpp_#.hbook in paw++ . Execute the paw kumac in the hbook directory fpp_#.hbook.kumac .
Execute the paw kumac paw_kumac/fpp_test which will cycle through the following histograms. Printouts of the histograms for comparison should be in the online replay binder.
- 3.a: Histogram of tc_cor , the corrected coincidence timing. Gates shown on plot are upper and lower limits of cut for good coincidence event. Peak should not move. If it moves contact an expert.
- 3.b: 2-d histogram of y-target position calculated by e-arm and h-arm. Box represents cuts used for good coincidence event. Shouldn't move outside of box. If moved or fuzzy then maybe problems with beam position or magnets.
- 3.c: 1-d histogram of e-arm y-target position fitted. FIt the three peaks. If sigma is wider then maybe beam unstable. If moved then probably beam has moved.
- 3.d: 1-d histogram of h-arm y-target position fitted. Fit the three peaks. If sigma is wider then maybe beam unstable. If moved then probably beam has moved.
- 3.e: 2-d histogram of theta target vs. phi target for e-arm gated on middle waterfall target. Box is to guide the eye.
- 3.f: 2-d histogram of theta target vs. phi target for h-arm gated on middle waterfall target. Box is to guide the eye.
- 3.g: 2-d histogram of missing energy vs. missing momentum. Polygon is cut used to identify hydrogen.
- 3.h: 1-d histogram of missing energy with ¹H cut. Fit of peak position and width. If peak position moved than beam energy probably changed. If wider maybe problem with beam stability. Write down peak position and width.
- 3.i: 1-d histogram of missing energy with not ¹H cut. Fit of peak position for p1/2 and p3/2 states. Write down peak positions and widths.
- 3.j: 1-d histogram of helicity signal. Number of plus and minus helicity states should be equal with small amount of undetermined helicity (=0). If helicity = 2 has any counts then there is a problem and one should talk to an expert.
- 3.k: 1-d histogram of polar angle theta (deg). Write down ratio of sum between 5 and 20^o to total sum.
- 3.l: 1-d histogram of zclose (cm).
- 3.m: Four 2-d histograms of VDC quantites versus the difference between the VDC quantity and the FPP quantity projected to the VDC position. The main purpose of these histograms is to look for problems with the data readout because the read out of the data from the ROCs for the VDC data and the FPP data could get out of synch. If the data is corrupt then the histograms would be random instead of a correlation.
- 3.n: Four plots of the chi-squared of the track for the front U and V and the rear U and V chambers.
Execute paw kumac fpp_det . Will cycle through plots of scintillator ADCs and TDCs, ADCs for the electron gas Cerenkov, VDC crude positions and drift times, 24 FPP wire maps, 8 FPP demux summed for each chamber U and V planes, 8 FPP TDC summed for each chamber U and V , and four histograms of the number of hits in the track for the front U and V and rear U and V chambers. From the number of hits the efficiency is calculated. The absolute efficiency is the number to write down.

Instruction for fast reject software

Use program SK_data in the ,b> /work/halla/e89033/filter directory to filter data. The program calculates the scattering angle theta_az of the protons in the Carbon analyzer of the FPP and writes in the filtered data file the events that have 4^o < theta_az < 30^o. To run the program modify the input data file named SK_data.inp as in the following example:

detmap.config	! detector map file name (max 64 char)
/cache/halla/com97/raw/com97_6508.dat	! input data file name (max 64 char)
com97_6508_c.dat	! output (filtered) file name (max 32 char)
db_coin_new	! database file name (max 64 char)
1 1000000000	! first \& last events to analyze(Fortran format I5, I15)

The program uses the following files, which are now located in the /work/halla/e89033/filter directory:

fpp_alignment_front.dat
fpp_alignment_rear.dat
fpp_demux_cuts.dat
fpp_drift_dist_fits.dat
fpp_toffset_crude.calib
fpp_toffset_ref.calib
SK_data.inp

If you want to run the program from a different directory, you should copy all these file to the same directory.

Instructions for making ntuples of beam position monitor data from EPICS

Luminita Todor wrote software to extract the EPICS BPM info from the data file and make an ntuple of the info.

Type ~luminita/bpm/bpm_see

Follow program instructions.

The program produces the file b#.hbook .

Start paw++ and open the file b#.hbook .

To look at the beam position monitors versus time run the paw_kumac beam_pos . b3x and b3y are the BPMs closest to the target.

Gilles Quéméner has written instructions / a kumac to look at BPMs across several runs.

Instructions for scaler summaries

At the end of the run the scalers for the run are appended to the file /home/adev/scaler/scaler_history.dat . To help print out the scaler rate (in Hz) in a one page format, a couple a TCL scripts have been written.
Go to the espace_fpp directory by typing goespace_fpp.
To look at hadron scalers type wish read_hscalers. A window pops up. Enter the run number and push the update button. While the button is down the script is looking for the data which may take awhile so be patient. Once you get the data to the screen press the print the scalers to a file.
To look at electron scalers type wish read_escalers. Follow above directions.
Put scaler print outs in the binder.
Fill in the list of non-helicity gates and helicity gated scalers in the binder. The first scaler output (run 1621) has highlighted the scalers which are on the list. To calculate deadtime use the formula DT = 1- [TS-output/(TS1/TS1prescale + TS3/TS3prescale + TS5/TS5prescale)] The prescales should be on the runsheet.
The V-to-F is the beam monitor scaler. TS1 is the electron arm singles. TS3 is the hadron arm singles. TS5 is the coincidence rate. TS-output is the output rate from the trigger supervisor. h-.pul.h-gat and h+.pul.h+gat rates are the rates of the helicity gates and they should be the same and not change during the run for any reason. The superperiod and scalread rates are used the in ``parity'' helicity scheme. The superperiod should be about 0.1~Hz and the scalread should be exactly half of the superperiod rate. All rates are determined from the reference clock which is at 1000Hz, but to what accuracy is uncertain.

Return to 89033 detector overview .

All problems with this dcument are the fault of the translation. Please send any comments on this page to Ronald Gilman, gilman@cebaf.gov.

Created July 7, 1996 Mark Jones

Revised July 17, 1997 latex -> html Ronald Gilman