GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Tracking » Tracking efficiency release/jan14
Re: Tracking efficiency release/jan14 [message #15897 is a reply to message #15896] Mon, 24 February 2014 16:10 Go to previous messageGo to previous message
MartinJGaluska is currently offline  MartinJGaluska
Messages: 203
Registered: March 2010
Location: Germany
first-grade participant
From: *
Hello Klaus,

I have just noticed that you seem to have included the very forward part to calculate the average tracking efficencies. One reason that the average efficiency might be measured lower than with previous versions of PandaRoot is a change in the FTS ideal tracking which leads to lower efficencies in the theta range 5⁰ to 12⁰ or so.

I have changed the standard behavior of the FTS ideal tracking to make it behave more realistically by requiring a track found by the FTS tracking to have at least 5 FTS hits (compare to Previously, the FTS ideal tracker "found" all tracks that had at least 1 hit in the FTS.

As I said, from the FTS tracking point of view that behavior is more realisitic. However, currently there is only a tracking starting from STT + MVD and from FTS in the code. Both tracking algorithms find mostly distinct sets of tracks so that a merge is easily done. Hits from GEM are only added to tracks found by FTS and by STT + MVD, but there is no tracking starting from GEM being used in the current version of the code.

I was made aware of the drop in efficiency by Donghee in December and as a workaround implemented PndFtsTrackerIdeal::SetMinFtsHitsPerTrack(int); to set the number back to 1 to have an overall detector performance that is similar to before the changes in the FTS ideal tracking. However, I did not change the default value of requiring at least 5 FTS hits.

I have just changed the default value to 1 to avoid possible problems and confusion, especially when the simulation campaigns will be executed and new results will be compared with old ones. At this point I suggest to use the value of 5 for standalone performance studies of the FTS only.

Maybe that was one factor that your efficiencies look worse than before, but in your talk this morning it seemed that the efficencies for the barrel part 22⁰<theta<140⁰ were also affected (which is most probably not due to any FTS ideal tracking changes).

Kind regards,

[Updated on: Mon, 24 February 2014 16:17]

Report message to a moderator

Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: FairHit::SetPositionError
Next Topic: [FIXED] Bug in PndFts/SttMvdGemTrackingIdeal ?
Goto Forum:

Current Time: Sun May 26 02:30:44 CEST 2024

Total time taken to generate the page: 0.01001 seconds