Christian, It seems as if you are looking at an old version of BrRawDataInput. All of the BrDigMultTile stuff is commented out and will be removed entirely shortly. There is now a BrDigTiles which contains an array for all of the ADC's. They are no longer put into a table. The BrDigMultSi does set the id in the version I have. That is kind of redundant at the moment, because all ADC's of all Mult detectors are read in each event as far as I know now. So the id would be directly related to the hit number. Same for the BrDigTiles. The identity of the detector is known by which entry it is in the array (fAdc[]) in BrDigTiles. These changes were made some time ago, so they are surely checked in. Hope this helps Kris Christian Holm Christensen wrote: > Hi All, again, > > Again, I took at the "BrRawDataInput::DecodeGlobal()", and it looks > like the identity of the Tile hit isn't written to the "BrDigMultTile" > object either, just as for the "BrDigMultSi". Agian, the same points I > made in the previous mail for the silicon strips, also applies here: > If you want to do analysis on fluctuations on event-by-event basis, > you really want to have this information. > > Also, it seems that in GBRAHMS 40 scintilator tiles are present, and > not 36 as in the IR. That is, there are 8 tiles on the ladder at the > inner (with respect to the ring) side of the array, not 4. Is this > right, or is it something else? > > Cheers, > > Christian ----------------------------------------------------------- > Holm Christensen Phone: (+45) 35 35 96 91 > Sankt Hansgade 23, 1. th. Office: (+45) 353 25 305 > DK-2200 Copenhagen N Web: www.nbi.dk/~cholm > Denmark Email: cholm@nbi.dk
This archive was generated by hypermail 2b29 : Thu Mar 16 2000 - 11:36:32 EST