Hi Florian, Could you clarify what you mean by "Frame" >From your brief explanation, I do not see why a TH2S histogram is not sufficient. The histogram number being the framenumber, row, col obvious and the adc the content (a short sufficient?) In case you intend to make statistical calculations using zillions of frames, a TTree would seem to be the most appropriate storage. Rene Brun Florian Schopper wrote: > > Dear rooters, > > we want to implement analysis-software for a CCD-readout using > root. The Data consists then of sets of 2D-frames of Float-data. > What class would be the most straightforward way of storing the frames, such > that the data can be easily analysed, projected, visualized .... > I thought of either 3D-Hists or ntuples (adc:row:col:framenumber), but: > > - 3D-Hists are nice to project into 1D, 2D Hists for analysis, but if you > want to add more frames or continuously add frames, increasing the size > seems unappropriate. > > - ntuples seem to be a waste of Memory because row and col are indexes only > and not Floats. > I also thought of using arrays of 2D-Hists but they are then > uncomfortable to project in the direction of Pixel versus Framenumber. > > Are there more appropriate classes which I didn`t consider, or should we > implement our own class? > > cheers, > Florian > > ---------------------------------------------------------------------- > Florian Schopper office: MPI Halbleiterlabor > > Ludwig-Merk str. 3 Otto-Hahn-Ring 6 , Gebäude 72 > D-80805 München D-81739 München > Germany Germany > > phone: 49/89/32455680 phone mpe: 49/89/30000 3625 > phone HLL: 49/89/839400-45 > > e-mail: fls@mpe.mpg.de > http://www.gamma.mpe-garching.mpg.de/MEGA/mega.html > ----------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:45 MET