Wed 28 May: ~16:00 arrival, unpacking
Thu 29 May: installation
Fri 30 May: beam on

1) Telescope + 8xSilC (~7hrs, overnight; first part)
2) 8xSilc, no telescope (fast runs during day)
3) Telescope + 8xSilC (~7hrs, overnight; second part after DUT shift)
4) 1xSilc, rotation
5) Belle, telescope

* starting telescope alignement
* adc delay scan, intcal, pedrun, pedcorr
* DUT alignement
* std. settings, telescope zero supr.(zp) 1st half, lunch break
* std. settings, telescope zero supr. 2nd half
* std. settings, telescope raw data, 1st half
* std. settings, telescope raw data, 2nd half
* optionally HV scan, tel. zp., (10 HV settings --> 2x 10 runs)
* unmount 7 DUTs
* std run 0 deg., (2 runs)
* angle scan (about 10 runs)      
* install Belle DUT
* std. settings, telescope raw, transparent mode
* std. settings, telescope sp, transparent mode, high statistics
* std. settings, telescope sp, processed mode, high statistics

SPS Status

Linac, PSB, CPS Status

• external: routerhephy.cern.ch (137.138.171.102)
  
• internal: 192.168.1.1
  US&ER /PA_SS'WD: admin/sensor
  
• WLAN-SSID: HEPHY
  
• WLAN-WPA-TKIP: testbeam08
  

• external: eudetmac001.cern.ch
  
• U1SE*R/P*AS§S/WD (ssh): eudet/gsigsi
  
• from EUDETMAC to TLU:
  ssh tlupc
  

• internal: 192.168.1.10
  
• external VNC: routerhephy.cern.ch (137.138.171.102:5900)
  pa2s2s2w2d: hephy
  

• internal VNC: 192.168.1.11
  pa2s2s2w2d: hephy
  

• external VNC: CWO-HNA453-H6B1.CERN.CH (137.138.61.206)
  

• 162471
  

• 165423
  

• Hostel (39-120): 79 120
  
• Private: +43 650 4243343
  

• Hostel (41-107): 60 107
  
• Private: +43 699 17251085
  

• Hostel (39-220): 79 220
  
• Private: +43 664 3769400 (switched off during testbeam)
  

• Hostel (41-222): 60 222
  
• Private: +43 699 19437327
  

• http://hpslweb.cern.ch/frame/java/1.1/view110-java.html
  
• Manual: http://jwenning.web.cern.ch/jwenning/documents/SPS/Operation/Page-1%20description.htm
  

• C:\WINNT\system32\javaws.exe http://abwww.cern.ch/ap/dist/cesar/cesar-gui/PRO/cesar-gui.jnlp
  

DUT, APVDAQ Documentation

Telescope:

APVDAQ Data Analysis
====================

The Vienna APVDAQ system has its origin in the late 1990s, and has grown and been improved since then.
Along with the hardware, also the software has grown and hence now consists of several steps rather
than a single piece of software.


DAQ and Analysis Chain
----------------------

Step 0: APVDAQ Software (=online) - CVI/LabWindows under Windows
        * controls and reads hardware, provides quick online analysis for online data quality check
        * can record software (pedestal), hardware (normal) or calibration runs
        * saves raw data (default) or hardware-zero-suppressed data

Step 1: APVDAQ_Analysis - CVI/Labwindows under Windows
        * essentially an improved version of step 0, reads step 0 data from file and performs pedestal 
          subtraction, common-mode correction, hit finding and clump finding (=2D-clustering; we record
          typically 6 samples along the shaped waveform for each event for later peak time reconstruction;
          thus clustering is not only done along strip axis, but also in time -> we search for contiguous
          hit clouds within the two-dimensional x-t-domain and sum up the cluster for each time point)
        * saves clustered waveform hit data (typically 6 sampled values per hit)

Step 2: hitfitgui - ROOT under Linux
        * reads the clustered waveform hit data from step 1 and performs a waveform fit for each hit with the
          reference waveform created from calibration data, resulting in peak amplitude and peak time for each
          hit which is compared to a reference time obtained with a TDC (included in the APVDAQ hardware)
        * saves peak amplitude and time information per hit

Step 3: anarun.C - ROOT under Linux
        * reads the hit properties file from the previous step and fills the data into several histograms like
          Signal, SNR, Noise, Cluster Width, Eta distribution etc. for subsequent graphical display, including
          Landau*Gauss fits and p-n side correlations
        * saves several plot canvasses as PS files


What we don't have
------------------

Tracking, alignment and such things. I think that the best starting point for these functions is the step 2
output data, as this is the most compact form of data and almost directly represents spatial hit points.


General things to consider
--------------------------

* All counting starts from zero
* Strip numbers are counted by hybrids and can span over up to 4 APV chips (=strip numbers 0..511)
* The first 600 events are always software-triggered and used for pedestal and noise evaluation. Thus, event
  numbers 0..599 will never appear in the zero-suppressed data
* The TLU event number is stored separately and does not correspond to the APVDAQ internal event number
* Zones were introduced to label detector regions of different properties, such as the 16 (!) geometrically
  different regions of the SiLC test structures, each comprising only 16 strips
         

Step 1 (APVDAQ_Analysis) output data format
-------------------------------------------

The first step of offline analysis produces a zero-suppressed data file stream out
of the raw data file, thus reducing the file size considerably. 
The zero-suppressed file (file name ends with "_cluster.hit") uses the following structure.


#define MAX_SUBEVENTS       6             // maximum number of samples in one readout buffer
#define MAX_HITS_PER_EVENT  200           // maximum number of hits per event
#define MAX_CLUSTERWIDTH 20               // maximum cluster width

#define P_SIDE	0                         // p-side of the sensor
#define N_SIDE	1                         // n-side of the sensor 

typedef struct {
   unsigned long event;                   // APVDAQ event number
   unsigned char numberofsubevents;	  // number of samples in this event
   unsigned short numberhits;		  // total number of hits (clumps) in this event

   unsigned char hitbegin;  	          // sample number of the begin of the hit
   unsigned char hitlength;     	  // number of samples of this hit
   unsigned short first_strip;		  // first strip of the cluster
   unsigned char clwidth;		  // cluster width
   double center_strip;  		  // center-of-gravity of the cluster (counted in strip units)
   double center_coord;  		  // coordinate of the center strip
   unsigned char side;           	  // sensor side, P_SIDE = 0, N_SIDE = 1
   unsigned char module;                  // module number (internal=0,1,...)
   unsigned char zone;			  // zone number (internal=0,1,...)
   unsigned short tlueventnumber;	  // TLU event number (was previously reserved2)

   double eta;				  // eta of cluster peak
   double clnoise;			  // calibrated cluster noise
   double reserved;			  // used for calibration constant

   double clsigcal[MAX_SUBEVENTS];	  // calibrated cluster signal of all subevents

   double tdc;                            // time of digital conversion
   
   double strsigcal[MAX_CLUSTERWIDTH][MAX_SUBEVENTS];	// calibrated strip signal of all samples
   double strnoise [MAX_CLUSTERWIDTH];			// calibrated strip noise

} Clusterhit_t;

Clusterhit_t clhits[MAX_HITS_PER_EVENT];  // cluster hits of the current event


Each structure array element describes a single clump (2D cluster) found in one sensor plane
in one particular event.
The APV25 chips read out 6 consecutive samples for each strip, spaced by 25ns (MAX_SUBEVENTS).
Hence, the term "cluster" is extended into 2D, with strip number and time sample as coordinates,
leading to a "clump".
A clump is a cluster built from one or more strips and spanning over several time samples.
The total number of clumps per event is stored in the "numberofhits" field, so the procedure
to read the complete event data is to read one element first, then numberofhits-1 more elements.


Step 2 (hitfitgui) output data format
-------------------------------------

The data structure looks very similar to the previous one, except that the (typically) 6 samples values along
the shaped waveform are replaced by a single value pair: peak amplitude and time. Well, actually, there are 3
pairs obtained in different ways, where the last one (i.e. sigcal[2] and tpeak[2]) are most accurate.
The output file (file name ends with "_cluster.hit.fit") uses the following structure.


typedef struct {
   unsigned long event;                 // master event number
   unsigned char numberofsubevents;     // number of subevents in this master event
   unsigned short numberhits;           // total number of hits (clumps) in this event
   unsigned short numfithits;           // total number of fitted hits (clumps) in this event

   unsigned char hitbegin;              // subevent number of the begin of the hit
   unsigned char hitlength;             // number of subevents of this hit
   unsigned short first_strip;          // first strip of the cluster
   unsigned char clwidth;               // cluster width
   double center_strip;                 // center strip of the cluster
   double center_coord;                 // u or v coordinate of the center strip

   unsigned char side;                  // sensor side, N_SIDE, P_SIDE
   unsigned char module;                // module number (internal=0,1,...)
   unsigned char zone;                  // zone number (internal=0,1,...)

   double tdc;                          // time of digital conversion

   double eta;                          // eta of cluster peak
   double clnoise;                      // calibrated cluster noise

// OLD:
//   double reserved;                     // reserved for future use
//
// NEW:
   unsigned short tlueventnumber;	  // TLU event number
   unsigned short reserved2;
   unsigned long reserved3;

   double sigcal[3];                    // fitted hit amplitude {raw data max / expfit / calfit}
   double tpeak[3];                     // fitted peak time {raw data max / expfit / calfit}
   
   double strsigcal[MAX_CLUSTERWIDTH][MAX_SUBEVENTS];	// calibrated strip signal of all samples
   double strnoise [MAX_CLUSTERWIDTH];			// calibrated strip noise

} FittedHit_t;

FittedHit_t fithits[MAX_HITS_PER_EVENT];


Each structure array element describes a single clump (2D cluster) found in one sensor plane
in one particular event.
The total number of clumps per event is stored in the "numberofhits" field, so the procedure
to read the complete event data is to read one element first, then numberofhits-1 more elements.





To be continued...

Stephan: weil ichs immer hier suche hab ich das Wafer Layout file geadded ;-)

The SILC DUT is a stack of 8 silicon sensors surrounded by the telescope.
The spacing between each of the 8 layers is 20mm. Seen with the beam, the fourth layer is exactly centered
between the telescope legs. This means that the stack as a whole is not exactly centered, as there is no
'center' module with an even number of layers. Please refer to drawings "telecope_single_dut.gif" and
"telescope_8_dut.gif" below.

Each sensor has 256 strips, which are read out by 2 APV25 chips. The numbering order of the modules follows the
beam direction (see drawing "silc_dut_stack_beam.jpg"). Modules will have the connector (and thus APV25 hybrid)
at the top as shown in the photos. The numbering scheme within one module is shown in drawing
"silc_dut_beam.jpg": Looking with the beam, strips are numbered from right to left. The strip pitch is 50um
everywhere.

The APVDAQ software works on APV25 level for the data acquisition, where raw data is saved. In that case, the
APVs are consecutively numbered 0,1 (=module 0), 2,3 (=module 1), 4,5 (=module 2), ... ,14,15 (=module 7).
In later steps of the analysis, data are presented on a module [0..7] / strip [0..511] base.
Zone numbers were removed, now everything is zone=1.
(Zone 0 is a reserved value and hence the actual zone counting starts with 1.)

The 256 strips are divided into 16 groups of 16 strips each with different strip width and intermediate strips,
according to the table below:
	 	pplus strip  	number of
		width 	intermediate
group#	strips 	[µm] 	strips
 0	16 	6 	none
 1	16 	10 	none
 2	16 	12.5 	none
 3	16 	15 	none
 4	16 	20 	none
 5	16 	25 	none
 6	16 	6 	single
 7	16 	7.5 	single
 8	16 	10 	single
 9	16 	12.5 	single
10	16 	15 	single
11	16 	17.5 	single
12	16 	6 	double
13	16 	7.5 	double
14	16 	10 	double
15	16 	12.5 	double

Please note that the strip pitch is 50µm everywhere, but between each group there is a gap of a single missing
strip. Hence, when calculating the coordinate from the strip number, one must take those distinctive gaps into
account.

We assume that we have a fractional strip position, where the fraction denotes (e.g.) the center of gravity of
the cluster. In order to convert this into a coordinate, we can use the following approach (where s is the
(fractional) strip number and x ist the fractional coordinate [µm]):

 /* *** tested and works *** */

double strip2x(double strip)
{
 unsigned short ints;

 // this is the integral part of the strip number
 ints = (unsigned short) strip;
 
 return ( 50.0 * ( strip + ( ints >> 4 ) ) + ( ( (ints+1) & 15 ) ? 0.0 : ( strip - ints ) * 50.0 ) );
 //       pitch    strip 
 //                          gaps between zones
 //                                                outside gap ? do nothing
 //                                                                      account for double pitch within gap 
    
}

Power-on Procedure
==================

PC logon: user "testbeam", pwd "sensor"

Order for switching on the hardware (not strict):
* VME 9U crate
* keithley instruments
* +-5V (fat) 2 lab power supplies (left stack)
* other 3 lab power supplies (right stack)
    BE CAREFUL NOT TO CHANGE DIALS AT ALL DURING SWITCHING!!!

Run ResMan.exe (shortcut on desktop) and click OK to close
Start longterm-R31.vi (shortcut on desktop) and start HV bias
Start APVDAQ.exe 

Now everything is on and ready to operate.
This is also the condition after a run is finished.


Start Run (see screenshot below)
================================

1. select proper run type (if different from previous run), typically
 Hardware (beam) or
 Software (pedestal) or
 Internal Calibration

2. open proper config file (if different from previous run), one of
 cern08_silc_all_single.cfg   (8 DUTs, 1 sample)  - for software (pedestal) and intcal runs
 cern08_silc_all_multi6.cfg   (8 DUTs, 6 samples) - for hardware (beam) runs

 cern08_silc_mod03_single.cfg (1 DUT, module 03, 1 sample)  - for software (pedestal) and intcal runs
 cern08_silc_mod03_multi6.cfg (1 DUT, module 03, 6 samples) - for hardware (beam) runs
 

3. select file name (typically: increase run number)

4. switch Write File ON (if turned off)

5. write some useful comments (conditions, HV, etc)

6. enter number of events

7. hit "Start Run" and relax or cry for help :-)


Additional Info
===============

path to APVDAQ:   e:\cvi-projects\apvdaq_fadc
path to Longterm: e:\labview-projects\longterm R3.1
path to data:     f:\testbeam\cern_jun08\silc\data

SiLC beam test - CERN SPS June 2008
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=+2 mm
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12 (now for real)
telescope: zero supressed, new firmware

- long break in the middle due to power outage after thunderstorm

horizontal position ("target") = +2.0mm - after we decided to scan the whole area in 3 steps
this is RIGHT position

all 3 positions are:
RIGHT: +2.00 mm    <--- this run
MID:   -2.75 mm
LEFT:  -7.50 mm

SiLC beam test - CERN SPS June 2008
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=-2.75 mm
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12 (now for real)
telescope: zero supressed, new firmware

horizontal position ("target") = -2.75mm
this is MID position

SiLC beam test - CERN SPS June 2008
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=-7.5 mm
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: zero supressed, new firmware

horizontal position ("target") = -7.5mm
this is LEFT position

SiLC beam test - CERN SPS June 2008 - HIT MODE
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=-7.5 mm
trigger: 9 mm opening, TLUControl.exe -d 2 -a 12 (manually)
no telescope

This is LEFT position
APVDAQ runs in HIT MODE (=0-suppressed)
acquisition rate ~300 Hz during spill

SiLC beam test - CERN SPS June 2008 - PEDESTAL
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=-7.5 mm
software trigger
no telescope

PEDESTAL with BEAM (10k events) @ LEFT

SiLC beam test - CERN SPS June 2008 - PEDESTAL with beam
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=-2.75 mm
software trigger
no telescope

PEDESTAL WITH BEAM (10k) @ MID

SiLC beam test - CERN SPS June 2008 - HIT MODE
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=-2.75 mm
trigger: 9 mm opening, TLUControl.exe -d 2 -a 12 (manually)
no telescope

This is MID position
APVDAQ runs in HIT MODE (=0-suppressed)
acquisition rate ~300 Hz during spill

SiLC beam test - CERN SPS June 2008
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=-2.75 mm
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: raw, new firmware

right from the start: no beam...

Very simple alignment (manual linear x direction shifting only, no rotation, assuming equal z spacing) and tracking.
Reference plane = Module 3 (~center)
Deviation calculated from track prediction using the other layers.
Simple Center-of-gravity algorithm (as of APVDAQ_Analysis), no eta applied.
Using only events which have exactly 1 hit per plane (~80% of all events).

Results: 
 Residual RMS = 4.99 um (REFERENCE against neighbor layers 2+4 only)
 Residual RMS = 6.35 um (REFERENCE against all 7 other layers) -> needs more sophisticated alignment

SiLC beam test - CERN SPS June 2008 - PEDESTAL with beam
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=+2 mm
software trigger
no telescope

this is RIGHT position

SiLC beam test - CERN SPS June 2008 - HIT MODE
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=+2 mm
trigger: 9 mm opening, TLUControl.exe -d 2 -a 12 (manually)
no telescope

This is RIGHT position
APVDAQ runs in HIT MODE (=0-suppressed)
acquisition rate ~430 Hz during spill (TLU says ~86 Hz)

• The first is zero supression an cluster finding done with "apvdaq_analysis_fadc" (Labwindows/CVI application)
  
• The second stage is hit time reconstruction done with ROOT. (hitfit)
  

• start apvdaq_analysis_fadc within the virtal Windows XP machine (parallels).
  
• select a runfile, e.g. run0001.dat
  
• select a propper calibration file, default is "cal002.out"
  
• select pedestal correction file, default is "pedcorr001.ped"
  
• enable "generate hit file and save results"
  
• click "Start"
  
  
• The result of the analyis is a file containing all hits above threshold, the filename is "xxxxxxx_cluster.hit", where xxxxxxx is the run name
  
• The data structure of the file is described at http://elog.hephy.at/testbeam-SPS08/04
  
• The file is located in the same folder as the raw data file (= data)
  

• Once apvdaq_analysis_fadc is finished, start a console window and change into the directory /Volumes/Data/eudet/APVDAQ
  
• execute ./hitfitrun nnnn, where nnnn is the run number
  
  
• results: file with fitted hits (data structure see http://elog.hephy.at/testbeam-SPS08/04) as well as several plots.
  
• file name: xxxxxxx_cluster.hit.fit, the file is located in the subdirectory output.
  

SiLC beam test - CERN SPS June 2008
8 modules, HV=100V, 40MHz, 6 samples, hor stage :=+2.0 mm
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: raw, new firmware

last raw run in RIGHT position

SiLC beam test - CERN SPS June 2008
HV scan,  HV=100V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12


Reference run with nominal HV after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=10V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=20V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=30V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=40V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=50V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware

stopped after beam problem


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=50V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware

re-try after several hours of beam down


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=60V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=70V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=80V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=90V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=120V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=150V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
HV scan,  HV=200V
8 modules, modules rearranged, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


HV scan after re-arranging the modules:

               JURA
          | | |
          | | | | |
beam ---->| | | | | | | |
                | | | | |
                    | | |
          0 1 2 3 4 5 6 7
               SALEVE

SiLC beam test - CERN SPS June 2008
Angle scan,  HV=100V, alpha = 10 degrees
8 modules, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware

Angle scan with pattern mask

SiLC beam test - CERN SPS June 2008
Angle scan,  HV=100V, alpha = 20 degrees
8 modules, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware

Angle scan with pattern mask

SiLC beam test - CERN SPS June 2008
Angle scan,  HV=100V, alpha = 30 degrees
8 modules, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware

Angle scan with pattern mask

SiLC beam test - CERN SPS June 2008
Angle scan,  HV=100V, alpha = 40 degrees
8 modules, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware

Angle scan with pattern mask

SiLC beam test - CERN SPS June 2008
Angle scan,  HV=100V, alpha = 50 degrees
8 modules, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware

Angle scan with pattern mask

SiLC beam test - CERN SPS June 2008
Angle scan,  HV=100V, alpha = 60 degrees
8 modules, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware

Angle scan with pattern mask

Please note that there are 8 modules read out in this run, but the last one (#7) is placed outside the beam and
hence does not provide any meaningful data.

SiLC beam test - CERN SPS June 2008
Angle scan,  HV=100V, alpha = 0 degrees
8 modules, 40MHz, 6 samples, hor position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware

Angle scan with pattern mask

SiLC beam test - CERN SPS June 2008
HV=100V, xy "telescope"
8 modules, 40MHz, 6 samples, position centered
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


this is a run where modules 0,2,4,6 are in normal position, while modules 1,3,5,7 are rotated by 90 deg
(counterclockwise as seen by the beam) and flipped (back<->forth) in order to achieve the minimum spacing
(~10.3mm) between "corresponding" x and y planes.

SiLC beam test - CERN SPS June 2008
4 Belle modules, 40MHz, HV=80V, 6 samples
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


Flex_Module has only 1 working APV - control bonds suffered during transportation

Position is approximately similar to KEK Nov 2007, however it appears like JP_module is flipped (up-down) w.r.t.
to other modules

SiLC beam test - CERN SPS June 2008 - HIT MODE
4 Belle modules, 40MHz, HV=80V, 6 samples
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


Flex_Module has only 1 working APV - control bonds suffered during transportation

Position is approximately similar to KEK Nov 2007, however it appears like JP_module is flipped (up-down) w.r.t.
to other modules

SAME AS PREVIOUS, BUT 0-SUP WITHOUT TELESCOPE


stuck after 45020 events with the repeated message  
 ***WARNING*** FIFO3 empty, FADC 0. Event discarded, reset sent.
to be investigated.

SiLC beam test - CERN SPS June 2008 - HIT MODE
4 Belle modules, 40MHz, HV=80V, 6 samples
trigger: 9 mm opening, TLUControl.exe -d 10 -a 12
telescope: 0sup., new firmware


Flex_Module has only 1 working APV - control bonds suffered during transportation

Position is approximately similar to KEK Nov 2007, however it appears like JP_module is flipped (up-down) w.r.t.
to other modules

RETRY

STUCK again after some time - now adding veto clear in error handling routine

SiLC beam test - CERN SPS June 2008 - HIT MODE
4 Belle modules, 40MHz, HV=80V, 6 samples
trigger: 9 mm opening, TLUControl.exe -d 2 -a 12
no telescope


Flex_Module has only 1 working APV - control bonds suffered during transportation

Position is approximately similar to KEK Nov 2007, however it appears like JP_module is flipped (up-down) w.r.t.
to other modules

RETRY after software bugfix - apparently works

SiLC beam test - CERN SPS June 2008
4 Belle modules, 40MHz, HV=80V, 6 samples
beam on (lower intensity)