GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Bugs, Fixes, Releases » Meaning of Core dump due to Geane application at rec. part
Meaning of Core dump due to Geane application at rec. part [message #11915] Fri, 27 May 2011 11:34 Go to next message
donghee is currently offline  donghee
Messages: 385
Registered: January 2009
Location: Germnay
first-grade participant
From: *kph.uni-mainz.de
Dear all,

I have funny problem and cannot understand the reason of fatal error.

When I do run reconstruction macro (with TPC) in my local machine, the output comes out smoothly without any error.
But in some other machine(local farm) with same data file following crash occur with fatal error at Geane application.

Is it related with the problem of symbolic link for fairsoft?
or do you have more simple guess for this problem?

Best wishes,
Donghee


-------------------------------------------------------------------
Calculating cross section tables, see gphysi.dat for more information

Cross section calculation concluded successfully
I- FairGeane::FairGeane: Geane is Initialized
[FATAL ] Initialization of Task Geane Application failed fatally
[FATAL ] We stop the execution of the process at this point.
[FATAL ] For later analysis we write a core dump to core_dump_31721
-------------------------------------------------------------------
Re: Meaning of Core dump due to Geane application at rec. part [message #11916 is a reply to message #11915] Fri, 27 May 2011 11:44 Go to previous messageGo to next message
StefanoSpataro is currently offline  StefanoSpataro
Messages: 2736
Registered: June 2005
Location: Torino
first-grade participant

From: *to.infn.it
Could you please be more explicit, telling us which macro have you used exactly, and at which stage this crashes? Have you seen some strange messages before?
Re: Meaning of Core dump due to Geane application at rec. part [message #11917 is a reply to message #11915] Fri, 27 May 2011 12:00 Go to previous messageGo to next message
donghee is currently offline  donghee
Messages: 385
Registered: January 2009
Location: Germnay
first-grade participant
From: *kph.uni-mainz.de
Hallo Stefano,

I'm testing the pandaroot may11 version with some modification(enc mode).

Few sim and digi file are produced with 1000 events at PBS system.
and then I'm going to reco part. I'm using quite standard code.
I have some crash due to geane application before initialization of pndlheHitmaker.

Quote:


-I- PndLheHitsMaker::Init ( this must to be appeared when reco macro works.)




Instead of sucessful I have now below error and go out of program.
Quote:


[FATAL ] Initialization of Task Geane Application failed fatally
[FATAL ] We stop the execution of the process at this point.
[FATAL ] For later analysis we write a core dump to core_dump_17535



But if I try same thing in my local machine, reco part doesn't show any error.

So, I assume that PANDAroot itself doesn't have any problem, since some files can also be run without such kind of error message.Only part of files are related with those problem.

If I know the meaning of above part, I can get some feeling where should be wrong in my farm machine.


cheers, donghee











Quote:


>./submit_test_submit_rec_99.sh
Processing /home/kang/GSI/pandaroot/macro/dvcs/run/enc_gendvcs_dvcs/My_enc_dvcs_rec .C( "test_submit/Panda_event_2_1_99", 100)...
Add file name : /home/kang/GSI/pandaroot/macro/dvcs/data/test_submit/Panda_event_2_1_99_ sim.root
Add file name : /home/kang/GSI/pandaroot/macro/dvcs/data/test_submit/Panda_event_2_1_99_ dig.root
FairGeane!!!
Info in (PndGeoHandling::Instance): Making a new instance using the framework.
Before Hit maker!!!
Before finder!!!
Before fitter!!!
Before kalman!!!
Before kalman!!!

[INFO ] The input consists out of the following trees and files:
[INFO ] - cbmsim
[INFO ] - /home/kang/GSI/pandaroot/macro/dvcs/data/test_submit/Panda_event_2_1_99_ sim.root
[INFO ] - FriendTree_1
[INFO ] - /home/kang/GSI/pandaroot/macro/dvcs/data/test_submit/Panda_event_2_1_99_ dig.root
[INFO ] Geometry was not found in the input file we will look in the friends if any!
[INFO ] The number of entries in chain is 1000

*************************************************************
initialisation for run id 600012391
*************************************************************
Info in <TGeoManager::TGeoManager>: Geometry Geometry, default geometry created
Warning in <TGeoManager::Init>: Deleting previous geometry: Geometry/default geometry
Info in <TGeoManager::CloseGeometry>: Geometry loaded from file...
Info in <TGeoManager::SetTopVolume>: Top volume is cave. Master volume is cave
Info in <TGeoManager::Voxelize>: Voxelizing...
Info in <TGeoNavigator::BuildCache>: --- Maximum geometry depth set to 100
Info in <TGeoManager::CloseGeometry>: 463899 nodes/ 1961 volume UID's in FAIR geometry
Info in <TGeoManager::CloseGeometry>: ----------------modeler ready----------------
Container FairBaseParSet initialized from ROOT file.
-I container name PndGeoSttPar

*************************************************************
initialisation for run id 600012391
*************************************************************
Container PndSensorNamePar initialized from ROOT file.
[ERROR ] init() PndGeoSttPar not initialized
Error in <FairRuntimeDb::initContainers()>: Error occured during initialization
PndFieldCreator::SetParm() 0xb8cd800

*************************************************************
initialisation for run id 600012391
*************************************************************
[ERROR ] init() PndGeoSttPar not initialized
Container PndMultiFieldPar initialized from ROOT file.
Error in <FairRuntimeDb::initContainers()>: Error occured during initialization
OBJ: PndTransPar PndTransPar Trans. Field parameter container
OBJ: PndDipole1Par PndDipole1Par Dipole Field parameter container
OBJ: PndDipole2Par PndDipole2Par Dipole Field parameter container
OBJ: PndSolenoid1Par PndSolenoid1Par Solenoid 1st region parameter container
OBJ: PndSolenoid2Par PndSolenoid2Par Solenoid 2nd region parameter container
OBJ: PndSolenoid3Par PndSolenoid3Par Solenoid 3rd region parameter container
OBJ: PndSolenoid4Par PndSolenoid4Par Solenoid 4th region parameter container
-I- PndFieldMap::Init: 2nd noenc
-I- PndFieldMap::Init: existed ENC map name = (noenc)
-I- PndFieldMap: Reading field map from ROOT file /home/kang/GSI/pandaroot/input/TransMap.1500.root
-I- PndFieldMap::Init: 2nd noenc
-I- PndFieldMap::Init: existed ENC map name = (noenc)
-I- PndFieldMap: Reading field map from ROOT file /home/kang/GSI/pandaroot/input/DipoleMap1.1500.root
-I- PndFieldMap::Init: 2nd noenc
-I- PndFieldMap::Init: existed ENC map name = (noenc)
-I- PndFieldMap: Reading field map from ROOT file /home/kang/GSI/pandaroot/input/DipoleMap2.1500.root
-I- PndFieldMap::Init: existed ENC map name = (SolenoidMap1_enc)
-I- PndFieldMap: Reading field map from ROOT file /home/kang/GSI/pandaroot/input/SolenoidMap1.root
-I- ENC Fieldmap: Reading field map from ROOT file /home/kang/GSI/pandaroot/input/SolenoidMap1_enc.root
-I- PndFieldMap::Init: existed ENC map name = (SolenoidMap2_enc)
-I- PndFieldMap: Reading field map from ROOT file /home/kang/GSI/pandaroot/input/SolenoidMap2.root
-I- ENC Fieldmap: Reading field map from ROOT file /home/kang/GSI/pandaroot/input/SolenoidMap2_enc.root
-I- PndFieldMap::Init: 2nd noenc
-I- PndFieldMap::Init: existed ENC map name = (noenc)
-I- PndFieldMap: Reading field map from ROOT file /home/kang/GSI/pandaroot/input/SolenoidMap3.root
-I- PndFieldMap::Init: 2nd noenc
-I- PndFieldMap::Init: existed ENC map name = (noenc)
-I- PndFieldMap: Reading field map from ROOT file /home/kang/GSI/pandaroot/input/SolenoidMap4.root
------------------------FairGeane::Init ()------------------------------
Loading Geant3 libraries ...
Loading Geant3 libraries ... finished

MZSTOR. ZEBRA table base TAB(0) in /MZCC/ at adr 554592759 210E69F7 HEX

MZSTOR. Initialize Store 0 in /GCBANK/
with Store/Table at absolute adrs 554615797 554592759
HEX 210EC3F5 210E69F7
HEX 560A 0
relative adrs 22026 0
with 1 Str. in 2 Links in 5300 Low words in 4999970 words.
This store has a fence of 16 words.

MZLOGL. Set Log Level 0 for store 0
1***** GEANT Version 3.21/11 Released on 100298
0***** Correction Cradle Version 0.1100

MZDIV. Initialize Division Constant in Store 0
NW/NWMAX= 20004000000, MODE/KIND= 1 2
Division 20 initialized.

MZLINK. Initialize Link Area /GCLINK/ for Store 0 NL/NS= 20 20

MZLINK. Initialize Link Area /GCSLNK/ for Store 0 NL/NS= 100 100
*** GCOMAD: cannot load common GCONSX
-I- G3Config: Geant3 with TGeo has been created for Geane.
-I- Geane.C: NOPRNT flag set to 1
-I- Geane.C: IERR flags are not printed. If you want to switch them on, please set fErtrio1->noprnt = 0 in Geane.C
Energy straggling area parameter from user set to: 0.999
======================================================
---- : TransMap.1500
----
---- Field type : Trans Map
----
---- Field map grid :
---- x = 0.000 to 240.0 cm, 61 grid points, dx = 4.000 cm
---- y = -240.0 to 240.0 cm, 241 grid points, dy = 2.000 cm
---- z = 283.0 to 343.0 cm, 41 grid points, dz = 1.500 cm

---- Field centre position: ( 0.000, 0.000, 0.000) cm
---- Field scaling factor: 1.000
----
---- Field at origin interaction point of primary vertex (0,0,30) is ( 0.000, 0.000, 0.000) kG
======================================================
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
======================================================
---- : DipoleMap1.1500
----
---- Field type : Dipole Map
----
---- Field map grid :
---- x = 0.000 to 158.0 cm, 80 grid points, dx = 2.000 cm
---- y = 0.000 to 51.00 cm, 52 grid points, dy = 1.000 cm
---- z = 342.0 to 602.0 cm, 131 grid points, dz = 2.000 cm

---- Field centre position: ( 0.000, 0.000, 0.000) cm
---- Field scaling factor: 1.000
----
---- Field at origin interaction point of primary vertex (0,0,30) is ( 0.000, 0.000, 0.000) kG
======================================================
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
======================================================
---- : DipoleMap2.1500
----
---- Field type : Dipole Map
----
---- Field map grid :
---- x = 0.000 to 170.0 cm, 35 grid points, dx = 5.000 cm
---- y = 0.000 to 60.00 cm, 31 grid points, dy = 2.000 cm
---- z = 560.0 to 660.0 cm, 26 grid points, dz = 4.000 cm

---- Field centre position: ( 0.000, 0.000, 0.000) cm
---- Field scaling factor: 1.000
----
---- Field at origin interaction point of primary vertex (0,0,30) is ( 0.000, 0.000, 0.000) kG
======================================================
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
======================================================
---- : SolenoidMap1
----
---- Field type : Soleniod Map
----
---- Field map grid :
---- x = 0.000 to 231.0 cm, 78 grid points, dx = 3.000 cm
---- y = 0.000 to 231.0 cm, 78 grid points, dy = 3.000 cm
---- z = -172.0 to -40.00 cm, 34 grid points, dz = 4.000 cm

---- Field centre position: ( 0.000, 0.000, 0.000) cm
---- Field scaling factor: 1.000
----
---- Field at origin interaction point of primary vertex (0,0,30) is ( 0.000, 0.000, 0.000) kG
---- Field at origin interaction point of primary vertex (0,0,90) is ( 0.000, 0.000, 0.000) kG
======================================================
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
======================================================
---- : SolenoidMap2
----
---- Field type : Soleniod Map
----
---- Field map grid :
---- x = 0.000 to 231.0 cm, 155 grid points, dx = 1.500 cm
---- y = 0.000 to 231.0 cm, 155 grid points, dy = 1.500 cm
---- z = -40.00 to 180.0 cm, 89 grid points, dz = 2.500 cm

---- Field centre position: ( 0.000, 0.000, 0.000) cm
---- Field scaling factor: 1.000
----
---- Field at origin interaction point of primary vertex (0,0,30) is ( 0.000, 0.000, 20.02) kG
---- Field at origin interaction point of primary vertex (0,0,90) is ( 0.000, 7.562, 19.99) kG
======================================================
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
======================================================
---- : SolenoidMap3
----
---- Field type : Soleniod Map
----
---- Field map grid :
---- x = 0.000 to 231.0 cm, 232 grid points, dx = 1.000 cm
---- y = 0.000 to 231.0 cm, 232 grid points, dy = 1.000 cm
---- z = 180.0 to 248.0 cm, 18 grid points, dz = 4.000 cm

---- Field centre position: ( 0.000, 0.000, 0.000) cm
---- Field scaling factor: 1.000
----
---- Field at origin interaction point of primary vertex (0,0,30) is ( 0.000, 0.000, 0.000) kG
---- Field at origin interaction point of primary vertex (0,0,90) is ( 0.000, 0.000, 0.000) kG
======================================================
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
======================================================
---- : SolenoidMap4
----
---- Field type : Soleniod Map
----
---- Field map grid :
---- x = 0.000 to 240.0 cm, 161 grid points, dx = 1.500 cm
---- y = 0.000 to 240.0 cm, 161 grid points, dy = 1.500 cm
---- z = 247.7 to 283.7 cm, 25 grid points, dz = 1.500 cm

---- Field centre position: ( 0.000, 0.000, 0.000) cm
---- Field scaling factor: 1.000
----
---- Field at origin interaction point of primary vertex (0,0,30) is ( 0.000, 0.000, 0.000) kG
---- Field at origin interaction point of primary vertex (0,0,90) is ( 0.000, 0.000, 0.000) kG
======================================================
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH

Calculating cross section tables, see gphysi.dat for more information
-I- PndLheHitsMaker::Init

Cross section calculation concluded successfully
I- FairGeane::FairGeane: Geane is Initialized
[FATAL ] Initialization of Task Geane Application failed fatally
[FATAL ] We stop the execution of the process at this point.
[FATAL ] For later analysis we write a core dump to core_dump_17535

Re: Meaning of Core dump due to Geane application at rec. part [message #11923 is a reply to message #11917] Fri, 27 May 2011 13:12 Go to previous messageGo to next message
Lia Lavezzi
Messages: 291
Registered: May 2007
Location: Torino
first-grade participant

From: *pv.infn.it
Hi,
I think there was a missng "return kSUCCESS" at the end of the Init, I just added it, please try updating the geane package and rerunning the macro.
Lia.
Re: Meaning of Core dump due to Geane application at rec. part [message #11925 is a reply to message #11923] Fri, 27 May 2011 13:46 Go to previous messageGo to next message
donghee is currently offline  donghee
Messages: 385
Registered: January 2009
Location: Germnay
first-grade participant
From: *kph.uni-mainz.de
Thanks Lia,

I was quite embarrassed.
But now after updating...it's fine!

But still this is funny feature in my understanding.

In local -> was all OK!
In submit machine -> was partly OK and partly wrong!

Is it no problem at stable version?
this is just a stupid question!

Donghee


Re: Meaning of Core dump due to Geane application at rec. part [message #11927 is a reply to message #11925] Fri, 27 May 2011 14:08 Go to previous message
Lia Lavezzi
Messages: 291
Registered: May 2007
Location: Torino
first-grade participant

From: *pv.infn.it
The problem was that a function which was supposed to return a InitStatus did not return anything, probably different machines handle this in a different way... I cannot answer the question why sometimes it works and sometimes it does not...
Lia.
Previous Topic: Mvd Hits bug still there
Next Topic: TPC digitization for more than 1000 events
Goto Forum:
  


Current Time: Wed Feb 01 00:36:39 CET 2023

Total time taken to generate the page: 0.00965 seconds