Updated Messages Distributed to the FPD Collaboration
Ricardo Ramirez-Gomez
06 December, 2002
FPD D0 Integration Meetings - Minutes
The minutes for the FPD D0 integration today's meeting
will be located in
http://d0server1.fnal.gov/projects/FPD/Hardware/Trigger/meetings/
I appreciate your comments.
______________________________________________________________________
Christophe Royon
06 December, 2002
list of tasks for Moriond
Dear all,
Here is a list of people/tasks for Moriond. We will discuss it a the
next
QCD meeting on Thursday. The idea is to get the different results for
Moriond at the end of January / February. We will meet once or twice a
week informally to get everything ready by then.
Thanks
Cheers
John~~
Christophe
List of tasks for Moriond 2003:
================================
Aim: - dijet mass cross section
- inclusive p_T spectrum
- jets for rapidity gap events, comparison with standard jets
- tag vs rapidity gap (depends on AFE)
- elastic events
People:
========
Alexander Kupco, Greg Davis, John Krane, Christophe Royon, Mike Strang,
Pavel Demine, Vivian O'Dell, Markus Wobisch, Jorge Barreto, Jorge
Molina,
Doug Chapin, Nikolai Skatchkov, Patrice Verdier
Topics:
========
Jets:
=====
1) Efficiencies for Jet ID cuts (to be calculated for both jet
analyses
as a function of p_T) Greg, Pavel
2) Efficiencies for event cuts (to be calculated for both jet analyses
as a function of p_T) Greg, Pavel
3) Jet Energy Resolution
Raw Data Resolution (including 3rd jet), Alexander
MC Particle Level Correction, Markus
Photon-Jet Resolution Check, Nikolai
4) Unsmearing Method, Alexander, Christophe, John, Greg
5) Eta Bias Studies, JES, Vivian
6) NLO QCD Prediction checks
Rsep ok?, Jet algo consistent?, Markus
7) jet and min. bias data stripping, Alexander, Patrice
8) MC production (check everything we need is there), John, Christophe
9) Lumi calculation for strimmed sample, Alexander
10) Dijet mass cross section, Alexander
11) pT spectrum, Greg
Diffraction:
==============
1) Rapidity gap definition, Pavel, Mike
2) Jets in diffraction compared with standard jets, Mike, Pavel
3) Elastic events, Jorge M.
4) rapidity gap data stripping, Pavel, Mike
5) Alignement studies, Jorge B., Mike
______________________________________________________________________
Christophe Royon
15 December, 2002
database / python code
Dear all,
Here is the results of a discussion Vladimir and I had last week about
the
possible improvements of the python code used for pot motion as well
as the database implementation. Please send us your
comments/suggestions.
Thanks
Cheers
Christophe
PYTHON PROGRAM ISSUES:
============================
1) Access to beam parameters and magnet currents:
==================================================
Will be done by Vladimir, should not be too difficult
2) Add time and day in the alarm window:
=========================================
can be done by Wanda?, should not be too difficult
3) HV alarm: HIGH PRIORITY
=============
The problem we are facing now is that the alarm message disappears when
the
rates are low again, and the shifter is sometimes not aware that the HV
has been
turned off. We will have now another window which will tell the shifter
that
the HV has been turned off, and the window will go away only when the
shifter
acknowleges the alarm. The other window will exist as long as the rates
are too
high. To resume, the shifter will know that the HV has been turned off,
and
when the rates are low again (when he can turn the HV on again)
Vladimir will provide this change.
4) Databases: HIGH PRIORITY
==============
We need to expand the database to account for all the variables needed
for the
offline reconstruction. This database will be available online and
offline via DB server. All the other variables which we need to keep
track of will
be recorded in the global database which runs all the time (even when we
are
not taking data). We need to get a list of needed variables. (A
preliminary
list will be sent out). This task has a very high priority since these
informations will be needed after the shutdown to be able to reconstruct
data from dipoles with AFE. Wanda will do it?
5) New EPICS word: FPD_runready: HIGH PRIORITY
=================================
Once we are integrated, we need to let D0 know when we are taking data.
The idea would be to add a new EPICS word which could be something like
FPD_runready. This work will be switched to one only when at least two
roman pots building a spectrometer are close to their operating position
(let us say for instance position > 20 mm) and the HV for the
corresponding detectors is ON.
We should process as follows:
- a stable store is declared by the captain, and the SMT/Muon HV are
turned on
- the calo/FPD shifter turns on the L0 HV, checks the rates and moves
the pot (for now, it is still the FPD shifter since we don not have any
automatised procedure) if the rates are low enough
- once the position of the pots is fixed (either the nominal position or
the position with the maximum possible value of the rates), the shifter
turns
on the FPD_runready word, and tells the captain to start a new run
which will
include the FPD. This word will be written at run start and will able us
later
on automatically in which runs (and in which lumi blocks) the FPD was
read out.
Wanda will do this with the help of Vladimir?
6) New EPICS word: allpots_home
=================================
We could add a new word which should be ok when all pots are at home.
This will
indicate the BD that they can inject (they would need only to check that
word). Vladimir can do that?
7) New alarm window in python program: HIGH PRIORITY
======================================
We need to implement a new check on LVDT position while pots are moving.
When the LVDT position is bigger than the wanted position, the pot
should
stop automatically and an alarm window should appear. This alarm is a
bit tricky
since we see fluctuations in the LVDT information when the pot is close
to home
position. This is why the alarm should be effective only when the
position
(LVDT) is above 15mm or so, and when the pot is moving.
8) Automatised pot insertion procedure: MEDIUM PRIORITY
========================================
The python program should be able by itself to insert automatically the
roman
pot detectors. The shifter will choose which pots to insert, and the
program will do the insertion procedure performed normally by the
shifter (namely,
insertion performed by steps, and check each time the rates). The
program
should stop inserting the pots either when the nominal position is
reached
or when the rates are too high. When this is done, a window should
appear telling the shifter that the pot insertion is done. The shifter
should then check the rates, turn on the MAPMT HV, switch to one the
FPD_runready word
and ask the captain to start a new run including FPD in the readout.
This work will require some changes in the python code directly. So far,
we
do not have any motion class which would be perfect for this kind of
studies.
Namely it would be good to have a class with inputs like pot name and
position
to go. So far, this is completely put inside the code. Wanda can do this
with the help of Vladimir?
______________________________________________________________________
Victor Bodyagin
18 December, 2002
summary of acces
Here is a summary of our access achievements. I prepared it as a set
of answers and comments to the questions pointed out by Andrew.
TEVATRON ACCESS
===============
Q.
1) A2 castle power - we believe the driver crate is not plugged into
the power box. Victor+Carley will verify this and replug. Jorge
will cycle control line and verify status of A2D (currently in alarm).
If this fixes problem, great! Suspect A2D may be dead, in which case
it should be brought out. If problem is power box, should swap it with
P2
and bring out power box to be repaired. Before end of access A2 control
line needs to work, else A2 should be disabled. If A2 disabled, should
switch PW08 cables from A1I A2I to P1D P2D. Spare driver can be tested
inserted at A2D if it works.
A. Yes, driver crate was not plugged into the power box. It was plugged
into the power outlet on TEV's wall and therefore it was not
controlled
by A-side toggle switch on the patch panel in D0CR. Carley and me
plugged it into controlled power box in rack A1. A2 station became
controllable by the switch but A2I LVDT readout fluctuations got
immediately back. The likliest guess is that we have ground loop
between controlling A1 and A2 racks. In this case we need to have
a separate power box in rack A2. Currently we decided to keep
A2 driver crate to be plugged into A1 power box since it is a safety
issue. After cycling the power A2D power driver got back and
seemingly
it's OK by now.
Q.
2) A2in bad A/S? Need to check all A/S cables and labels
vv' gives correlations but xx' don't and uu' are mostly dead.
Pedestal tests, then LMB tests? Verify all cables?
A.
It turned out to be the problem of cables. With the help of Jorge
we were plugging ribbon cables one by one into A/S which was
suspected to be dead. It turned out that Jorge could see nice
pedestals when cables for A2I V - V' and X - X' were plugged into it.
For U - cable Jorge did not see high pedetals and for U' the pattern
was also very poor. Unfortunately, I could not complete the job in the
CH since too little time remained and other tasks of higher priority
prevented me from starting this job. If we are lucky we can discover
and fix this problem in SCR under floor. More generally, we can
lokalize this porblem by replugging jumper cables into ribbon cables
going to SCR. In the tray an access to them is easy. Unfortunately
access
to the cables in PW08 now is difficult due to TPP installed there.
Q
3) DIPOLE LMB - We are not seeing signals at the input of the TPP from
dipole LMB. We will try to pursue some tests during collision hall
acceses, if problem persists we have to bring scope to tunnel and check
from tunnel. Should check SLP as well.
A. Yesterday we just could not make it. I need to see Pierrick.
Q.
4) TV cameras - Mike will try to contact the person that can tell us
what is wrong with the camera lights. So we fix them during the next
access.
A.
Jorge called to camera people they arrived and fixed all the problems.
They notified me that P2 camera is weak because it's old. We have
to apply for replacement of this camera ASAP . So far they have a few
more used. It will be free for us. A new camera is some 5K bucks.
Q.
5) A1O pot motion needs to be debugged. A problem sending the A1O pot
to 10 mm was detected in the previous access. We have now to
figure out what is causing the problem: mux,iib, rm, cabling?
Newton suggests a simple cable swap to isolate problem (see notes at
end).
*see comments from newton at end of message
A. At first Jorge did not see any problems with A1O motion. It was OK.
The problem got back when Carley and me left the tunnel and
surrendered
all access stuff to MCR.
COLLISION HALL ACCESS
======================
Q.
1) John Anderson+Tom Regen+Victor Martinez will prepare PW08,
check power supply monitor, put in panels, verify air flow,
remove extra power supply cables.
A. These people did their job perfectly well.
Q.
2) Installation of sequencer+AFE+VRB (George)
A. The attempt was done but failed. See Fred's and George's reports on
it.
Q.
3) TPP tests (Ricardo+Russ)--these should not interfere with
critical work of getting FPD integrated
A.
Russ, Wanda and Ricrado tested a tool suggested by Russ. This
tool should make installation of TPPs into PW08 much easier.
As Ricardo reported they were not happy with this version of a tool.
Russ is searches for a new solution.
Q.
4) System tests, downloads database etc. (Jadwiga+Victor)
A. Vladimir created a new DB. On Jadzia's opinion it's OK. She did some
tests already.
Q.
5) Afternoon safety review (Freeman+Woolfe)?
A. Done, approved and not an issue anymore.
Q.
6) LMB tests
A. We could not make it.
______________________________________________________________________
Andrew Brandt
draft of access report for dmitri and draft of next access plan
Dmitri,
Here is a report on the recent FPD access.
TUNNEL ACCESS
======================
1) The A-side driver crate was not plugged into the power box.
It was plugged into the power outlet on TEV's wall and therefore
it was not controlled by A-side toggle switch on the patch panel
in D0CR. Apparently this happened during tests of jitter in the
A2I LVDT some time ago. When the power was plugged correctly,
the remote control ability returned, but so did the A2I LVDT
instability, so there is a ground problem that needs to be
investigated further.
2) The A2D driver which was showing a major alarm reset okay when
the power was cycled and the A2D pot motion is again normal.
3) Problems with A1O pot motion were investigated, but ran out
of time--this pot is currently not instrumented and has been
disabled.
4) 2 planes of A2I detector have not been reading out properly rendering
current data not useful. The amplifiers were tested and are fine,
indicating a cable problem. Time was insufficient to track the
problem further. There is a chance that local SCR cables are to
blame--this is being investigated today (harder to pin down without
someone in the tunnel).
5) Problems with TV cameras in tunnel were fixed.
COLLISION HALL ACCESS
======================
1) John Anderson+Tom Regen+Victor Martinez prepared PW08,
check power supply monitor, put in panels, verify air flow,
remove extra power supply cables.
2) The FPD sequencer was installed but later removed due to
problems with sequencer crate. It seemed to fail when 16 sequencers
were installed but was okay with 15. Fred + Mike Utes did not have
time to investigate further, and will continue to search for solution.
3) Russ, Wanda and Ricardo tested a tool prepared by Russ for installing
future TPP boards (interface between ribbon cables and flex cables).
Tests were not successful. Solution is needed for January shutdown.
4) Database tests were successful (Jadwiga+Victor)
5) Afternoon safety review (Freeman+Woolfe+Victor) was successful
and PW08 was certified, pending division head signatures.
CONCLUSIONS:
There were some successes, but the access was of insufficient length
(combined with limited manpower during holidays) to get all of the
critical work done. The inability to get the sequencer working is a
serious setback, as we only have a few weeks before January shutdown
to get commissioning data on AFE. Given that the A2I data is not
useful, there is no point in operating until the next access, so we
are suspending FPD operations until further notice.
______________________________________________________________________
Jorge Barreto
18 December, 2002
A1O and A2I Pot Motion Problems
here is a summary of all pot motion problems related to A1O and
A2I during yesterday access.
1) When in the D0CR, I started to check what has been observed
previously, i.e., A2I could be moved when A-side CL was off and P1O
wouldn't stop when sent from home to 10mm. For A2I, I observed, of
course, that it could be moved when CL was off. However, I tried
many times to move A1O from home to 10mm and each time it stopped at
the correct position.
2) Victor/Carley had then found that A2 castle had not the drivers
connected to the power box, but to an HV outlet in the wall. They
connected then A2 to the power box of the A1 castle. I could immediately
observe that LVDT started to have large fluctuations for A2I.
3) As a final test, I sent all enabled pots from home to 20mm, to verify
that everything was OK before the access was over. When all pots were
moving, I hit the CL off, to show that pots would stop and they would
resume their coarse when ordered to move again. That, indeed was what
happened.
4) However, I observed that neither A1O or A2I didn't stop at 20mm, and
I
had to stop them by hitting the stop bottom. Then I sent all pots to the
home position, without any problem.
5) I started then to move A1O and A2I, independently, from home to 10mm,
15mm and 20mm. Most of the times, they stopped at the correct positions,
but a few times A10 kept going behind the designated position. And
during
the last time that A1O was at 20mm off home, it seems FPDGui lost the
pot
position, since the following message was appearing in FPDGui window:
P1 OUT : Bad verification of the position, new verification - home
position activated.
However, I could see on the TV that the motor was trying to spin up, but
could only spin 1 or 2 turn, after what it stopped and the same message
kept appearing again. It took more than 1 hour for A1O to go to home.
I'd
then software disabled A1O. Moreover, it was of no avail my attempts to
stop the motion by hitting the stop bottom.
6) Finally, as a last test, I sent A2I to 20mm. The pot stopped
correctly
at this positions. But when it was sent to home, it showed the same
problem described above as for A1O. Nevertheless, after a few minutes in
that situation, it started to move fast from around 15mm to 5mm without
any problem, when this kind of unknown problem started again. It also
took
a while for A2I to go from 5mm to home.
______________________________________________________________________
Andrew Brandt
19 December, 2002
Access summary/FPD operations
Dmitri,
Here is a report on the recent FPD access--more detail than usual
since we have had a couple problems that I have talked to you about.
TUNNEL ACCESS
======================
1) The A-side driver crate was not plugged into the power box.
It was plugged into the power outlet on TEV's wall and therefore
it was not controlled by A-side toggle switch on the patch panel
in D0CR. Apparently this happened during tests of jitter in the
A2I LVDT some time ago. When the power was plugged correctly,
the remote control ability returned, but so did the A2I LVDT
instability, so there is a ground problem that needs to be
investigated further. It should not affect normal operations
but only the readback of A2I (not used as an input to pot
motion program).
2) The A2D driver which was showing a major alarm, and we feared might
be dead, reset okay when the power was cycled and the A2D pot
motion is again normal.
3) Problems with A1O pot motion were investigated, but ran out
of time--this pot is currently not instrumented and has been
disabled.
4) 2 planes of A2I detector have not been reading out properly rendering
current data (elastic events reading out A1I and A2I detectors) not
useful. The amplifiers were tested and are fine,
indicating a cable problem. Time was insufficient to track the
problem further. There is a chance that local SCR cables are to
blame or cables at PW08--this is being investigated today (harder to
pin down without someone in the tunnel).
5) Problems with TV cameras in tunnel were fixed.
COLLISION HALL ACCESS
======================
1) John Anderson+Tom Regen+Victor Martinez prepared PW08,
check power supply monitor, put in panels, verify air flow,
remove extra power supply cables.
2) The FPD sequencer was installed but later removed due to
problems with sequencer crate (believed to be power supply
problems). It seemed to fail when 16 sequencers
were installed but was okay with 15. Fred + Mike Utes did not have
time to investigate further.
3) Russ, Wanda and Ricardo tested a tool prepared by Russ for installing
future TPP boards (interface between ribbon cables and flex cables).
Tests were not successful. Solution is needed for January shutdown.
4) Database tests were successful (Jadwiga+Victor)
5) Afternoon safety review (Freeman+Woolfe+Victor) was successful
and PW08 was certified, pending division head signatures.
CONCLUSIONS:
There were some successes, but the access was of insufficient length
(combined with limited manpower during holidays) to get all of the
critical work done. The inability to get the sequencer working is a
serious setback, as we only have a few weeks before January shutdown
to get commissioning data on AFE. Given that the A2I data is not
useful, there is no point in operating until the next access
(not sure whether collision hall access is sufficient),
so we are suspending FPD operations until further notice.
Operations will resume when either A2I is fixed or Sequencer/AFE are
installed.
______________________________________________________________________
Gregorio Bernardi
06 January, 2003
Thanks to help the Speaker's Bureau for missing slides of your 2001/2002
talk
Dear Colleague,
as you know we have been collecting slides and proceedings of all the
talks in 2001 and 2002 given by D0 collaborators and stored in the SB
database, and we are continuing with 2003, such that everybody can have
immediate access in a central place to all the D0 slides shown at
conferences.
We have now the majority of these slides/proceedings in a web
page and are storing them in the official SB database. The web page is:
http://www-d0.fnal.gov/~d0conf/2002.html (includes 2002 and 2001)
but as you will be able to see, at least one talk that you have been
given
is not in our hands and so could not be linked:
Just search for your name in the web page, and you will see which talk
is
missing, since there will be explicitely written:
"no slides received from 'your name'" attached to the conference info.
Note that you must repeat the search for all occurences of your name:
For instance if you have given 2 talks we might have received one, and
not
the other, or both could be missing.
Or you could be listed for a talk not given if it's a SB mistake, so
we need your help to clarify these "missing slides" and it's important
that these kind of mistakes be corrected. Do not worry if the missing
talk
is not a "D0 talk" but a more general one, since we anyway want to
collect
the slides of the D0 collaborators, and the SB pays attention to the
fact if a given talk is "D0" or not when discussing future
assignments.
We have been also collecting the associated proceedings, so if you have
them please forward them as well.
The Speaker's Bureau is planning to render public this page at the end
of
this week, so thanks to forward your missing slides/procs as soon as
possible, and also excuse us if you already forwarded them and they got
lost in all the movements (we received about 200 ps/ppt/pdf files).
Thanks to store temporarily your files on d0mino with the correct
convention and notify me, I will reply back as soon as I have copied
them
in the SB space.
reminder:
the name convention is for talks 021225-BERNARDI-talk.ppt or pdf or ps
for procs 021225-BERNARDI-proceedings.ps or ...
the date is the beginning date of the conference (given in the web
page).
Putting them on d0mino with the correct name greatly reduces the burden
of storing them properly later.
Thanks again and happy new year
Gregorio for the Speaker's Bureau
______________________________________________________________________
Michael Strang
06 January, 2003
Results of today's tunnel access
Today, Pierrick and I entered the tunnel. We accomplished the following:
-We verified that the Dipole LMB is working (i.e. the LEDs are producing
light) in the tunnel. We still need to determine why signals were not
seen at PW08. This will need to be accomplished during the January
Shutdown.
-We replaced the Driver Control box for A2 and verified that it works.
We repositioned the driver box to a location behind the concrete wall to
hopefully protect it from radiation since this box seems to fail often.
-We tried to verify the mapping for A2 using a controlled light leak
through the LMB bulkheads since we had mapped LMB bulkheads to MAPMTs.
It appears that V, X, U' and M are mapped properly but U shows no dark
signal in the SCR. We were unable to verify presence of dark signal in
the tunnel so this problem still needs to be studied further during the
January shutdown.
-Pierrick says that the only remaining tasks for the tunnel ORC are to
replace the extension cords between the 1 and 2 stations on both the
A and P side with a conduit which we should be able to do ourselves. We
also need to replace an extension cord to P1 that passes over the beam
with a conduit but this would require the help of FNAL electricians.
Pierrick says that he had sent out a previous email with the required
dimensions needed and he will look for it.
______________________________________________________________________
Jorge Luis Barreto
06 January, 2003
Summary of today access
Hello,
During the controlled access today, I sat in D0CR and performed
the
following tasks:
1) Made sure all HV were off;
2) Tested A2 pot motion with the new power box and verified it is OK;
3) Debugged A1O pot motion by sending the pot from home to different
positions, including the 10mm one. No problems with pot not stopping
at 10mm was observed. However, I've noticed the same previous problem
when sending pot back home: it starts spinning then stops and get
stacked for while, then starts spinning again, and so forth. A1O is now
at home position and disabled.
4) Tested A2I pot motion without any related problem. LVDT seems OK now
for A2I.
5) Tested pot motion for D1-D2. At the beginning, sent pots to 10 and
15mm
and back home without problem. At the very end, sent the pots to their
operational positions within three steps: 15mm (fast), 25mm (fast), and
28.68mm (slow) and 30.98mm (D1-slow). Although every step was fine, D1
didn't stop at 30.98 in the last step, and went all the way down to
37mm!
Had no time to verify in detail this problem. Need to be checked during
next access.
6) Observed signals in SCR coming from tunnel for A2I cables. See
Mike Strang report in this issue.
______________________________________________________________________
Victor Bodyagin
07 January, 2003
summary of CH supervised access and more..
today I studied PW08 cabling problem further. Seemingly the solutions
I suggested before this access will not work. It turned out that
L-like shape of the combs causes most of the alignment problems since
the cables are coming to the comb through the gaps between the teeth
at slightly different angles and their connectors are touching
the other (lower) side of the L at different points and resist the
alignment.
The solutions suggested by Russ is as follows:
Removal of extra metal from _ -side of the "L" right beneath the
connectors will make alignment much easier. After the alignment
and plugging into TPP cables can be fixed at the comb in different
way.
So, I took one comb out and gave it to Russ. In the very
beginning
of shutdown we'll try it.
Also today Vladimir created a new development DB for 8 AFE
configuration.
Ricardo Ramirez
11 January, 2003 23:11
FPD D0 Integration Meetings - Minutes January 10th, 2003
The minutes for the last FPD D0 integration meeting
will be located in
http://d0server1.fnal.gov/projects/FPD/Hardware/Trigger/meetings/index.html
I appreciate your comments.
______________________________________________________________________
Michael Begel
January, 2003
Luminosity by Reco Version
Following the discussion in today's QCD meeting, I decided to dump the
reconstructed luminosities by reco version. The total for p13.05 was
20.6 pb-1 (out of 75.7 pb-1 recorded). Here are the numbers for the
rest of the Moriond sample (all values in pb-1):
January 2003:
recorded : 7.00
p13.05.00: 0.13
December 2002:
recorded : 16.88
p13.04.00: 4.42
p13.05.00: 11.40
November 2002:
recorded : 15.43
p13.02.00: 8.48
p13.03.00: 4.52
p13.04.00: 1.77
p13.05.00: 7.41
October 2002:
recorded : 13.92
p11.12.01: 1.95
p11.13.00: 4.43
p13.02.00: 2.29
p13.03.00: 4.11
p13.04.00: 6.92
p13.05.00: 0.18
September 2002:
recorded : 10.23
p11.11.00: 1.45
p11.12.01: 2.71
p13.05.00: 1.49
August 2002:
recorded : 6.35
p11.09.00: 0.0021
p11.10.01: 0.63
p11.11.00: 2.03
July 2002:
recorded : 5.40
p11.09.00: 1.85
p11.10.01: 0.41
June 2002:
recorded : 0.52
p10.15.02: 0.15
p11.08.00: 0.0027
p11.08.02: 0.11
p11.09.00: 0.23
p11.10.01: 0.033
p11.11.00: 0.032
p11.12.01: 0.037
p11.13.00: 0.012
p13.02.00: 0.012
______________________________________________________________________
Victor Bodyagin
14 January, 2003
access plans, schedule and results of the first day
let me inform you about the results and the problems of the first
day of shutdown.
Problems:
1. John Andersson has to take medical evaluation for ODH otherwise
he will not be allowed to visit the tunnel. He'll get it soon.
2. Due to cooling problems most of d0online machines were down.
So we could not start any work related with pot motion and DAQ.
Results:
1. Mike and George removed A2I detector. Tomorrow Mike will proceed
with building detectors.
2. Carley, Ricardo and me were busy with PW08 comb - TPP problems.
The improvements of the comb done by Russ did not work. The alignment
needs to be improved. Also one more problem was discovered. We need
to shift by 1/2'' the frame with combs to the east otherwise
the ribbon cables coming into the rack will prevent TPP #1 from
installation. Tomorrow morning I'll see Russ.
Main goals:
A2 vacuum repairs, surveying, and refurbishing
12 detectors+6 pseudodetectors installed (see detector goals)
A2I+D2 LVDT stability
Pot motion tests (especially A1+A2 castle)
ORC in tunnel
2 new AFE's+TPP's -> phase I of FPD 10 detectors in readout
pot motion upgrades
new LVPS tests
LMB system decoupled from calorimeter+fully functional and in readout
Prior to access:
Detector preparation, new pseudo-detectors prepared, all cables ready
Mike+Carley
TPP tool ready +tests of 2nd+3rd TPP board Ricardo+John A.
LMB pin diode adapter Pierrick?
3rd AFE time (Ricardo)
Driver tests+new LVPS tests (Victor)
Preparation of new power boxes for A2+P2? (Victor+Pierrick+technician?)
Detector goals:
Overall plan is to have real (tested) detectors in all up and down
locations
and dipoles
and A1I+A2I and pseudo detectors at other 6 locations.
real detectors in:
D1,D2,P1D,P2D,P1U,A1D,A1I already there (mike mentioned moving A1I to A1U
but
I
don't know why?)
P2U needs new detector and modified cartridge top
A1U, A2U, A2I, A2D will need to be installed
pseudo-detectors:
P1O+P2O already in place
P1I+P2I use old prototype detectors as pseudo detectors --cartridge
bottoms
don't
need to be modified
A1O+A2O need to be prepared
**********************************
Tunnel:
1) work on A2 castle
Jan. 13 pot motion tests on A2 castle, remove A2I detector (1 hour) Mike
A2I grounding tests,LVDT tests (Victor)
Jan. 14 remove A2 motors+encoders (time Sergio?) Carley+Victor
Jan. 15-23? vacuum repairs to A2 castle (schedule Mike M.?)
Jan. 24-25 surveying A2 castle
Jan. 27-28 refurbishing of A2 castle motors+encoders Carley+Victor
pot motion tests on A2 castle
Jan. 29 install detectors: A2I+A2U (new) 1 hour each A2D 2 hours, A2O
pseudodetector 1 hour
Jan. 30 A2 detector and cable tests
2) installation of other detectors:
Jan. 14 P2U modify cartridge top, put in new detector+test Mike+Jorge
insert new detector in A1U and test Mike+Jorge
Jan. 15 A1O+A2O P1I+P2I pseudo detectors installation +testing
Mike+Carley
3) Jan. 14-15 AIO castle pot motion tests Victor+Wanda
4) Extension cable work done for ORC (Mike M.+electricians?)
Final ORC well before end of access
5) cable repairs:
Jan. 16-17 week of Jan 20 Carley+Jorge (tech help needed?)
6) lmb tests:
part of detector testing (Mike)
pin diode signals to AFE? (Pierrick?)
7) add sandbags around electronics+beampipe (Mike M.+Victor)
8) more pot motion tests as needed
Platform (PW08):
1) Jan 13 or from first access installation of 2 TPP's
(Ricardo+Russ/tech)
may involve recabling of PW08 to allow for 5 TPP operation in fall?
2) Cable repairs
3) 3 AFE+ 1 DFE installation
4) test spare sequencer?
Control room:
pot motion upgrade tests (Wanda)
AFE tests (Victor+Ricardo)
______________________________________________________________________
Christophe Royon
15 January, 2003
EPICS / ACNET Variables for database
Here is the list of variables we would like to keep offline and
online in the archiver. Note that the variables in the archiver cannot be
accessed from D0Reco but they can be checked at any time. This means
that all variables needed in the D0reco code have to be in the FPD
database. Please let us know if all these variables are needed in the
reconstruction code and if this is enough (no missing variables)
Thanks
Cheers
Wanda
Vladimir
Christophe
LIST OF FPD ACNET AND EPICS VARIABLES:
=========================================
1) List of variables needed offline (FPD database)
===================================================
ACNET | EPICS | meaning
====================================================
C:D0Q2 | FPD_ACNET_QUAD/Q2 | Q2 low beta quadrupole
C:D0QT2 | FPD_ACNET_QUAD/QT2 | Q2 trim low beta quadrupole
C:D0Q3 | FPD_ACNET_QUAD/Q3 | Q3 low beta quadrupole
C:D0QT3 | FPD_ACNET_QUAD/QT3 | Q3 trim low beta quadrupole
C:D0Q4 | FPD_ACNET_QUAD/Q4 | Q4 low beta quadrupole
C:D0QT4 | FPD_ACNET_QUAD/QT4 | Q4 trim low beta quadrupole
C:C4HSP | FPD_ACNET_SEPC49/C4HSP| C49 horizontal separator
C:C4HSM | FPD_ACNET_SEPC49/C4HSM| C49 horizontal separator
C:C4VSP | FPD_ACNET_SEPC49/C4VSP| C49 vertical separator
C:C4VSM | FPD_ACNET_SEPC49/C4VSM| C49 vertical separator
C:D1HSP | FPD_ACNET_SEPD1/C4HSP | D11 horizontal separator
C:D1HSM | FPD_ACNET_SEPD1/C4HSM | D11 horizontal separator
C:D1VSP | FPD_ACNET_SEPD1/C4VSP | D11 vertical separator
C:D1VSM | FPD_ACNET_SEPD1/C4VSM | D11 vertical separator
T:HPC48 | FPD_ACNET_BPM/HPC48 | horizontal BPM
T:VPC48 | FPD_ACNET_BPM/VPC48 | vertical BPM
T:HPC49 | FPD_ACNET_BPM/HPC49 | horizontal BPM
T:VPC49 | FPD_ACNET_BPM/VPC49 | vertical BPM
T:HPD0U | FPD_ACNET_BPM/HPD0U | horizontal BPM
T:VPD0U | FPD_ACNET_BPM/VPD0U | vertical BPM
T:HPD0D | FPD_ACNET_BPM/HPD0D | horizontal BPM
T:VPD0D | FPD_ACNET_BPM/VPD0D | vertical BPM
T:HPD11 | FPD_ACNET_BPM/HPD11 | horizontal BPM
T:VPD11 | FPD_ACNET_BPM/VPD11 | vertical BPM
T:HPD12 | FPD_ACNET_BPM/HPD11 | horizontal BPM
T:VPD12 | FPD_ACNET_BPM/VPD11 | vertical BPM
T:D0UHPP | FPD_ACNET_CPM/D0UHPP | D0 upstream horizontal proton
position
T:D0DHPP | FPD_ACNET_CPM/D0DHPP | D0 downstream horizontal proton
position
T:D0UVPP | FPD_ACNET_CPM/D0UVPP | D0 upstream vertical proton
position
T:D0DVPP | FPD_ACNET_CPM/D0DVPP | D0 downstream vertical proton
position
T:D0UHNP | FPD_ACNET_CPM/D0UHNP | D0 upstream horizontal pbar
position
T:D0DHNP | FPD_ACNET_CPM/D0DHNP | D0 downstream horizontal pbar
position
T:D0UVNP | FPD_ACNET_CPM/D0UVNP | D0 upstream vertical pbar
position
T:D0DVNP | FPD_ACNET_CPM/D0DVNP | D0 downstream vertical pbar
position
T:D0UHDF | FPD_ACNET_CPM/D0UHDF | D0 upstream horizontal p pbar
position
T:D0DHDF | FPD_ACNET_CPM/D0DHDF | D0 downstream horizontal p pbar
position
T:D0UVDF | FPD_ACNET_CPM/D0UVDF | D0 upstream vertical p pbar
position
T:D0DVDF | FPD_ACNET_CPM/D0DVDF | D0 downstream vertical p pbar
position
T:IRING | FPD_ACNET_D1/IRING | Tev dipole magnet
In addition, all pot positions which are already being written out in the
database (names: FPD_RM_A1UP/POS ...., infos from LVDT, and
FPD_SCALER_A1/UP...), and all alarms (FPD alarms, HV alarms)
Should we also provide a list of dead channels, hot channels, HV
values for each MAPMT... in the offline DB?
Remark: order in the tunnel
=============================
HPC48 - VPC48 - D1/D2 pot - IRING - VPC49 - HPC49 - A2 pot - C4HSP - C4HSM
- C4VSP -
C4VSM - A1 pot - D0Q2 - D0QT2 - D0Q3 - D0QT3 - D0Q4 - D0QT4 - HPD0U -
VPD0U -
D0 detector - VPD0D - HPD0D - D0Q4 - D0Q3 - D0Q2 - P1 pot - D1HSP -
D1HSM - D1VSP - D1VSM - P2 pot - HPD11
2) List of variables needed for monitoring (Archiver)
=======================================================
ACNET | EPICS | meaning
====================================================
T:IBEAM | FPD_ACNET/IBEAM | total beam intensity in the
Tevatron
T:IBEAMB | FPD_ACNET/IBEAMB | total beam intensity in the
Tevatron
| | (for intensity > 1E13
C:FBIPNG[0-36] | FPD_ACNET/FBIPNG0... | TEV narrow gate fast bunch
integrator
| ...36 | intensity (proton intensity)
C:FBIPWG[0-36] | FPD_ACNET/FBIPWG0... | TEV wide gate fast bunch
integrator
| ...36 | intensity (includes proton
| | satellite bunches intensity)
C:FBIANG[0-36] | FPD_ACNET/FBIANG0... | TEV narrow gate fast bunch
integrator
| ...36 | intensity (pbar intensity)
C:FBIAWG[0-36] | FPD_ACNET/FBIAWG0... | TEV wide gate fast bunch
integrator
| ...36 | intensity (includes pbar
| | satellite bunches intensity)
T:WHEP00[0-143]| FPD_ACNET/WHEP000 ...| TeV horizontal proton normalised
| ...143 | emittances
T:WHEA00[0-143]| FPD_ACNET/WHEA000 ...| TeV horizontal pbar normalised
| ...143 | emittances
T:WVEP00[0-143]| FPD_ACNET/WVEP000 ...| TeV vertical proton normalised
| ...143 | emittances
T:WVEA00[0-143]| FPD_ACNET/WVEA000 ...| TeV vertical pbar normalised
| ...143 | emittances
T:RFSUM | FPD_ACNET/RFSUM | TeV proton RF voltage
T:RFSUMA | FPD_ACNET/RFSUMA | TeV pbar RF voltage
C:D0PHTL | FPD_ACNET_LOSS/D0PHTL| D0 proton losses
C:D0AHTL | FPD_ACNET_LOSS/D0AHTL| D0 pbar losses
C:D0FLTL | FPD_ACNET_LUMI/D0FLTL| D0 Lumi
______________________________________________________________________
Victor Bodyagin
16 January, 2003
access updates
today Carley and me were in the tunnel in order to make a preview
of the problems we have to solve to get ORC. Tomorrow I'm going
to bring John there and discuss work necessary to be done and
man power help we need from him. John is ODH approved now.
First I have to notice that A2 castle was not taken for baking yet.
The situation with the racks in the tunnel is as follows:
1. All of them need additional front covers for closing air flow.
2. A1, P1 racks need red power cords extenders to be replaced.
3. D1/D2 racks look more or less complete.
Probably this is only part of the problems we have.
Also D0 online cluster got back and we can run software on it.
1. FPDGui is running.
2. DAQ is running.
3. SCR electronics is ON.
______________________________________________________________________
Ricardo Ramirez
16 January, 2003
D0 minutes server - D0 Integration meeting
Dear All,
Frank Filthaut has added a location for our 'D0 Integration
meetings'.
The link is as follow.
http://www-d0.hef.kun.nl///displayLevel.php?fid=43
The required password for accessing the D0 minutes server
is the same that we use for going to private areas in
d0 domain.
______________________________________________________________________
Victor Bodyagin
17 January, 2003
access progress updates
here are some news on our access progress.
1. Russ and me discussed comb issues and seemingly we've found a good
solution.
2. Tomorrow John Anderson will'be in the tunnel so we'll be able
to work out our ORC plans and define the amount of manpower from
him to help us.
3. At 2:30 p.m. Doug called to Sergio's office and asked me about
the readiness of A2 castles to be moved for baking. Tomorrow
morning we'll know the results.
4. Wanda, Carley, George, and me started to scan
all cables and A/Ss for bad channels. Within some 3hours
we've scanned P1U, P1D, P2U, P2D, A1I, A1O, A2I, A2O, i.e.
all vertical P and horizontal A quads. Tmorrow we'll proceed.
5. Our sequencer is expected to be taken out temporaly in order
to make a spare one.
______________________________________________________________________
Victor Bodyagin
17 January, 2003
access updates
here are access updates for Jan 17.
1. John Anderson and me were in the tunnel this morning.
John made a thorough review of all our racks.
I expect to get the full list with is remarks on Tuesday.
The biggest issue will be replacing of power cord
extenders by normal cords.
2. Russ Rucinsky promised that we'll get a new comb no later then
Tuesday afternoon.
3. A2U is installed back and showed no vacuum leakage so far.
Vacuum team people told me that there is a big chance that we do not
need baking at all. Final decision we'll be made up on Tuesday
morning.
4. Wanda, Carley, Jorge, and me proceeded with A/Ss+cable scan.
The first pass is completed practically except D1 and D2.
Analysis is underway.
______________________________________________________________________
Victor Bodyagin
19 January, 2003
A/Ss and cable scan results
here are the results of scan over all FPD from A/S outputs to SCR.
The scan was done in the following way:
jumper cables were beeing replugged in PW08.
Note that each FERRA ADC in SCR corresponds to the same jumper and
RC going from PW08 to SCR. So it is very likely that correlated
bad channels in each ADC mean jumper or RC problem and in fact
A/S + RC route from the tunnel to PW08 is perfect.
D1/D2 scan was not done yet because of TPP sitting in PW08. Guys who can
remind me numbers of data taking runs for D1/D2? We can get the similar
map for them on real data.
Now, the scan table is coming...
ADC0 *P1U OK* *P2U OK* *A1I OK* *A2I 7,8,9,15* *P1I OK* *P2I all dead*
*A1U OK* *A2U OK*
ADC1 *P1U 3* *P2U 0,3* *A1I 3* *A2I 1,3,6* *P1I 3* *P2I all dead* *A1U 3*
*A2U 3,7*
ADC2 *P1U 0,2,4,5* *P2U 0,2* *A1I 0,2,13* *A2I 0,2* *P1I 0,2* *P2I all
dead*
*A1U 0,3* *A2U 0,2*
ADC3 *P1U OK* *P2U OK* *A1I 12* *A2I OK* *P1I OK* *P2I 0,8* *A1U OK*
*A2U 0*
ADC4 *P1U OK* *P2U OK* *A1I OK* *A2I OK* *P1I OK* *P2I
1,10,11,13,14*
*A1U OK* *A2U 3,5,13,14,15 (low tune?)*
ADC5 *P1U 6* *P2U OK* *A1I OK* *A2I OK* *P1I OK* *P2I many dead*
*A1U OK* *A2U OK*
ADC6 *P1U 1,2* *P2U 0,1,2* *A1I 1,2,13* *A2I all dead* *P1I 2* *P2I
1,2,8,13*
*A1U 1,2* *1,2*
ADC7 *P1D 5,8,11,12* *P2D 2,4,5,6,8,11,12,14* *A1O 5,8,11,12* *A2O
5,8,11,12*
*P1O 5,8,11,12* *P2O all dead* *A1D 5,8,11,12* *A2D all dead*
ADC8 *P1D 15* *P2D 15* *A1O 15* *A2O 15* *P1O 15* *P2O 15* *A1D 15*
*A2D 15*
ADC9 *P1D 5* *P2D 5,8* *A1O 5* *A2O all dead* *P1O 5* *P2O 5,6,9,10*
*A1D 5* *A2D 4,5,11*
ADC10 *P1D 5* *P2D 5* *A1O 5* *A2O all dead* *P1O alldead* *P2O 1,5,6*
*A1D 5* *A2D 5*
ADC11 *P1D 1,14* *P2D 1,14* *A1O 1,14* *A2O 1,14* *P1O 1,14* *P2O all
dead*
*A1D 1,14* *A2D 1,14*
ADC12 *P1D 0,15* *P2D 0,5,15* *A1O 0,15* *A2O 0* *P1O 0,15* *P2O all dead*
*A1D 0,15* *A2D 0,1,15*
ADC13 *P1D 0,13* *P2D 0,13* *A1O 0,13* *A2O 0,13* *P1O all dead or
untuned*
*P2O 0,13* *A1D 0,13* *A2D all dead*
______________________________________________________________________
Jorge Luis Barreto
20 January, 2003
A/Ss and cable scan results
From your message, I've prepared a table containning the
results of the A/Ss and cables' first scan from Tevatron tunnel to
SCR. You can find either a chan_list_012003.doc (text) or a
chan_list_012003.sdw (soffice) in
http://www-clued0.fnal.gov/~barreto/fpd/
______________________________________________________________________
Victor Bodyagin
January, 2003
access updates and plans
here are our news and plans.
The biggest news is that A2 castle is ready for pot motion tests.
Carley and Jorge completed the reinstallation of step-motors,
encoders and LVDTs on all four pots.
Plans:
Tomorrow:
1. Carley, Jorge and me will perform pot motion tests.
2. Ricardo and me will test a new comb for TPP.
Sunday:
1. Cristophe will perform LVDT calibrations.
Monday:
1. a 30-minute FPD operations meeting at 9a.m.
2. A2 survey is expected to be done.
______________________________________________________________________
Victor Bodyagin
26 January, 2003
A2 motion test results.
today Carley, Jorge and me were testing A2 pots' motion.
1. All pots are moving well, i.e. the have smooth running
and stop in right positions: home, 30mm, 15mm, 10mm etc.
2. The values of LVDT readouts for A2D and A2I are OK and can be
calibrated.
3. The values of LVDT readouts for A2U and A2O are smaller by
factor of ~100 in comparison with those for A2D and A2I.
They can not be calibrated and we are looking into the
problem.
4. A2I readout flucuates as usually.
______________________________________________________________________
Victor Bodyagin [bodyagin@fnal.gov]
Sent: 27 January, 2003 23:31
To: D0FPD_LOCAL@listserv.fnal.gov
Subject: [D0FPD_LOCAL] access uodates
here are some news.
1. Apparently, A2 is in a good shape. All pots are moving well.
All LVDTs work well. Christophe is going to calibrate the
remaining A2U and A2O. The phantom of a problem with A2U and
A2O readout was caused by the scaling factor in our DB.
Since A2U and A2O were not installed LVDT were giving
arbitrary readouts. In order to avoid extra MCR complaints
that these pots are not at home position their readouts
were prescaled by factor 100. Now we got back with them.
A1O has a problem while moving to home position. It is
stacking. In forward direction it moves OK.
2. Pierrick is going to help us with TPP installation tomorrow.
3. Survey and alignment of A2 castle and pots will be finished tomorrow.
4. We need to have three TPPs installed into PW08 before Thursday.
______________________________________________________________________
Christophe Royon
28 January, 2003
calibration
The calibration LVDT vs number of turns is finished. We clearly need to
change some calibration factors for D2 for instance.
I observe a few problems:
- A2 up is blocked now in IN position and faces a mechanical failure, we
need to remove it by hand in the tunnel
- The LVDT for A2 up is not good since we are getting constant LVDT values
when going in, or the IN switch is not well placed
- The A2 out never finds its IN position
Here are the values for calibration (the plots will be made soon)
Thanks
Cheers
Christophe
POT CALIBRATION DATA 01/26/2003
====================================
pos. | A1 up | A1 down | A1 in | A1 out
===================================================
0.0 | 0.00 | 0.00 | 0.00 | 0.00
1.0 | 0.83 | 0.90 | 0.73 | 0.78
2.0 | 1.89 | 1.87 | 1.74 | 1.75
3.0 | 2.86 | 2.88 | 2.72 | 2.83
4.0 | 3.90 | 3.88 | 3.75 | 3.82
5.0 | 4.88 | 4.84 | 4.75 | 4.80
6.0 | 5.89 | 5.85 | 5.79 | 5.85
7.0 | 6.83 | 6.80 | 6.70 | 6.77
8.0 | 7.85 | 7.83 | 7.74 | 7.78
9.0 | 8.86 | 8.84 | 8.75 | 8.78
10.0 | 9.84 | 9.83 | 9.76 | 9.78
11.0 | 10.85 | 10.92 | 10.74 | 10.82
12.0 | 11.89 | 11.85 | 11.81 | 11.81
13.0 | 12.88 | 12.87 | 12.76 | 12.82
14.0 | 13.90 | 13.84 | 13.82 | 13.85
15.0 | 14.87 | 14.88 | 14.80 | 14.83
16.0 | 15.91 | 15.89 | 15.82 | 15.82
17.0 | 16.90 | 16.93 | 16.87 | 16.86
18.0 | 17.92 | 17.91 | 17.90 | 17.87
19.0 | 18.90 | 18.92 | 18.87 | 18.85
20.0 | 19.92 | 19.93 | 19.92 | 19.88
21.0 | 20.90 | 20.94 | 20.86 | 20.84
22.0 | 21.95 | 21.95 | 21.97 | 21.86
23.0 | 22.93 | 22.96 | 22.94 | 22.88
24.0 | 23.95 | 23.97 | 24.00 | 23.90
25.0 | 24.92 | 24.99 | 24.99 | 24.90
26.0 | 25.96 | 25.99 | 26.05 | 25.88
27.0 | 26.93 | 27.00 | 27.04 | 26.89
28.0 | 27.93 | 28.02 | 28.07 | 27.89
29.0 | 28.95 | 29.02 | 29.05 | 28.88
30.0 | 29.96 | 30.04 | 30.08 | 29.92
31.0 | 30.95 | 31.05 | 31.09 | 30.92
32.0 | 31.98 | 32.05 | 32.15 | 31.89
33.0 | 32.94 | 33.06 | 33.13 | 32.88
34.0 | 33.95 | 34.07 | 34.16 | 33.88
35.0 | 34.93 | 35.06 | 35.14 | 34.87
36.0 | 35.98 | 36.08 | 36.22 | 35.88
37.0 | 36.94 | 37.07 | 37.18 | 36.88
38.0 | 37.95 | 38.10 | 38.24 | 37.90
39.0 | 38.94 | 39.07 | 39.23 | 38.89
40.0 | 39.70 | 40.00 | 39.79 | 39.57
pos. | A2 up | A2 down | A2 in | A2 out
===================================================
0.0 | 2.91 | 0.05 | 0.39 | 0.00
1.0 | 3.79 | 0.69 | 1.47 | 0.00
2.0 | 5.01 | 1.75 | 2.39 | 0.25
3.0 | 6.09 | 2.76 | 3.37 | 1.20
4.0 | 7.21 | 3.78 | 4.31 | 2.13
5.0 | 8.30 | 4.84 | 5.25 | 3.08
6.0 | 9.44 | 5.89 | 6.18 | 3.98
7.0 | 10.52 | 6.92 | 7.10 | 4.94
8.0 | 11.69 | 7.97 | 8.06 | 5.84
9.0 | 12.77 | 8.99 | 9.01 | 6.77
10.0 | 13.90 | 10.00 | 9.94 | 7.67
11.0 | 15.01 | 11.09 | 10.89 | 8.63
12.0 | 16.14 | 12.16 | 11.85 | 9.57
13.0 | 17.23 | 13.18 | 12.79 | 10.50
14.0 | 18.39 | 14.20 | 13.72 | 11.45
15.0 | 19.48 | 15.25 | 14.70 | 12.37
16.0 | 20.61 | 16.31 | 15.62 | 13.31
17.0 | 21.74 | 17.36 | 16.60 | 14.23
18.0 | 22.87 | 18.38 | 17.55 | 15.21
19.0 | 23.98 | 19.42 | 18.51 | 16.13
20.0 | 25.11 | 20.44 | 19.46 | 17.07
21.0 | 26.20 | 21.50 | 20.44 | 18.04
22.0 | 27.37 | 22.52 | 21.36 | 18.95
23.0 | 28.48 | 23.58 | 22.34 | 19.90
24.0 | 29.61 | 24.62 | 23.29 | 20.85
25.0 | 30.72 | 25.65 | 24.25 | 21.79
26.0 | 31.86 | 26.68 | 25.22 | 22.73
27.0 | 32.97 | 27.72 | 26.18 | 23.66
28.0 | 34.10 | 28.78 | 27.11 | 24.56
29.0 | 35.19 | 29.83 | 28.08 | 25.49
30.0 | 36.34 | 30.82 | 29.04 | 26.41
31.0 | 37.43 | 31.88 | 30.01 | 27.35
32.0 | 38.55 | 32.94 | 30.94 | 28.29
33.0 | 39.67 | 33.98 | 31.88 | 29.22
34.0 | 40.00 | 35.01 | 32.84 | 30.15
35.0 | 40.00 | 36.07 | 33.79 | 31.05
36.0 | 40.00 | 37.11 | 34.75 | 32.00
37.0 | 40.00 | 38.14 | 35.69 | 32.93
38.0 | 40.00 | 39.23 | 36.66 | 33.89
39.0 | 40.00 | 39.68 | 37.00 | 34.83 A2UP IN...
40.0 | 40.00 | 39.68 | 37.00 | 35.76
41.0 | | | | 36.44
41.0 | | | | 36.52 DOES NOT FIND IN POSITION
pos. | P1 up | P1 down | P1 in | P1 out
===================================================
0.0 | 0.00 | 0.00 | 0.00 | 0.00
1.0 | 0.99 | 0.93 | 1.01 | 0.77
2.0 | 1.95 | 1.93 | 1.99 | 1.79
3.0 | 2.96 | 2.95 | 2.94 | 2.76
4.0 | 3.95 | 4.00 | 3.94 | 3.72
5.0 | 4.99 | 5.02 | 5.00 | 4.76
6.0 | 5.97 | 6.01 | 5.99 | 5.71
7.0 | 6.98 | 6.98 | 6.95 | 6.70
8.0 | 7.97 | 8.05 | 7.96 | 7.68
9.0 | 8.97 | 8.98 | 8.95 | 8.69
10.0 | 9.97 | 9.98 | 9.97 | 9.73
11.0 | 10.98 | 10.98 | 10.95 | 10.74
12.0 | 11.97 | 12.02 | 11.92 | 11.76
13.0 | 12.98 | 13.03 | 12.97 | 12.80
14.0 | 14.00 | 14.03 | 13.96 | 13.78
15.0 | 15.01 | 14.99 | 14.96 | 14.82
16.0 | 16.00 | 16.07 | 16.00 | 15.84
17.0 | 17.04 | 17.03 | 17.00 | 16.87
18.0 | 18.00 | 18.02 | 17.99 | 17.87
19.0 | 19.04 | 19.05 | 19.00 | 18.88
20.0 | 20.02 | 20.08 | 19.99 | 19.91
21.0 | 21.03 | 21.05 | 21.00 | 20.91
22.0 | 22.05 | 22.07 | 22.00 | 21.91
23.0 | 23.06 | 23.03 | 23.00 | 22.93
24.0 | 24.06 | 24.13 | 24.00 | 23.95
25.0 | 25.09 | 25.12 | 25.01 | 24.97
26.0 | 26.10 | 26.06 | 26.00 | 25.99
27.0 | 27.09 | 27.08 | 27.00 | 26.97
28.0 | 28.11 | 28.14 | 28.00 | 28.02
29.0 | 29.11 | 29.13 | 29.00 | 29.01
30.0 | 30.11 | 30.09 | 30.01 | 30.02
31.0 | 31.14 | 31.11 | 31.01 | 31.04
32.0 | 32.11 | 32.16 | 32.02 | 32.04
33.0 | 33.14 | 33.14 | 33.03 | 33.04
34.0 | 34.15 | 34.11 | 34.00 | 34.07
35.0 | 35.16 | 35.12 | 35.00 | 35.06
36.0 | 36.15 | 36.14 | 35.97 | 36.07
37.0 | 37.16 | 37.12 | 36.97 | 37.08
38.0 | 38.15 | 38.12 | 37.95 | 38.12
39.0 | 39.20 | 39.12 | 38.97 | 39.14
40.0 | 39.76 | 40.00 | 39.76 | 39.53
pos. | P2 up | P2 down | P2 in | P2 out
===================================================
0.0 | 0.00 | 0.00 | 0.00 | 0.00
1.0 | 0.99 | 0.98 | 1.05 | 1.08
2.0 | 2.01 | 2.02 | 2.04 | 2.07
3.0 | 2.98 | 2.99 | 3.03 | 3.06
4.0 | 4.00 | 4.02 | 4.06 | 4.05
5.0 | 4.99 | 4.96 | 5.01 | 5.06
6.0 | 5.95 | 5.96 | 6.05 | 6.07
7.0 | 6.97 | 6.91 | 7.00 | 7.02
8.0 | 7.95 | 7.94 | 8.02 | 8.05
9.0 | 8.94 | 8.90 | 9.02 | 9.02
10.0 | 9.96 | 9.95 | 9.99 | 10.05
11.0 | 10.96 | 10.95 | 11.00 | 11.01
12.0 | 11.97 | 11.94 | 12.01 | 12.02
13.0 | 12.94 | 12.90 | 13.01 | 13.00
14.0 | 13.99 | 13.97 | 14.03 | 14.02
15.0 | 14.99 | 14.95 | 15.00 | 15.00
16.0 | 15.96 | 15.97 | 16.05 | 16.01
17.0 | 16.96 | 16.95 | 17.04 | 17.00
18.0 | 17.98 | 17.99 | 18.01 | 18.04
19.0 | 18.99 | 19.00 | 19.05 | 19.03
20.0 | 20.01 | 20.00 | 20.03 | 20.02
21.0 | 21.00 | 21.01 | 21.04 | 21.01
22.0 | 22.00 | 22.04 | 22.04 | 22.03
23.0 | 23.02 | 23.03 | 23.02 | 23.03
24.0 | 24.03 | 24.07 | 24.02 | 24.00
25.0 | 25.02 | 25.01 | 25.05 | 24.99
26.0 | 26.03 | 26.11 | 26.03 | 26.06
27.0 | 27.03 | 27.06 | 27.07 | 27.02
28.0 | 28.04 | 28.09 | 28.03 | 28.01
29.0 | 29.10 | 29.10 | 29.02 | 28.98
30.0 | 30.10 | 30.13 | 30.05 | 30.02
31.0 | 31.06 | 31.15 | 31.03 | 31.02
32.0 | 32.06 | 32.17 | 32.07 | 32.00
33.0 | 33.11 | 33.12 | 33.08 | 33.00
34.0 | 34.07 | 34.18 | 34.06 | 34.03
35.0 | 35.08 | 35.15 | 35.02 | 35.02
36.0 | 36.08 | 36.17 | 36.05 | 36.02
37.0 | 37.13 | 37.19 | 37.04 | 37.02
38.0 | 38.12 | 38.19 | 38.08 | 38.04
39.0 | 39.10 | 38.19 | 39.03 | 39.03
40.0 | 39.25 | 38.19 | 39.54 | 39.61
pos. | D1 | D2
=============================
0.0 | 0.09 | 0.00
1.0 | 1.06 | 0.00
2.0 | 2.12 | 0.00
3.0 | 3.12 | 0.85
4.0 | 4.08 | 1.94
5.0 | 5.09 | 3.13
6.0 | 6.05 | 4.22
7.0 | 7.06 | 5.37
8.0 | 8.02 | 6.48
9.0 | 9.02 | 7.65
10.0 | 10.01 | 8.77
11.0 | 11.03 | 9.94
12.0 | 12.02 | 11.02
13.0 | 13.00 | 12.20
14.0 | 13.99 | 13.31
15.0 | 14.99 | 14.44
16.0 | 15.98 | 15.61
17.0 | 16.99 | 16.77
18.0 | 17.97 | 17.91
19.0 | 18.98 | 19.07
20.0 | 19.95 | 20.17
21.0 | 20.94 | 21.33
22.0 | 21.94 | 22.46
23.0 | 22.97 | 23.61
24.0 | 23.92 | 24.73
25.0 | 24.95 | 25.93
26.0 | 25.92 | 27.00
27.0 | 26.92 | 28.17
28.0 | 27.90 | 29.33
29.0 | 28.97 | 30.47
30.0 | 29.89 | 31.59
31.0 | 30.91 | 32.76
32.0 | 31.89 | 33.87
33.0 | 32.89 | 34.99
34.0 | 33.85 | 36.15
35.0 | 34.91 | 37.32
36.0 | 35.86 | 38.43
37.0 | 36.88 | 38.65
38.0 | 37.88 | 38.65
39.0 | 38.90 | 38.65
40.0 | 39.46 | 38.65
______________________________________________________________________
Boaz Klima
29 January, 2003
Figure style
Dear convenors,
A few of you have been bugging me for some time about standardizing the look
of plots coming out of D0. It's an interesting idea and needs some
discussion. The pros are obvious, but I know some people do not like this.
So, we should probably discuss this in one of our upcoming convenors
meetings. In the meantime, Avto circulated the enclosed message to the Higgs
group. Please feel free to use these in your group too. And, please do not
ask me right away about colors; that will hopefully come next.
Enjoy!
Boaz
From: "Avto Kharchilava"
As promised at last Higgs working group meeting, under
http://www-clued0.fnal.gov/~avto/higgs/template.html
you will find a few ROOT commands that may improve the style
of your "Moriond plots", in particular. Suggestions are welcome.
______________________________________________________________________
Victor Bodyagin
01 February, 2003
more updates on FPF status
today Wanda completed calibrating measurements for LVDT readouts.
She tested 17 out of 18 pots. A1O was disabled since it has motion
problems. We'll have new calibraring constants on Monday.
George Ginther attached the TPPs to the cassetes and installed 3 AFE:
AFE in slot 0 for A1/P1 vertical
AFE in slot 1 for A2/P2 vertical
AFE in slot 6 for D1/D2
Our VRB, Sequencer and AFEs were succesfully downloaded.
In cooperation with Jadzia we are going to take two
calibrating runs:
1. With A/S OFF
2. With A/S ON
Since Monday FPD can be in global data stream.
Sergio F. Novaes Tuesday, 04 February, 2003 Forward Proton ID Certification document Hello FPDers, It is a pleasure for us to announce that our Forward Proton ID Certification document for the elastic process is (finally) ready and approved by our godparent. It was posted as a D0 Note (# 4054), and all files of the document could be accessed at http://www-d0.fnal.gov/fpd/PidI/. We would like to thank Jorge Barreto for all his help in the preparation of the manuscript. Regards, Gilvan, Moacyr & Sergio ______________________________________________________________________ Mike Martens Wednesday, 05 February, 2003 Beam emittances I have attached a Power Point file (and a Postscript version) with some slides and comments about the present state of beam position and emittance measurements in the Tevatron. Unfortunately, even this late in Run II, we do not have good measurements for these. Work is in progress and I hope to have some better results on the beam position after the Jan 2003 shutdown. Since they are so large, I give the web page address instead http://waldo.fnal.gov/~martens/public/FPD_beamsize_Jan03.ppt and http://waldo.fnal.gov/~martens/public/FPD_beamsize_Jan03.ps ______________________________________________________________________ Victor Bodyagin Friday, 07 February, 2003 access updates Today Carley, Wanda and me were fighting with the problem of LVDT readout fluctuations in A2 castle. Many of us remember about the mystery of A2I fluctuations. We tried to solve it few times and were not successful. While this shutdown we had enough time to try again. Again we were observing big fluctuations for A2I and A2O and very significant for A2U and A2D. By swapping the LVDT-to-Conditioner cables on LVDTs we figured out that the problem is related with conditioners. Measurements of voltages at the outputs of LPCs, comparisons with good castles and many attempts to find something interesting with the help of scope gave us practically nothing. Fast ACNET plot usually used by us to watch A-halo P-halo turned out to be the most powerful tool in our studies. Of course, we used it to watch LVDT readouts. 1. It turned out that A2 problem is a part of more general one. All LVDT readouts for good castles also fluctuate when pots are at home positions. One can see it for A1, P1 and P2 as well, though the fluctuations will be much smaller ~1mm. For A2 they could be up to ~10mm when all A2 are at home. A2 is still not calibrated but improvement of LVDT readouts by ~20% corrections will not change this picture dramatically. 2. All fluctuations in good castles and in A2 are extremely strongly time correlated! It is clearly seen at time plots. For us it turned out to be the most striking feature. 3. But probably the most amazing thing we observed today is that these fluctuations are position correlated also, for A2 at least. For instance, when all four pots are home one can see from time to time (quasiperiodical) fluctuations for all pots. After moving A2U, A2D and A2I to 5-7mm no fluctuations are observed for these 3 pots meanwhile A2O has fluctuations. Moreover, the closer A2O to them the bigger fluctuations can be observed. You can move A2U, A2D, A2I to 15 or to 20 mm and watch perfect straight lines as long as you want but once A2O is moved closely to the same positions the flucts appear again. It is really a resonant effect. Certainly A2O is a primary suspect. Ricardo and me this night swapped A2I and A2O LVDT-to-LPC cables and it was clearly seen that it was not A2O LVDT which was responsible for such for such a behavior of A2O readout. The problem is that this A2O LPC is so-called "master" while the others are "slaves". Earlier Carley and me replaced A2O LPC by a spare "master" but nothing has changed. Seemingly A2I fluctuations mystery does not exist anymore. We can leave A2O at home and have very good readouts for the others. So far we can live with that. Today I could not get into LAB6 and check do we have more spares or not since Wanda (a tech in charge for our room) has changed the lock on the door or its code. We'll have access till 4p.m. Friday Feb 7th. Ricardo and me left all tools in the tunnel we brought together with Carley. A guy from MCR whom I do not know (sorry for that) told me that Mike Martens told him to prepare sandbags. According to his estimates it's a lot (some two trucks). We need somebody who could clearly tell him where to put them. ______________________________________________________________________ Victor Bodyagin Friday, 07 February, 2003 some access news yesterday I was wrong with the statement that A2O conditioner was bad. Finally it turned out to be A2O LVDT. We moved A2I LVDT into A2O pot and A2O LVDT to A2I pot. Since A2O has a pseudodetector it is preferrable to move it and to work with it while A2I is now empty. Our suggestion is to keep A2I at home and to work with A2U, A2D and A2O. Right now Wanda is doing calibration measurements. It is necessary to do since there was a deal of activity in A2 castle with swapping LVDTs setting LPC spans etc. The status of the pots is as follows: 16 good pots out of 18. A2I has a problematical LVDT in it. I could not find a spare one at Lab6. We need to have spares. A1O has problems while moving home. This problem will be investigated next time. Very likely Newton is right and it can be IIB problem. Readout status: did not change since my last report since CFT guys were too busy with their own problems. They tried to take our AFEs in calibrating run but DAQ failed for its own reasons this morning. Obviously, after this shutdown everyone who was busy with it feels tired. Let's have a quiet weekend. I'll remain an on-call FPD expert this weekend. ______________________________________________________________________ Jorge Luis Barreto Wednesday, 12 February, 2003 QCD talk The slides for my tomorrow's talk in the QCD meeting can be found at http://www-clued0.fnal.gov/~barreto/fpd/QCD_021303.ppt Please, let me know about any suggestion/comments. ______________________________________________________________________ Sergio F. Novaes Friday, 21 February, 2003 Workshop Agenda - Permanent URL The workshop agenda has been transferred to its permanent location: http://www-d0.fnal.gov/fpd/Links/Workshops/FPDWorkshop0302.html with a link in the FPD homepage / Documents.
Dmitri Denisov
5 February 2003
Status of the Summer 2003 shutdown
Dear Colleagues!
Here is brief summary from today's Run II Strategy Meeting between
BD/D0/CDF:
1. Shutdown of ~6 weeks is needed by BD for maintenance as well as
recycler related jobs. Both experiments expressed preference of running
without shutdown.
2. With ~2-3 weeks postshutdown startup and outlined above shutdown
duration all FY03 integrated luminosity will be collected before
shutdown.
Extrapolating recent Tevatron performance to reach goal of 225pb-1 of
delivered luminosity in FY03 brings us to about mid. August 2003.
3. Based on the above summer shutdown start date will most probably be
delayed by ~3-4 weeks past originally scheduled begining date of July 28
2003. We expect to hear final decision on start date and duration of the
shutdown from the Lab within a few weeks.
______________________________________________________________________
Mike Martens
5 February 2003
Beam emittances
I have attached a Power Point file (and a Postscript version) with some
slides and comments about the present state of beam position and
emittance measurements in the Tevatron. Unfortunately, even this late in
Run II, we do not have good measurements for these. Work is in progress
and I hope to have some better results on the beam position after the
Jan 2003 shutdown.
Since they are so large, I give the web page address instead
http://waldo.fnal.gov/~martens/public/FPD_beamsize_Jan03.ppt
and
http://waldo.fnal.gov/~martens/public/FPD_beamsize_Jan03.ps
______________________________________________________________________
Victor Bodyagin
7 February 2003
access updates
sorry to be that late with updates but I was really busy today.
Today Carley, Wanda and me were fighting with the problem
of LVDT readout fluctuations in A2 castle.
Many of us remember about the mystery of A2I fluctuations.
We tried to solve it few times and were not successful.
While this shutdown we had enough time to try again.
Again we were observing big fluctuations for A2I and A2O and
very significant for A2U and A2D. By swapping the LVDT-to-Conditioner
cables on LVDTs we figured out that the problem is related with
conditioners. Measurements of voltages at the outputs of LPCs,
comparisons with good castles and many attempts to find something
interesting with the help of scope gave us practically nothing.
Fast ACNET plot usually used by us to watch A-halo P-halo turned out
to
be the most powerful tool in our studies. Of course, we used it
to watch LVDT readouts.
1. It turned out that A2 problem is a part of more general one.
All LVDT readouts for good castles also fluctuate when pots
are at home positions. One can see it for A1, P1 and P2 as well,
though the fluctuations will be much smaller ~1mm. For A2
they could be up to ~10mm when all A2 are at home.
A2 is still not calibrated but improvement of LVDT readouts
by ~20% corrections will not change this picture dramatically.
2. All fluctuations in good castles and in A2 are extremely
strongly time correlated! It is clearly seen at time plots.
For us it turned out to be the most striking feature.
3. But probably the most amazing thing we observed today is that
these fluctuations are position correlated also, for A2 at least.
For instance, when all four pots are home one can see from
time to time (quasiperiodical) fluctuations for all pots.
After moving A2U, A2D and A2I to 5-7mm no fluctuations
are observed for these 3 pots meanwhile A2O has fluctuations.
Moreover, the closer A2O to them the bigger fluctuations
can be observed. You can move A2U, A2D, A2I to 15 or to 20 mm
and watch perfect straight lines as long as you want but
once A2O is moved closely to the same positions the flucts
appear again. It is really a resonant effect.
Certainly A2O is a primary suspect. Ricardo and me this night
swapped A2I and A2O LVDT-to-LPC cables and it was clearly seen
that it was not A2O LVDT which was responsible for such
for such a behavior of A2O readout.
The problem is that this A2O LPC is so-called "master" while the
others are "slaves". Earlier Carley and me replaced A2O LPC
by a spare "master" but nothing has changed.
Seemingly A2I fluctuations mystery does not exist anymore.
We can leave A2O at home and have very good readouts for the
others. So far we can live with that.
Today I could not get into LAB6 and check do we have more spares
or not since Wanda (a tech in charge for our room) has changed the
lock on the door or its code.
We'll have access till 4p.m. Friday Feb 7th.
Ricardo and me left all tools in the tunnel we brought together
with Carley.
A guy from MCR whom I do not know (sorry for that) told me that
Mike Martens told him to prepare sandbags. According to his
estimates it's a lot (some two trucks). We need somebody who
could clearly tell him where to put them.
Bye. I'll try to be at work no later than 9:30.
______________________________________________________________________
Victor Bodyagin
7 February 2003
some access news
yesterday I was wrong with the statement that A2O conditioner was bad.
Finally it turned out to be A2O LVDT. We moved A2I LVDT into A2O pot
and A2O LVDT to A2I pot. Since A2O has a pseudodetector it is
preferrable to move it and to work with it while A2I is now empty.
Our suggestion is to keep A2I at home and to work with A2U, A2D and
A2O.
Right now Wanda is doing calibration measurements. It is necessary
to do since there was a deal of activity in A2 castle with swapping
LVDTs setting LPC spans etc.
The status of the pots is as follows:
16 good pots out of 18. A2I has a problematical LVDT in it. I could
not find a spare one at Lab6. We need to have spares. A1O has
problems while moving home. This problem will be investigated next
time. Very likely Newton is right and it can be IIB problems
Readout status:
did not change since my last report since CFT guys were too busy
with their own problems. They tried to take our AFEs in calibrating
run but DAQ failed for its own reasons this morning.
Obviously, after this shutdown everyone who was busy with it
feels tired. Let's have a quiet weekend.
I'll remain an on-call FPD expert this weekend.
Let's meet on Monday 11th at 14:00 in SdH for FPD operations.
______________________________________________________________________
Jorge Luis Barreto
12 February 2003
QCD talk
Hello,
The slides for my tomorrow's talk in the QCD meeting
can be found at
http://www-clued0.fnal.gov/~barreto/fpd/QCD_021303.ppt
Please, let me know about any suggestion/comments.
______________________________________________________________________
Sergio F. Novaes
21 February 2003
Workshop Agenda - Permanent URL
The workshop agenda has been transferred to its permanent location:
http://www-d0.fnal.gov/fpd/Links/Workshops/FPDWorkshop0302.html
with a link in the FPD homepage / Documents.
During the workshop, please keep using the old address:
http://d0server1.fnal.gov/users/novaes/FPDWorkshop.html
This one is easier to update.
______________________________________________________________________
Wanda Prado da Silva
9 March 2003
Pot calibration
Dear all.
Let me report the procedure and observations did during the pot
calibration
work.
First of all, Vladimir and Christophe give me information that LVDT
reading
is related to a value named RAVL by a linear equation like
LVDT=RVAL*ASLO + ROFF
For procedure calibration, We record LVDT reading for all pots, from
home
position to maximum position, each 1.0mm. Then using current value for
ASLO and ROFF and LVDT reading recorded for each position, we determine
the
RVAL value for each pot position. Finally, we plotted the wanted
position X RVAL in order to determine the new value for ASLO and ROFF
parameters, where wanted position is the position were asked pot to go.
The plots with this results are:
\\D0server4\users\prado\Pot_Calibration\A1U-A1D_1.ps
\\D0server4\users\prado\pot_calibration\A1I_1.ps
\\D0server4\users\prado\Pot_Calibration\A2U-A2D_1.ps
\\D0server4\users\prado\Pot_Calibration\A2I_1.ps
\\D0server4\users\prado\Pot_Calibration\A2O_1.ps
\\D0server4\users\prado\Pot_Calibration\P1U-P1D_1.ps
\\D0server4\users\prado\Pot_Calibration\P1I-A1O_1.ps
\\D0server4\users\prado\Pot_Calibration\P2U-P2D1.ps
\\D0server4\users\prado\Pot_Calibration\P2I-P2O1.ps
\\D0server4\users\prado\Pot_Calibration\D1-D2_1.ps
After introduce new value for ASLO and ROFF, I did measurement for pot
position from home until maximum position. These data are found on
\\D0server4\users\prado\pot_calibration\P1_pos.xls
\\D0server4\users\prado\pot_calibration\P2_pos.xls
\\D0server4\users\prado\pot_calibration\A1_pos.xls
Pots from A2 castle are miscalibrated and show big fluctuations, D2 is
also
miscalibrated and show little fluctuation.
I have been discussing with Vladimir and we are investigating the cause
of this fluctuantions and miscalibration, doing the following procedure:
- runnig a archiver process, in order to record the position for all
pots;
- moving pots in different positions searching some kind of
correlation between position X fluctuation;
- moving pots and record the RVAL for different pot position.
A plot from data record by archiver can be found at
\\D0server4\users\prado\Pot_Calibration\D1_D2_HPos1.gif
when dipoles were at home position, and
\\D0server4\users\prado\Pot_Calibration\D1_D2_Mov1.gif
when dipoles were moved
The summary for the study of A2 castle, movement is:
Pot Position | behaviour
________________________________________
A2U/A2D/A2I/A2O
at home | big fluctuation
________________________________________
A2I at 10.0mm | stable
and
A2U/A2D/A2O | big fluctuation
at home
________________________________________
A2U/A2D/A2O | stable
at 10.0mm
and
A2I at home | big fluctuat
________________________________________
A2U/A2D/A2I/A2O
at any position | big fluctuation
different from
home position
________________________________________
A2I/A2O | stable
at 10.0mm
and
A2U/A2D | big fluctuation
at home
________________________________________
A2I/A2O/A2D | stable
at 10.0mm
and
A2U at home | alternating between big
| and little fluctuation
________________________________________
So I didn't understood this behaviour.
The RVAl value for different dipole positions, has being recorded and
is being analysed. Also for A2 castle, I intend to
do many tests, arranging these pots in pars and recording the RVAL
value.
I hope receive comments that help me in this task.
______________________________________________________________________
Wanda Prado da Silva
10 March 2003
pot calibration
I don't have specific information how this variable is
processed internally. I have only the information that links this
variable to LVDT reading by a linear relation.
Me Carley and Ricardo, just find documentation about this issue. I am
convinced that there are some kind of mistake on this calibration
procedure, some mistake about linear region.
About the calculation, I used the linear equation:
LVDT=RVAL*ASLO + ROFF
Since I had ASLO and ROFF, I determined RVAL:
RVAL= (LVDT - ROFF)/ASLO
and I proced as explained in the previous message.
Regard to A2I pot, the previous test made by Victor, me and Carley,
adressed all fluctuations problems to this pot, but note that now
I did tests that show A2I stable when this pot, A2O and A2D, is at
10.0mm while A2U left at home, shows big fluctuations. For other hand,
the fluctuations can't be linked only to home position, since if
we put all four pots, together, they fluctuate, doesn't matter the
position, in wich they are. Those observation changed our understanding
about this fluctuations.
The correct address and the name of plots are:
//d0server1/users/prado/Pot_Calibration/A1U-A1D_1.ps
//d0server1/users/prado/Pot_Calibration/A1I_1.ps
//d0server1/users/prado/Pot_Calibration/A2U-A2D_1.ps
//d0server1/users/prado/Pot_Calibration/A2I_1.ps
//d0server1/users/prado/Pot_Calibration/A2O_1.ps
//d0server1/users/prado/Pot_Calibration/P1U-P1D_1.ps
//d0server1/users/prado/Pot_Calibration/P1I-A1O_1.ps
//d0server1/users/prado/Pot_Calibration/P2U-P2D1.ps
//d0server1/users/prado/Pot_Calibration/P2I-P2O1.ps
//d0server1/users/prado/Pot_Calibration/D1-D2_1.ps
//d0server1/users/prado/Pot_Calibration/P1_pos.xls
//d0server1/users/prado/Pot_Calibration/P2_pos.xls
//d0server1/users/prado/Pot_Calibration/A1_pos.xls
//d0server1/users/prado/Pot_Calibration/D1_D2_HPos1.gif
//d0server1/users/prado/Pot_Calibration/D1_D2_Mov1.gif
______________________________________________________________________
Wanda Prado da Silva
15 March 2003
Pots calibration
I compute new parameters for all pots, after we discussed the procedure
about that and looking the epics documentation. I also examined the
epics.db and I checked AOFF, ESLO value on this file. Occour that this
procedure didn't results in good calibration, but the fit on plot
wanted position X RAW, looks good. All pots at home position show
values for LVDT different from zero, some of them positive and some
negative.
So sounds like a problem in ROFF value.I examine the epics reference,
but I didn't find anything that help me to adjust this values.
The plots Wanted position X RAW, for all pots are on:
//d0server1/users/prado/Pot_Calibration/A1U-A1D.ps
//d0server1/users/prado/Pot_Calibration/A1I.ps
//d0server1/users/prado/Pot_Calibration/A2U-A2D.ps
//d0server1/users/prado/Pot_Calibration/A2I.ps
//d0server1/users/prado/Pot_Calibration/A2O.ps
//d0server1/users/prado/Pot_Calibration/P1U-P1D.ps
//d0server1/users/prado/Pot_Calibration/P1I-A1O.ps
//d0server1/users/prado/Pot_Calibration/P2U-P2D1.ps
//d0server1/users/prado/Pot_Calibration/P2I-P2O1.ps
//d0server1/users/prado/Pot_Calibration/D1-D2.ps
and the table with the parameters before calibration and after
calibration, is on
//d0server1/users/prado/Pot_Calibration/Parameters.ps
______________________________________________________________________
Victor Bodyagin
28 March 2003
fpd MAP
I've attached a full-scale-FPD-from-fiber-to-SVX channel map
bellow. Please, note that:
1. Practically everyone of us contributed into this project at
different
stages of FPD development and I just tried to assemble our mapping
folklore onto one list.
2. The map has not been tested and verified yet with fpd_examine since
examine development is still underway. So I can not claim that it is
correct.
3. This is a full-scale project map, i.e. for all 18 pots and 5 AFEs.
Our current hardware configuration is:
1. We have 3 AFEs for vertical quads and dipoles.
2. Cables from vertical detectors A1,P1 are plugged into A/S
inputs for horizontal A1,P1.
3. Vertical A2,P2 and Dipoles are attached normally.
Please, take a look at it and any comment or correction
is welcome.
______________________________________________________________________
Michael Strang
3 April 2003
DPF Diffraction talk
The location of the updated diffractive talk is:
http://www-clued0.fnal.gov/~strang/web/DPF2003.ppt
Please look it over and send any comments this afternoon. Thanks.
______________________________________________________________________
Vladimir Sirotenko
7 April 2003
acnet separator values
When we access seperator's values from acnet, we got errors all the time.
From BD Vax consol we also can not access them (from page D80, tehre is
an error: this is not valid device name). For example, varaibles
C:C4HSPF, C:D1HSMF and so on. Script is written to put acnet variables to
RUNS database, but those variables are zeros all the time .. your
suggestions?
Complete list which was agreed to keep for every run is the following:
'C:C4HSPF':{'DESC':'C49 horizontal separator settings','UNIT':'VOLT'},
'C:C4HSMF':{'DESC':'C49 horizontal separator settings','UNIT':'VOLT'},
'C:C4VSPF':{'DESC':'C49 vertical separator settings','UNIT':'VOLT'},
'C:C4VSMF':{'DESC':'C49 vertical separator settings','UNIT':'VOLT'},
'C:D1HSPF':{'DESC':'D11 horizontal separator settings','UNIT':'VOLT'},
'C:D1HSMF':{'DESC':'D11 horizontal separator settings','UNIT':'VOLT'},
'C:D1VSPF':{'DESC':'D11 vertical separator settings','UNIT':'VOLT'},
'C:D1VSMF':{'DESC':'D11 vertical separator settings','UNIT':'VOLT'},
'C:A4HSPF':{'DESC':'A49 horizontal separator settings','UNIT':'VOLT'},
'C:A4HSMF':{'DESC':'A49 horizontal separator settings','UNIT':'VOLT'},
'C:A4VSPF':{'DESC':'A49 vertical separator settings','UNIT':'VOLT'},
'C:A4VSMF':{'DESC':'A49 vertical separator settings','UNIT':'VOLT'},
'C:B0HSPF':{'DESC':'B11 horizontal separator settings','UNIT':'VOLT'},
'C:B0HSMF':{'DESC':'B11 horizontal separator settings','UNIT':'VOLT'},
'C:B0VSPF':{'DESC':'B11 vertical separator settings','UNIT':'VOLT'},
'C:B0VSMF':{'DESC':'B11 vertical separator settings','UNIT':'VOLT'},
'C:A1VSPF':{'DESC':'A17 vertical separator settings','UNIT':'VOLT'},
'C:A1VSMF':{'DESC':'A17 vertical separator settings','UNIT':'VOLT'},
'C:B1HSPF':{'DESC':'B17 horizontal separator settings','UNIT':'VOLT'},
'C:B1HSMF':{'DESC':'B17 horizontal separator settings','UNIT':'VOLT'},
'C:C1VSPF':{'DESC':'C17 vertical separator settings','UNIT':'VOLT'},
'C:C1VSMF':{'DESC':'C17 vertical separator settings','UNIT':'VOLT'},
'C:D4HSPF':{'DESC':'D48 horizontal separator settings','UNIT':'VOLT'},
'C:D4HSMF':{'DESC':'D48 horizontal separator settings','UNIT':'VOLT'},
______________________________________________________________________
Victor Bodyagin
18 April 2003
rates OK
when I came in the morning to look into the problem of the update of
the
scalars at first I found nothing wrong. SDAQ was running and scalars
were being updated properly. The only one thing I found to be wrong is
that "GRAND OR" NIM Logical Unit (LU) has gone crazy. It was generating
output logical "1" ignoring any input combinations and "AND" terms.
It was working like a free generator. So Carley and me replaced it.
Now things got back under our control.
So far I have no any satisfactory explanation why the problem
of the ACNET update appeared and was it in fact a problem of ACNET.
Probably this problem appeared in the "transition" period for
the LU from a reasonable to a mad state.
Now, let me remind you a few things about update.
Counting rates are measured by normalizing them by a standard
frequency (1MHz) coming from the generator. For that purpose these
standard frequency NIM pulses are coming at the input No.11 of the
first CAMAC scalar. The sum of this scalar values over some period
of time (mostly it is 5 seconds) is used for normalization.
SDAQ does it in the following steps:
1. Gets the trigger.
2. Reads out the event with the current values of the scalars in it.
3. Sums up scalars' values with the values from the previous events.
4. Checks time and statistics.
5. If 5 seconds passed since last update and if total statistics for
the scalar is greater than 100 SDAQ normalizes this value and
updates the counting rate. Big enough statistics is necessary hear
in order to have some reasonable accuracy of the counting rate
estimation.
6. SDAQ updates are coming:
a. To vxWorks window.
b. To EPICS variables.
One can see these updates:
1. As ACNET variables provided nothing is wrong neither with EPICS db
nor with ACNET.
2. In FPD Gui provided nothing is wrong with SDAQ and EPICS.
3. In vxWorks window provided nothing is wrong with SDAQ.
What can be wrong with SDAQ ?
For SDAQ update two things a crucial:
1. Triggering. If it is absent then SDAQ can not readout an event.
2. 1MHz pulses at the input #11 of the first scalar. If they are
absent
then SDAQ can not divide by ZERO.
Since main Logical Unit got crazy there are many possible guesses
what and why was wrong.
There are no rules for love and madness!
______________________________________________________________________
Michael Strang
24 April 2003
Access results
The first order of business was to put the A2 castle into normal
operating condition, which was accomplished. The pots where then moved
and the LVDT values were observed to change. Further studies showed that
the LVDTs were stable, even with all pots at nominal positions over a
long period of time. The other pots were exercised as well. With these
results, it was decided to not replace the LVDT at this time.
Most of our efforts were spent on the noise problem which took longer
than expected due to the unusual results. We tested the P1I cables that
are carrying the P1U signal looking for common ground between the
channels. The dipoles show common ground on all channels and work fine.
In the cables we tested, we found that for P1I-1, some of the channels
had common ground and others did not. Those that did not were
interspersed with those that did. Inspecting the cable, we found no
problems. P1I-2 showed that half of the cable had common ground and the
other half did not. P1I-3 showed that no channels had common ground. We
inspected P1I-3 both in the tunnel and at PW08 and everything looked
fine. P1I-3 looked to be plugged into the TPP correctly during the test.
We then used the master map to convert from cable channel to SVX channel
and ultimately to calibration histogram channel (after some confusion)
and compared our results to the latest calibration for P1I taken last
night. If the antenna hypothesis were true (channel without a common
ground indicate that the signal channel is picking up noise and causing
spikes) it should be clear. Instead, what we found was that the channels
with common ground are evenly distributed between noisy and quiet
channels as are the channels with no common ground. We unplugged P1I-3
from the TPP and Jadzia will be performing a full CFT calibration run
tonight and we will be able to see if this has any effect on the noise
levels for those 16 channels compared to last nights calibration where
the cable was plugged in.
We will discuss these results with John Anderson tomorrow morning to try
to figure out where to go from here on the noise issue.
In parallel with these tasks, Mike Utes installed the new sequencer
software and Victor is downloading updated time delays for the dipoles.
______________________________________________________________________
Mike Martens
25 April 2003 12:03
Orbit smoothing
The Tevatron orbits were adjusted this week so some amount of extra care
should be given when moving the pots in for next store.
Horizontally I expect orbit differences of less than 0.5 mm except at
the location of the dipole pots. At the dipole pots the horizontal orbit
position is now +2 mm different than it was before the smoothing. (It is
now 2 mm further to the radial outside.) However, there is some
confusion because smoothed and tried to keep that position constant. It
appeared to be constant, but now it shows a 2 mm orbit difference.
Vertically I expect that the beam will be +2mm higher at the proton
pots, -1mm lower at the pbar pots, and +1mm higher at the dipole pots.
Also, we are now saving the orbits periodically during a store in the
SDA (Sequenced Data Acquisition) database. The orbits are collected
about every 30 minutes. These are the orbits during a store with
coalesced beam, so there will be a difference between these measurements
and the orbit measurements made during the smoothing. They should give
an indication of the stability of the beam however.
To view the orbits,
Start up T39 on an ACNET console.
Select the "sda" menu item.
Select "Collider Shot" for usage.
Select "HEP" for case.
Enter the store number for the file #.
Then you should be able to plot the orbit positions.
______________________________________________________________________
Mario Vaz
April 28, 2003
Wagner and I are working on a new set of L1 trigger equations. The DI
implementation made with Ramirez at D0 was replicated here. Do you guys
downloaded and tested it in the FPD DFE at the Test Stand ? is any FPD
DFE
operating at the PW08 rack ?
About the FPD noise problem, I wrote a short note at
http://d0br1.lafex.cbpf.br/~mario/FPD/TPP_Ground_Loops.htm
______________________________________________________________________
Carley Martins
30 April 2003
TPP: news results
The last results of run calibration for 0x50 and 0x52 done by CFT,
can be found at:
\\D0server4\users\cmartins\TPP_PLOTS\AFE_CAL_histo1_04-29-03.jpg
\\D0server4\users\cmartins\TPP_PLOTS\AFE_CAL_histo2_04-29-03.jpg
This plots are related to 4quarter of TPP (PW08 border) with all
cables unplugged.
The previous results, with (n-1)cables plugged, can be found at:
\\D0server4\users\cmartins\TPP_PLOTS\AFE_CAL_histo1_04-25-03.jpg
\\D0server4\users\cmartins\TPP_PLOTS\AFE_CAL_histo2_04-25-03.jpg
\\D0server4\users\cmartins\TPP_PLOTS\AFE_CAL_histo3_04-25-03.jpg
Please, take a look at this plots and comments are wellcome!
______________________________________________________________________
Michael Strang
6 May 2003
FPD Issues
Ok, I've returned the FPDIssues link to the top of the online version of
the checklist. The url is:
d0server1.fnal.gov/users/strang/web/fpd/documents/FPDIssues.txt
Please look it over and let me know if there is anything I should change
or add.
Vladimir Sirotenko 21 May, 2003 status of FPD databases Current status of FPD databases project can be found in the following location: http://d0server1/users/sirotenko/presentations/FPD/FPDDatabases1.ppt ________________________________________________________________________ Helio da Motta Filho 05 June, 2003 noise There has just been a meeting where we discussed the issue of the TPP noise. The presents were myself, Carley, Wanda, Carlos and Ricardo. Ricardo presented some plots where we could see the noise. The main points of the meetings were: 1) it does not look as bad as once we thought. The number of counts may be small compared to the counts we will have from a MAPMT signal. If this is the case we can easily live with the noise just setting a threshold above the noise counts. This would not prevent us to deal with possible channel optical crosstalk since we would still be able to distinguish a direct signal from a Xtalk signal. 2) the noise seems to be picked up by the cables in their journey from the castles to the TPP in the collision hall. A test was made when the cable was wrapped around a ferrite coil (a device used for the purpose of reducing this kind of noise). The results was a very sharp reduction on the noise! 2) we would like to have histograms of the noise for each channel (or at least some of them) to see how it is distributed. The plots shown are acumulated from about 10000 readouts. It is useful to know what is the typical count. Our guess is that the MAPMT signal will give a much higher count. 3) Ricardo is getting the specifications of the coil so we can see the cost of having them in case we really need it. I will check at LNLS about this, since they probably need similar coils in their system and could tell us about possible supliers and models. 4) another option would be to redo the TPP boards. That's something we would not like to do. we will think on trhat only the the coil solution does not work and IF the signal does not prove to be strong enough to overcome the noise. This test will soon be done. 5) shielding all the cable seems unpractical and, probably, expensive; therefore, we are no considering it now. ________________________________________________________________________ Helio da Motta Filho 06 June, 2003 news on LVDT fluctuation I have been concerned with the lVDT fluctuations. Today I met Victor and we discussed the issue for quite sometime. After gathering some gipothesis we went to talk to Shua Mua who knows technical details of the RM, 1553 and system. We talk with him for a long time explaining the problem and some of our hypothesis. Basically he discarded any possible problem with strobing, reading rates. However, in the course of the conversation something came that surprized me and Victor. We came to find out that the cable connecting the 1553 to the RM has an extra layer that connects the two grounds. We, maybe naively, thought that there would be only a signal connection through the cable, but indeed there is one more connection that is puting the RM ground (at the TEVATRON) with the 1515 ground (up here at D0). Shua said that this COULD be a source of interferences and, consequently of the fluctuations we observe and that such connection must be cut at the RM side. So, this is new (at least it is from us) and, indeed, can be a source of the problems with the LVDT readout. We should then cut this connection in an acess to the tunnel and see what happens. It is something new on the LVDT problem. Please, lets hear from the group. What do people have to say about that and if we have the OK to go on with this try. ________________________________________________________________________ Ricardo Ramirez 18 June, 2003 CH Access report This is the Collision Hall Access report. Achieved Tasks: 1. Verification: Spare cables were attached to Dipole board (for both detectors). 2. One spare cable has been connected to one quarter TPP it is going to be read as a 1q4 (MCM6 and MCM7). However, I checked the RC connection, and the cable was not properly plugged in. I would suggest to do not take care for the results of this board. 3. 10 turns of patch cable have been wrapped over the Tape Wound Core. We will ask for a Calibration Run. ________________________________________________________________________ Sergio F. Novaes 21 June, 2003 DOE Guidelines to Foreign Visits These are the new DOE security guidelines for foreign visits to Fermilab and other national labs. http://www.ig.doe.gov/pdf/ig-0579.pdf ________________________________________________________________________ Dmitri Denisov Dates of the Summer shutdown are fixed The Lab has announced that Summer 2003 shutdown will start on August 25 and last for 7 weeks. There will be some "turn on" period for the accelerators after the shutdown with duration which is not yet well defined. Major reasons for the extended shutdown are: accelerators maintenance, recycler commissioning and electron cooling construction, and NuMi construction.