GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » EMC » Bump splitting: new endcap vs. old endcap
Bump splitting: new endcap vs. old endcap [message #7833] Wed, 04 February 2009 19:21 Go to previous message
Bertram Kopf is currently offline  Bertram Kopf
Messages: 110
Registered: March 2006
continuous participant
From: *ep1.ruhr-uni-bochum.de
Dear all,
I tested the bump splitting for a couple of different scenarios. 5 GeV/c pi0's have been simulated separately for the forward endcap (10-20 deg) and for the forward barrel part (30-90 deg) for two different geometries. I used in the simulation macro the initialization
Emc->SetGeometryFileName("emc_module12345.dat");
for the old geometry;
and Emc->SetGeometryFileNameDouble("emc_module1245.dat","emc_module3new.root ");
for the new geometry and changed moreover the mapper version number to 1 (old) and to 2 (new) in all.par and emc.par.

I got the following results with the bump analysis qa macro provided by Dima:

1. Everything looks more or less o.k. for the barrel part (30-90 deg) (black=old, red=new)

index.php?t=getfile&id=4999&private=0

2.In comparison to this the results for the forward part (10-20 deg) look completely different (black=old, red=new) and it seems that there is only something wrong with the new geometry.

index.php?t=getfile&id=5000&private=0

My assumption is that something is not properly initialized in the new EMC geometry setup (e.g. EmcMapper, TwoCoordinateIndex, etc.) and that the bump splitting algorithm works fine.

Due to this I have a few questions / remarks:

1. Is there a tool available with which one can easily check whether the crystal neighbour list, TwoCoordinateIndex, etc. are o.k.?

2. All the geometry information will be handled via the singleton objects "PndEmcMapper" and "PndEmcStructure".
The static function instance has to be called with arguments here: e.g. static PndEmcMapper* Instance(Int_t, TString geoName="");
This suggests that one can get different mappers by steering it via these arguments. But this is not the case: Once initialized, the instance will never be changed afterwards.
In the code the instance of the mapper is sometimes called with fixed arguments: e.g. PndEmcMapper::Instance(0), etc.. Therefore my question: Who takes care of the initialization for such global objects. How is it guaranteed that the instance will be called there the first time in the application?

3. Would it make sense to introduce an EMC initialization sequence where everything will be initialized centrally at one place.

4. Does it make sense to introduce a global Emc environment class where all global emc environment objects are collected?

Best regards,
Bertram.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: correction in emc bump splitting
Next Topic: New geometry of the Backward EndCap
Goto Forum:
  


Current Time: Tue Feb 07 09:48:51 CET 2023

Total time taken to generate the page: 0.01053 seconds