Minutes of the ST-Testbeam Run-Meeting - July 7, 2004
=====================================================

General
-------

 - next run meeting on Monday, July 8, 15:00

 - stable beam, with sufficient high lumi that we have
   not observed a slower data taking rate.


Report from yesterday untill 15:00 today
----------------------------------------

  - after beam came back on, it got also finally
    delivered in our area.

  - data was taken, but some problems with our daq
    system prevented us from completing the HV scan.

  - During the night-shift, the daq program crashed during
    the initialization of the sharc boards. Problem was solved
    by switching off the crate and removing and putting back the
    sharc boards.

  - however, the shift crew found out later that no tracks were
    found in the runs taken since. Data taking was aborted until
    experts came back in the morning.

  - a latency scan was performed, and from that it was concluded
    that somehow the latency has changed from the original value
    of 73 to 65. It is unclear how this happend, nor do we know why...

  - Finally, the HV scan was completed.


Measurement program (aka todo list)
-----------------------------------

 - bring/keep documentation up to date

 - log all actions in the *** logbook *** and/or
   in the *** spreadsheet ***

   don't forget to document
     - beam conditions
     - voltages
     - currents
     - temperatures

   These parameters should be logged once per hour,
   NOT only once per HV point!


Plans:
-----

 - adjust the sampling point of the ADC.

 - possibly adjust the gain for the Beetles at the optical receiver
   end. An attempt to do this for one chip will be undertaken.
   If this turns out to be too risky, the gain will be left as it is.

 - pulseshape scans for two values of HV, two values
   of Vfs and 100K per point.
   HV settings: 450V on all substrates for the 'high' HV
                nomimal (i.e. 1.5 X depletion voltage)
	        for the other HV point.
   Vfs: 100 and 400

   Data points: 6 data points around the maximum, with a spacing
                of 5 ns.
                With t = 0 for the maximum, that would be
                -15, -10, -5 0 +5 +10 (in ns)
                +20, +25 +30 +40 +50 +60 +70 +80 +100 +120 (in ns)

   With a data taking rate of roughly 100K events in 30 minutes,
   this would constitute:
   2 (HV points) x 2 (Vfs points) x 16 (points) x 30 (minutes) = 32 hours

   Given our data taking efficiency, including the beam-delivery
   efficiency, this would take us close to 6 shifts or two days.




Cheers,



	Johan