Opened 8 years ago
Closed 3 years ago
#1001 closed Bug (fixed)
Segfault with LHCb card on Delphes 3.3.2
Reported by: | James Keaveney | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Delphes code | Version: | Delphes 3 |
Keywords: | Cc: |
Description
Hi,
I'm attempting to run Delphes with the preliminary LHCb card over a STDHep file I produced with MG5_aMC@NLO. However, I get a segfault. I assumed that there was something wrong with my STDHep file
so I tried the standard example -
wget http://cp3.irmp.ucl.ac.be/downloads/pp_bb.hep.gz
gunzip pp_bb.hep.gz
./DelphesSTDHEP cards/delphes_card_LHCb.tcl delphes_output.root pp_bb.hep
but I still get the error:
Jamess-MacBook-Pro:Delphes-3.3.2 keaveney$ ./DelphesSTDHEP cards/delphes_card_LHCb.tcl d.root pp_bb.hep
INFO: adding module PhotonConversions PhotonConversions
INFO: adding module ParticlePropagator ParticlePropagator
INFO: adding module MomentumSmearing ChargedHadronMomentumSmearing
INFO: adding module MomentumSmearing ElectronMomentumSmearing
INFO: adding module MomentumSmearing MuonMomentumSmearing
INFO: adding module Merger TrackMerger
INFO: adding module ImpactParameterSmearing ImpactParameterSmearing
INFO: adding module IdentificationMap IdentificationMap
INFO: adding module SimpleCalorimeter ECal
INFO: adding module SimpleCalorimeter HCal
INFO: adding module TreeWriter TreeWriter
INFO: initializing module Delphes
INFO: initializing module PhotonConversions
* Break * segmentation violation
Generating stack trace...
0x0000000102dad0dd in ExRootTask::Exec(char const*) (in DelphesSTDHEP) + 301
0x00000001030ec4e8 in TTask::ExecuteTasks(char const*) (in libCore.so) + 424
0x00000001030ec2d6 in TTask::ExecuteTask(char const*) (in libCore.so) + 454
0x0000000102ef6e64 in main (in DelphesSTDHEP) + 1620
0x00007fff92d335ad in start (in libdyld.dylib) + 1
0x0000000000000004 in <unknown function>
I thought I was missing something in my OSX environment but what is surprising is that if I change to the CMS card, I have no problems and a Delphes root file is successfully created with meaningful information within.
Any help much appreciated,
James.
Change History (2)
comment:1 by , 8 years ago
comment:2 by , 3 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Hi James,
thanks for spotting this, we introduced a bug when adapting the TF1 formula to comply with newer ROOT versions. Should be fixed now. You can fetch the HEAD, or wait for a new version to come out (very soon..)
Michele