Draft: Writing truth charge particle information for trackless
Description
Added an option to dump truth charged particles. This information could be useful for trackless b-tagging development together with the Barcode variable.
There is still some question to be address:
-
What selection should we apply on the truth charge particle (current: status==1,energy>=500 MeV) -
How many truth particle should we write? (5, 10, 20)
We should probably write multiple barcode information for each hit in the future.
Side note: With the "any" option here, I have a feeling ftagTPValid flag is outdated.
Review checklist:
-
CI Passing -
Comments addressed -
Source branch is up to date with target
Merge request reports
Activity
144 146 "particles": "promptLepton" 145 147 }, 146 148 "decorate_summary": true 149 }, 150 { 151 "association": { 152 "file": "fragments/baseline-truth-kinematics.json", 153 "particles": "stableCharged" 154 }, 155 "association_name": "charged_particles", 156 "output": { 157 "n_to_save": 20, changed this line in version 2 of the diff
-
Looks pretty good! Have you tried adding this information to the trigger config too? I guess @backes et al are using https://gitlab.cern.ch/atlas-flavor-tagging-tools/training-dataset-dumper/-/blob/main/configs/trigger_hits.json?ref_type=heads?
I was trying to download a file from
valid1.601229.PhPy8EG_A14_ttbar_hdamp258p75_SingleLep.recon.AOD.e8514_e8528_s4111_s4114_r14634to test it out locally but it's giving me this errorDirect download from tape is prohibited. Please request a transfer to a non-tape endpoint.@backes, am I looking at the right files? do I need special permission for them?
Yes these are the correct files, but I am also not able to download them anymore... I also don't know what is going on there. I am quickly giving you access to a copy that I made some time ago on eos so you can try it locally: /eos/user/b/backes/QT/AOD
Let me know if you cannot access it!
Moving AODs to tape is pretty standard (although I don't have any documentation that says just how it works). We're not generally supposed to access AODs for long, especially ones from validation campaigns.
My guess is that this was produced in some trigger validation and as such they didn't keep it around forever. We can always request more samples, of course, if they are needed, or move files off of tape.
