-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tau decay products are produced at the origin with ddsim #1256
Comments
Is that from your pdf the case?
This doesn't work. Please use the hepmc3 reader. |
Is it ok to mix and match hepmc versions? For generation, the installation log in madgraph was hepmc2.06.09. |
Yes. HepMC3 has a hepmc2-ascii reader. The HepMC2 reader that is implement in DD4hep doesn't work for secondary vertices. |
Ok I see thank you. The reason we tried the hepmc2 reader is because using the hepmc3 reader, the taus were being produced at the origin. There is a screenshot in the presentation showing the taus coming from staus that decay far away from the origin but the taus are produced at the origin. We also do not see any stau or tau hits in simhit collections. Do you have any suggestions? |
This looks OK? The staus decay where the tau + Neutralino (?) start
I used your 1000GeV_30mm.tbl file and set the GeneratorStatus of the staus from 22 to 2. ddsim doesn't pass anything with generator status > 2 to Geant4. What is important here also is the "SimStatus" which shows that the staus were actually simulated and decayed. And I also get hits from the Staus, note the PDG of the MCParticle
I used ddsim from LCG_105b , so DD4hep version 1.27.02 |
This looks great, thank you for trying it out. How did you change the GeneratorStatus of the staus? |
I used emacs to replace the 22 with 2 in the first event.
This issue with the generator status showed up before, maybe we should add some treatment to allow this in ddsim. |
I just had a couple more questions:
|
|
Also @Lrozzy , can you think of something to improve the documentation for this option (or other options) that would have made you realise this is what you need to set if it had already existed? |
Thanks Andre. Unfortunately I think the status code 22 was only one of a few issues. Some of our staus promptly emit a photon and then continue on treated as different particles with different status codes:
In this case the status of the staus that continue on are 51 and 52. These are defined as:
When we just changed the status code 22 --> 2, we realised that we also have taus that come from staus but, again, promptly emit a photon and continue on, treated as different particles with different status codes:
In this case you can see the tau that emits a photon has status code 23, and the one that continues has status code 2, but we do not see the tau in simhits. Also, somehow the tau that promptly emits a photon emits it at the origin despite being very far away from the origin, but this is not a problem for the status 2 tau that continues on. |
HI @Lrozzy |
Sure, this was event number 1, index 1. So the 2nd event of the 1000_0.1.hepmc file |
Seems to work for me with event 1 |
Ok great, I'll try and do the same! |
If the applied fixes are not enough, please let us know. (Also let us know if everything works). |
Just a quick update - we got ddsim working and the output seems ok (stau and tau hits present) but when I try to run digi it fails, using both the old stack and the new. I've attached the outputs for both. Please let me know if you have any suggestions or want more information. |
Hi @Lrozzy The digi issue however is outside the scope for the DD4hep repository. Just some comments:
File not found? Can't help you there. New:
Points towards a mixture of environments: same packages with different versions... As I don't know who or how you build the stack, I can't tell you where would be a better place to raise this issue. Cheers, |
Thanks @andresailer. The file not found is strange because when I try to run digi on a sim file produced from the old stack (dd4hep 1.25) it works fine, and there shouldn't be any permission issues. As for the new, I built dd4hep and lcgeo, and then I sourced first the cvmfs/muoncollider, then my dd4hep and my lcgeo. This was how I made the working sim file.
|
This is exactly what I mean with mixing environments. It works for simulation, because you are just using DD4hep, but your Digi was build against an older DD4hep version, so you start mixing libraries. Please open a new issue with all the details that would allow someone to reproduce what your are doing. |
Check duplicate issues.
Goal
Wanted to run an LLPs sensitivity study using susy-taus. Ran simulation over a healthy .hepmc file. The susy-taus decay to taus, but the tau decay products are being produced at the origin. Attached is a presentation showing more details/examples.
ddsim bug.pdf
Operating System and Version
Alma Linux 9
compiler
GCC 11
ROOT Version
6.28/02
DD4hep Version
1.25.1
Reproducer
I ran ddsim over the .hepmc file with the attached configurations and particle.tbl file.
The code I used to run ddsim is available at (specifically sim_Hbb/multi_sim.py):
https://github.com/kdp-lab/Leo-LLPs-Code/tree/main
The particle.tbl, .hepmc, and steering (.py) files are available at:
https://drive.google.com/drive/folders/1MjvZVrmsot-WBf74FLbVYZfWptAe-ZAX?usp=drive_link
Additional context
No response
The text was updated successfully, but these errors were encountered: