GSI Forum: Data Analysis » flag for different data structures

Home » R3BRoot » Data Analysis » flag for different data structures (data structures)

Show: Today's Messages :: Polls :: Message Navigator

flag for different data structures [message #18879]

Tue, 12 January 2016 12:57

Michael Heil
Messages: 4
Registered: July 2015

occasional visitor

From: *gsi.de

In Neuland we have the old Tacquila and now the new Tamex electronics. The data structrue and therefore R3BNeulandRawItem and R3BNeulandMappedItem are not the same. How can we differ between them? Can we set a flag in the macro according to the used electronics? Or is there already a feature included?

Report message to a moderator

Re: flag for different data structures [message #18882 is a reply to message #18879]

Tue, 12 January 2016 15:43

Dmytro Kresan
Messages: 166
Registered: June 2004

first-grade participant

From: 93.77.23*

Hi Michael,

There is no feature included yet.

I propose a following solution. According to the UCESB interface design we will have 2 separate readers for Tacquila and Tamex. So we can have 2 different data classes, which will be stored in TClonesArray by a reader. During the next stage, the TCAL calibration task will recognise which class is stored in the array, will do a cast to proper type and handle it accordingly. So no flag in the macro is needed.

In addition, if there are 2 - 3 common data members for Tacquila and Tamex data classes - it makes sense to create a common base class.

For the moment, you can create additional data class for Tamex. Then I will modify TCAL calibration tasks. Later we will decide wether a base class is needed.

Cheers,
Dima

Report message to a moderator

Previous Topic:	Ucesb Interface in R3BRoot
Next Topic:	Data levels in R3Broot - suggestion

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Sep 16 17:37:36 CEST 2025

Total time taken to generate the page: 0.00712 seconds