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.