Privacy and Security Notice

Archived Messages for CLAS_DRIFT_CHAMBERS_1996@cebaf.gov: mtg at TJNAF Sat morn at 10am?

mtg at TJNAF Sat morn at 10am?

Steven Dytman, Univ of Pittsburgh (DYTMAN@vms.cis.pitt.edu)
Thu, 05 Dec 1996 21:32:15 -0500 (EST)

Friends,
My last class is tomorrow, I am finally getting clearance to come to
Newport News.

Talking with Mac this morning, he brought up an idea he and I discussed
weeks ago. We desparately need a full DC meeting to plan and coordinate
work over the next few months. I hear of lots of good work getting done
at CLAS, and it seems Mac is doing a great job coordinating things.
However, I know there is lots left to do also and I worry that in the
rush to get things in, we might be leaving off some important tasks.
Mac suggested I make a tentative agenda with the 1st item being
to decide what the agenda really is. I think that's right, because we
each have different ideas. Nevertheless, I would like to insist that
we devote at least half the meeting to plans of a general nature with
particular emphasis on devloping a priority scheme and tacking names
onto important tasks. One result might be to name a coordinating
committee (no more than 3 people) to develop this scheme and list if
we can't get agreement among ourselves.

Mac and I agreed on a meeting time of 10am Saturday at the CEBAF center.
The idea was to have it on a day when normal work obligations don't hold
and have a natural ending (or dividing) time at noon. See Mac if you
think that's wrong. I arrive late Friday night.

I benefitted from discussions with Mac and Jim Mueller in writing this
list.

AGENDA IDEAS

1. set agenda
2. set up check list of tasks for installation?
install sectors
install cables
work up HV to operating values
verify signals at STB (scope) (make list of dead and hot wires=file)
install pulser system (***can be done in parallel with previous 4
items. is this getting enough priority?)
install ADBs
verify signals at output of ADB (scope)
set up cosmic ray trigger (*** can also be done in parallel)
verify signals at TDC with computer (trigger? timing?)
pulse wires and verify in computer (software?)
2a. Identify people (mostly already working at it!) to do these
things.
3. discuss progress to date (using checklist?)
4. define tasks remaining before Feb 1 (broadly)
discuss what is possible for Feb 1. Do we have the manpower and
resources to have everything in for Feb. 1. If not, priorities become
more important.
5. discuss pulser test progress and identify people to make it
happen. To me, this is almost as important as installation
of detectors because the first channel that works all the
way through tells us we can get all 30,000 later.
6. discuss software needed for commissioning drift chambers. identify
missing capabilites and identify manpower available to make it happen.
(This is hopefully clear after we discuss 4 and 5. Maybe, we have
to devote all manpower to installation and initial checkout. I
think that would be a mistake.)
monitor program
recsis program
CLAS event display
I have read Monitor program and talked to Jim Mueller about
Recsis a number of times. I know almost nothing about CED. My general
impression is that the software we have is inappropriate for a situation
when not much works. Monitor has no discrimination and Recsis only looks
for golden high quality events. If Recsis sees too many or not enough
track segments, it quits.
-There aren't enough simple counters to log good events and bad events
according to type, i.e. is there a bad (impossible) word in the BOS bank?
Do events tend to have lots of hits or small number? Do hits tend to
cluster?
-There are no cuts in monitor program, I worry we will see mostly
noise and not learn what we really want. We also need a way
to learn a lot about a particular wire that is behaving badly,
what is STB, HVTB, who are neighbors?
-Is there a way to put cuts on CED display? Here, I am blind.
-With all the experience we have in the group, I bet we can
make great lists of things that aid understanding of chamber
performance.
7a. discuss order and priority for tests with cosmic rays.
7b. discuss order and priority for tests with beam.
These of course are closely related. We can do cosmic ray tests
instead of beam for many tasks. Nevertheless, I have NEVER
done an experiment where we got a lot of useful cosmic ray data
before beam came on the 1st time. THe record is safe so far,
installation is just too complicated.
Identify wires in specific TDCs, plateau chambers come to mind
right away as tasks that will keep us busy a long time.
We can go further if time and/or inclination.

This is best I can do for now, I hope this is useful. See you
all soon.

regards,
Steve