Removing the tasks from the digitization (Ruben)2011-10-23T15:46:57Zhristovhristov@f7af4fe6-9843-0410-8265-dc069ae4e863hristovhristov@f7af4fe6-9843-0410-8265-dc069ae4e8632011-10-23T15:46:57Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=f21fc003c20acf4ef162ab5c82e902915a6c92f0

A lot of changes after detector review:2009-01-22T16:07:40Zcholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e863cholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e8632009-01-22T16:07:40Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=faf80567e50c3b411106dcc26a9d3e95b6a1fa1a

A lot of changes after detector review:
* AliFMDBaseDigit (and AliFMDDigit and AliFMDSDigit
by extension) derive from silly AliDigit.
* Up to 3 track labels propegated from hits to
digits and sdigits.
* Implemented AliFMD::Raw2SDigits (see also
scripts/TestRaw2SDigits.C).
* Added survey data of FMD1 and 2.
* Added FMD2 survey markers to geomtry.
* Survey to alignment is almost done. The code
is in AliFMDSurveyToAlignObjs. Note, FMD2
survey can only give FMD2 z-offset, while FMD1
survey can in priniple also give x,y offsets
as well as rotations. FMD2 z-offset is determined
as a best-fit of a plane to the available data.
* FMD2 and 3 are still roughly 4mm off from design. I
need to talk to ITS people about this.

Various fixes2009-01-15T00:24:30Zcholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e863cholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e8632009-01-15T00:24:30Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=b2e6f0b0e4ef3872ef9a6f1364370c91732a2650

Several changes:2008-12-16T07:46:03Zfcafca@f7af4fe6-9843-0410-8265-dc069ae4e863fcafca@f7af4fe6-9843-0410-8265-dc069ae4e8632008-12-16T07:46:03Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=7dd2cbe4f183e78c83c59e4a366a72cd04a7f660

Several changes:
- Removal of HBTAN
- Removal of libAnalysisOld (related to the above)
- Removal of the old event display (some remnants still need to be removed)
- Removal of the fHistogram data member in AliDetector, and related code
(it was never used)
- Removal of Euclid files and related code
- Removal of the class depending on the above
- Simplification of AliRun (more to come!)

Added code to put N_primary and N_total into all SDigits.2008-12-09T05:45:53Zcholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e863cholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e8632008-12-09T05:45:53Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=83ad576afc080f2194558539b48bb4ccb56790fc

Added code to put N_primary and N_total into all SDigits.
This is for background studies, so that we don't need to store hits.
In the not too distant future, we'll also add track references. See also
FMD/scripts/DrawSDigits.C.
Hans, perhaps you could check this code.

Several fixes (the Make-Federico-Happy-Commit):2008-08-25T09:27:41Zcholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e863cholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e8632008-08-25T09:27:41Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=ef8e862321a54d139b59b912a26975020e4dab67

Several fixes (the Make-Federico-Happy-Commit):
- Calibration: Redid calibration - sample rates where wrong.
- Alignment: Fixed bug in AliFMDAlignFaker and made new alignment
objects.
- Digitisation:
* Implemented digitisation from SDigits->Digits
* Reimplemented Hit->Digit conversion using loaders
only.
* Reimplemented Hit->SDigit conversion using loaders
only.
- Display: Fixed few problems here and there.
Note, this was completed a little a head of time of when I thought it would.
Basically, I managed to fix an urgent Hardware task quicker than I originally
thought. I guess patience is a virtue.

Fixes for SDigit generation. First attempt at making SDigit->Digit2008-08-18T00:33:20Zcholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e863cholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e8632008-08-18T00:33:20Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=42f1b2f58c7412f4914c2eeaaf691707aeac83b7

Fixes for SDigit generation. First attempt at making SDigit->Digit
conversion, by introducing class AliFMDSSDigitizer.

Massive commit to flesh out the geometry in more details.2008-05-09T15:43:51Zcholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e863cholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e8632008-05-09T15:43:51Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=d98fbfa5ba9387e9535c2288e6bce69d52473709

Massive commit to flesh out the geometry in more details.
Most of the geometry is there. Missing - if at all relevant are only
- Cooling pipes in FMD3
- Cooling fin in FMD2
Although all volumes are there, it should be noted that the
geometry should really be checked against CAD drawings and
installation/assembly notes. This will, however, take some
time to do, and I need some information from the relevant
parties.
What has been added to the geometry is
- Support of FMD2 - barrel, covers, and flanges.
- Support of FMD1 - both the upper and lower saucers are there.
- Digitiser cards on all half-rings.
- Cooling plates on FMD3
What has been changed in the geometry is
- Sensors are now put into an assembly together with the hybrid
cards and the stand-offs. This is to make it easier to have
enough clearance for alignment, and it is, after all, more likely
that the mounting of a module (sensor+hybrid+stand-offs) to the
honeycomb plates is less precise than the compound itself.
- The cone of FMD3 is now made as a composite shape of a cone minus
the openings where the cooling plates sit.
- Computations done more robust - gone are a lot of stupid fudge
parameters.
Other changes are for the display and alignement macros and similar.

Removing inheritances from TAttLine, TAttMarker and AliRndm in AliModule. The copy... 2006-11-14T17:11:17Zhristovhristov@f7af4fe6-9843-0410-8265-dc069ae4e863hristovhristov@f7af4fe6-9843-0410-8265-dc069ae4e8632006-11-14T17:11:17Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=e939a978a98d29901b86bdb02cdcaf5157e717de

Removing inheritances from TAttLine, TAttMarker and AliRndm in AliModule. The copy constructor and assignment operators are moved to the private part of the class and not implemented. The corresponding changes are propagated to the detectors

Applied patch from Raffaele to set symbolic names for the alignable2006-11-11T12:28:44Zcholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e863cholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e8632006-11-11T12:28:44Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=ee8a5fe69a998eb0bd7394b1b7f936c07dc32f7e

Applied patch from Raffaele to set symbolic names for the alignable
FMD volumes. Raffaele wrote:
Could you apply and commit the attached path? It is intended to be
temporary and to be fixed later by you but in the meantime, setting the
symbolic names for the 76 FMD alignable volumes as equal to the volume
paths, it avoids the warnings and hopefully it could make it easier
(and thus faster :)) for you to assign the proper symbolic names; at that
point I can also produce the zero misalignment objects for FMD so we
could accelerate the solution of this issue.
Note that I've modified the code a bit - it was too heavy. Also note, that
this code should be considered temporary - when I have time to wrap my
head around these symbolic name issues, I'll make some better names.
Actually, it should really be a job for the AliFMD[1,2,3] and AliFMDRing
classes to setup these things - probably via the AliFMDGeometry class.
Anyway, this should make Raffaele happy for now.

Added documentation of each file.2006-03-28T13:08:09Zcholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e863cholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e8632006-03-28T13:08:09Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=c2fc12580f7bb903a1f061ae3d60882098e8a988

Added documentation of each file.
Re-enabled RAW I/O using AliAltroBuffer and AliAltroRawStream.
Re-implemented AliFMDRawStream for better use with AliAltroRawStream.
Added strip range to calibration parameters. Perhaps I also need
a calibration that says how many pre-samples the ALTRO makes. Currrently
with the hardware we have now, it seems that the ALTRO makes 4 pre-samples,
regardless of the oversampling rate. However, we've only varied the
VA1 shift clock (between 5 and 1.25MHz), relative to 10MHZ for the ALTRO
sample clock. It may be that the number of pre-samples is a constant time,
which means it depends on the actual sample clock frequency. If that's the
case, then this parameter should be stored with the sampling rate parameter.
If not, then it should probably be stored independently.
I'm seriously considering making a base class, AliFMDIndex, like
struct AliFMDIndex {
UShort_t fDetector;
Char_t fRing;
UShort_t fSector;
UShort_t fStrip;
};
and have the `per-strip' classes derive from that, like
class AliFMDHit : public AliHit, public AliFMDIndex { ... }
class AliFMDDigit : public TObject, public AliFMDIndex { ... }
What does the experts think about that?

More docs2006-03-24T16:09:36Zcholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e863cholmcholm@f7af4fe6-9843-0410-8265-dc069ae4e8632006-03-24T16:09:36Zhttp://git.uio.no/git/?p=u/mrichter/AliRoot.git;a=commitdiff;h=9b48326f0faac4ff8ece535f303cc2b8a4860280