Thermal behavior of a TOB rod prototype
 


Where to find the files:

Hostname: pcepcmt17.cern.ch
Username: control
(To have the password, ask me or Laurent)
Directory: ~/slow


TOB rod setup:

rod layout

Have a look here.


Induction of noise from the temperature probes:

The external probes attached to the system can induce additional noise.
To study the noise, launch ~/anal/job/test1_rob.job and then analyze the ntuples with the macro ~/anal/anal/showpfast.kumac (which shows several noise estimators for every APV; a nicer display, joining APVs in modules, is obtained by ~/anal/anal/showp3.kumac).
Reference runs: 20690 (before installation of the probes) 20694 (after installation of the probes). A worsening of the noise profile is apparent (it's particularly clear from a comparison of page 4 of these files).
To do: check it for run 20702 (see later) both in the transient and in the plateau.


Pedestal vs time:

A pedestal run (number 20702) was taken on 15/5/2003 from 11:42:33 to 12:01:30. The aim is to correlate the rise of the noise during this run with the thermal evolution of the system (our guess is that the variation in the pedestals is due to a variation in the gain of the optohybrids).
To analyze it, run ~/anal/job/test1_andrea.job as explained here, having care that the flag ROB has the value FALSE (i.e.: noise analysis; with TRUE the program executes the physics analysis described in tob.html).
The ntuples can be read by ~/slow/ped.f, which writes an only row-wise ntuple with the correct module numbering. This new ntuple can be read by the PAW macro ~/slow/ped.kumac, showing the evolution of the average ADC counts per APV as a function of the event number.

Warning: only the first 600 seconds are plotted, due to memory problems:
***** ERROR in HRZOUT : An error has occured whilst writing data : ID= 1 RZOUT . Request exceeds quota

To do:


Temperature vs time:

In the slow control database you can find all the data from DCU, embedded and external probes.
In the "command" field, the instruction select * from slowcontrol where name='dcu' will give only the records relative to the DCU readings, name='emb probe' and name='ext probe' will give the embedded and external probes readings. Save the output pages as output_dcu.html, output_probes_emb.html and output_probes_ext.html.
Program ~/slow/readdb.f (to be compiled with gmake -f readdb.mk) reads data from these html files, recognizes the type (this is not trivial for DCUs, for which the routine ~/slow/idconvert.f has been designed) and writes them in text files to be analyzed in PAW with ~/slow/plot.kumac. It also converts, calling ~/slow/timeconversion.f, the timestamp (written as milliseconds from 1/1/1970) in hh:mm:ss (warning: in solar time!).

Thermal measurements performed:

Calibration curves obtained with macro ~/slow/calib2.kumac, using only the first measurement of every data set. With this calibration, the temperature readings from the DCU, for 16/5/2003 data, are these (also shown are the 2.5 and 1.25 volts tensions and the leakage current). How do we justify these spreadings in temperature?
To do: perform the calibration using all the points from all the data sets, and make a comparison with the calibration from the only first points.
The calibration with only the first points, while having much less statistics, is also much less affected by systematics arising from dissipation (we believe that dissipation also explains the deviations from linearity in the calibration curves shown in the list above). The comparison should help to estimate this effect.


Open issues:


Position of the temperature probes:

External probes (with normal duct tape when not otherwise specified):

Embedded probes:


DCU channels:


Contact me (andrea.giammanco@pi.infn.it) for any question about the files.