[PWGJE] Systematic flag setup for associates and efficiency#16302
[PWGJE] Systematic flag setup for associates and efficiency#16302joachimckh wants to merge 2 commits into
Conversation
|
O2 linter results: ❌ 0 errors, |
joachimckh
requested review from
alibuild,
fjonasALICE,
maoyx,
mfasDa,
mhemmer-cern,
nzardosh and
raymondEhlers
as code owners
| @@ -949,25 +1115,25 @@ struct JetSpectraEseTask { | |||
| PROCESS_SWITCH(JetSpectraEseTask, processMCGenTrack, "jet MC process: Generated track", false); | |||
| void processMCRecoTrack(soa::Filtered<soa::Join<aod::JetMcCollisions, aod::BkgChargedMcRhos>>::iterator const& mcCollision, | |||
| soa::SmallGroups<aod::JetCollisionsMCD> const& collisions, | |||
| aod::JetTracksMCD const& tracks, | |||
| aod::JetParticles const&) | |||
| soa::Join<aod::JetTracksMCD, aod::JTrackPIs> const& tracks, | |||
There was a problem hiding this comment.
it would be good to put the new stuff in a new process function so you still have a process function that can run on derived data
There was a problem hiding this comment.
@nzardosh I see, but then I cannot apply this additional trackselection right?
There was a problem hiding this comment.
Is this a study for the efficiencies or is it actually implementing a new track selection? Are you planning on replacing globalTracks?
There was a problem hiding this comment.
@nzardosh It should have all the default cuts from globalTracks. It is so I can tighten them for systematic effects on the associated tracks. For the efficiency I need the corresponding selection, so they match the data
| case 0: | ||
| break; | ||
| case 1: | ||
| systCuts.vertexZCut = 9.0f; | ||
| break; | ||
| case 2: | ||
| systCuts.vertexZCut = 8.0f; | ||
| break; |
There was a problem hiding this comment.
What do these numbers mean?
There was a problem hiding this comment.
Explained in the configurable. But self consistent number used offline aswell.
There was a problem hiding this comment.
It would be more explanatory if these were enumerated and referenced in the documentation of the configurable.
3 participants
No description provided.