GSI Forum: General » Re-Mapping of SDS SensorIDs

Home » PANDA » PandaRoot » General » Re-Mapping of SDS SensorIDs

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

Re-Mapping of SDS SensorIDs [message #21793]

Tue, 21 November 2017 17:30

Stefan Pflueger
Messages: 99
Registered: February 2012

continuous participant

From: *specf.him.uni-mainz.de

Hi,

I want to assign the SensorID's of the Lmd Pixel sensor volumes with a fixed number. Right now the ID's of active volumes are just globally counted and referenced to the volume paths. So depending on which Detectors you load in the simulation first the ID's of the sensors vary. I thought about introducing a remapping function that would take the global sensor ID get the volume path and with that information remap it to some specific sensor ID of the detector (in the case of the lmd sensors 0-399). I did not look deeply, but I could not find any function so far that would allow me to do this. I think this would be needed in a general way (so not only for the sds hits) and should be implemented in the digitization stage. Could anyone comment on this? I would implement this in a general way in the digitization stage. Is this a good idea?

Best regards,
Stefan

Report message to a moderator

Re: Re-Mapping of SDS SensorIDs [message #21796 is a reply to message #21793]

Tue, 21 November 2017 17:41

Ralf Kliemt
Messages: 507
Registered: May 2007
Location: GSI, Darmstadt

first-grade participant

From: *gsi.de

Hi Stefan,

Until now we did not need fixed sensor id's. The dynamic tool is sufficient as it creates for each simulation a global(!) one-to-one map of the active volumes. Fixed numbers may counter these benefits.
What is your issue with the dynamic IS?

Cheers!
Ralf

Report message to a moderator

Re: Re-Mapping of SDS SensorIDs [message #21799 is a reply to message #21796]

Tue, 21 November 2017 19:14

Stefan Pflueger
Messages: 99
Registered: February 2012

continuous participant

From: *dip0.t-ipconnect.de

Hi Ralf,

yeah the global one-to-one mapping of active volume paths to a global sensorID is good and I don't want to change that. Basically I need to know in a "secure" manner, which sensor is fired based on the sensorID associated with the hit (so where this sensor is located in the setup). With secure I mean that it will always deliver the correct result. Atm I don't think this is possible, because the global sensorID (which is assigned to each active module) depends on the order you load the detector modules. The LMD has 400 active sensors atm. If I load that detector first I get assigned 0-399. If I load MVD first I get something like 500-899. How is it planned later on in the runtime? I believe every sub detector gets a unique ID and then each subdetector can assign its sensor ids as they wish, or not (as long as its one-to-one)? Therefore a mapping of the global sensorIDs to the actual sensorID scheme used later on would be necessary. Maybe I'm also missing something here...

Cheers,
Stefan

Report message to a moderator

Re: Re-Mapping of SDS SensorIDs [message #21802 is a reply to message #21799]

Tue, 21 November 2017 20:21

Ralf Kliemt
Messages: 507
Registered: May 2007
Location: GSI, Darmstadt

first-grade participant

From: *dyn.telefonica.de

Hi,

We actually do that by the geometry path string.
Also the PndGeoHandling can transform your coordinates, to and from volumes by ID or path. Maybe that's already what you need?

https://subversion.gsi.de/trac/fairroot/browser/pandaroot/trunk/PndTools /generalTools/PndGeoHandling.h

Cheers!
Ralf

Report message to a moderator

Re: Re-Mapping of SDS SensorIDs [message #21807 is a reply to message #21802]

Wed, 22 November 2017 09:19

Stefan Pflueger
Messages: 99
Registered: February 2012

continuous participant

From: *dip0.t-ipconnect.de

Hi Ralf,

ok correct me if I'm wrong. The PndGeoHandling class can convert the volume path to the globalID (or shortID). Now later on when the experiment runs the Lmd detector sensors for example will be assigned ids 0-399 (in some order we like). How do you connect that sensorID to a sensor on the geometry? Because that is the data the experiment will deliver or not? I dont see how this works atm. Of course you could assign every sensor in panda the same ID as the geometry globalID, but that concept would not be very open to changes.

Cheers,
Stefan

Report message to a moderator

Re: Re-Mapping of SDS SensorIDs [message #21832 is a reply to message #21793]

Mon, 27 November 2017 09:58

Ralf Kliemt
Messages: 507
Registered: May 2007
Location: GSI, Darmstadt

first-grade participant

From: *gsi.de

Hi Stefan,

Today we'll have our computing eZuce meeting at 2pm. It would be a good idea to discuss your issues there in person. I'm not entirely sure, yet, why this is an issue.

Cheers!
Ralf

Report message to a moderator

Re: Re-Mapping of SDS SensorIDs [message #21835 is a reply to message #21832]

Mon, 27 November 2017 10:29

Stefan Pflueger
Messages: 99
Registered: February 2012

continuous participant

From: *specf.him.uni-mainz.de

Hi Ralf,

all right. I will be there

Cu later

Report message to a moderator

Previous Topic:	Initialization Error of Geane using Geant3 (duplicate)
Next Topic:	Migration to git

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Nov 27 05:18:05 CET 2024

Total time taken to generate the page: 0.00576 seconds