Difference: EsdProduction (1 vs. 3)

Revision 32005-01-18 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="AthenaStuff"
Added:
>
>

Troubles in 9.0.3

When using iPatRec: lots of warnings like:
TrackCollectionCnv::PoolToD...   INFO
TrackCollectionCnv::PoolToD...   INFO No TrackParameter & no RIO_OnTrack on TrackStateOnSurface! Malformed Track?Dumping TSoS :TrackStateOnSurface, of type : Unknown
TrackCollectionCnv::PoolToD...   INFO    NO FitQualityOnSurfaces.
TrackCollectionCnv::PoolToD...   INFO    NO TrackParameters.
TrackCollectionCnv::PoolToD...   INFO    NO RIO_OnTracks.
TrackCollectionCnv::PoolToD...   INFO    HAS ScatteringAngle(s).
TrackCollectionCnv::PoolToD...   INFO ScatteringAngleOnSurface:
         deltaPhi        : -0.00206092
         deltaTheta      : 0.000285324
         sigmaDeltaPhi   : 4.7499e-06
         sigmaDeltaTheta : 2.48353e-06
This is due to troubles in the converters. When a track goes through a surface, iPat only stores the scattering angle but not the changed trackparameters. This has only implications if you want to refit the tracks. Fitting from scratch is fine of course.
 

To do's for 9.0.2

DONE InDetPrepRawData needs to be adjusted to the new TruthEvent ... Maria will do.

Revision 22004-11-29 - AndreasWildauer

Line: 1 to 1
 
META TOPICPARENT name="AthenaStuff"

To do's for 9.0.2

DONE
Line: 10 to 10
 
  1. GEN_EVENT
  2. TruthEvent

Runtime Errors and Warnings with 9.0.1

Changed:
<
<
OPEN
>
>
FIXED
 
TrackCollectionCnv::DataObj...WARNING TrackParameter has no associated surface. Malformed track.
This one only shows up when only xKalman is used. It does not show up when iPat is on as well and also iPatTracks are used as the tracks.
Added:
>
>
Apparently this fixes it in 9.0.2:
InnerDetector/InDetRecTools/InDetLegacyCnvTools/InDetLegacyCnvTools-00-07-00
 
Changed:
<
<
OPEN
>
>
PARTLY FIXED In 9.0.2 muons dont crash anymore with this fix (will be in 9.0.3):
cmt co -r MuonAlgs-00-01-06 PhysicsAnalysis/MuonID/MuonAlgs
The bug was:
 However, when iPatRec is on there are other warnings and errors, e,g,:
ToolSvc.Trk::TrackSummaryTool WARNING Null pointer to TRTDriftCircle found on Track (author = 7). This should never happen!
Line: 30 to 40
 ToolSvc.Trk::MooreToTrackTool WARNING No prep raw data pointer found for identifier [7.2.-4.3.2.1.1.1.1.1.56] ToolSvc.Trk::MooreToTrackTool ERROR HitOnTrack of type -23 has no RIO and so no RIO_OnTrack can be created
Changed:
<
<
aso. aso. ...
>
>
To these last three Ketevi says:

This, I know where it comes from and it will go away when we start using the
RPC clusters in MOORE - one should not mind these unless one refitting
tracks.
 
FIXED When iPat is used many lines of these warnings appear:
Line: 45 to 61
  "Trk::RIO_OnTrack" part will be written
Changed:
<
<
This on is FIXED, you need to load the dictionary:
>
>
This one is FIXED in 9.0.2 (in 9.0.1 you need to load the dictionary):
 
include( "MuonRIOOnTrack/MuonRIOOnTrackDict_joboptions.py" )

Revision 12004-11-17 - AndreasWildauer

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="AthenaStuff"

To do's for 9.0.2

DONE InDetPrepRawData needs to be adjusted to the new TruthEvent ... Maria will do. TrackTruthMaker and TrackParticleTruthMaker as well, but only the input name of the McEventCollection from GEN_EVENT and G4Truth to TruthEvent ... probably possible via jobOptions.

McEventCollections after Digitization with 9.0.0, checking output of ESD production with 9.0.1:

  1. GEN_EVENT
  2. TruthEvent

Runtime Errors and Warnings with 9.0.1

OPEN
TrackCollectionCnv::DataObj...WARNING TrackParameter has no associated surface. Malformed track.
This one only shows up when only xKalman is used. It does not show up when iPat is on as well and also iPatTracks are used as the tracks.


OPEN However, when iPatRec is on there are other warnings and errors, e,g,:
ToolSvc.Trk::TrackSummaryTool WARNING Null pointer to TRTDriftCircle found on Track (author = 7). This should never happen!

There are many muon errors and warnings as well ... :

ToolSvc.Trk::MooreToTrackTool   ERROR no brem, and scatterer parameter is out of bounds!!!!
ToolSvc.Trk::MooreToTrackTool WARNING No prep raw data pointer found for identifier [7.2.-4.3.2.1.1.1.1.1.56]
ToolSvc.Trk::MooreToTrackTool   ERROR  HitOnTrack of type -23 has no RIO and so no RIO_OnTrack can be created
aso. aso. ...
FIXED When iPat is used many lines of these warnings appear:
Warning in <TBuffer::WriteObjectAny>: since Trk::RIO_OnTrack had no
public constructor
      which can be called without argument, objects of this class
      can not be read with the current library. You would need to
      add a default constructor before attempting to read it.
Warning in <TStreamerInfo::WriteBuffer>: The actual class of
  Trk::TrackStateOnSurface::m_rioOnTrack is not available. Only the
  "Trk::RIO_OnTrack" part will be written

This on is FIXED, you need to load the dictionary:

include( "MuonRIOOnTrack/MuonRIOOnTrackDict_joboptions.py" )


FIXED for 9.0.2. There were two bugs: one in the digitization and one in the ESD production with 9.0.1 use:
LArCalorimeter/LArCellRec/LArCellRec-02-09-34
LArCalorimeter/LArROD/LArROD-02-08-02

The bug was:

LArCellBuilderFromLArRawChannelTool::addCell ERROR inconsistent caloDDE 180691caloDDE2 180705
After that athena is stopped with
ToolSvc.LArCellBuilderLAr     WARNING fastBuildCellCont : hole detected!
In the package LArCellRec on can see:
if (*itrCell==0){
  MsgStream log (msgSvc(),name());
  log << MSG::WARNING << "fastBuildCellCont : hole detected!" << endreq;
  return StatusCode::FAILURE;
}
David R. has a look at it.

-> seems to be more serious error ...

This should be fixed in 9.0.2. For earlier versions use:

cmt co -r LArCellRec-02-09-32 LArCalorimeter/LArCellRec

For files simulated with final layout the error remains ... will check again.


Set DENYTOPICCHANGE = EdwardMoyse

-- DerSchrecklicheSven - 17 Nov 2004

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback