-
Notifications
You must be signed in to change notification settings - Fork 100
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
Abnormal material budget of DDCAD-imported files #1134
Comments
To make sure the baseline works as expected, what do you get for the beampipe of https://github.com/key4hep/k4geo/tree/master/FCCee/compact/FCCee_o2_v02 ? |
Hi André For my vertex detector and beampipe it works fine, I just also checked for the CLD version you linked: Cheers, |
Concerning the material budget with ddsim: You have a problem there which is noit dd4hep related:
|
We cannot really support problems embedded inside lcgeo, Gaudi etc. It would take way off more time to Is there no way to strip down the problem to only use dd4hep, ROOT and Geant4? |
Ah sorry, yep, I forgot to add the ./ in front of the xml file name, but still it doesn't work for me (seg fault), here's the updated log from |
For the ddsim material check I understand, but for the other way of estimating the material budget (cd FCCee/compact/IDEA/IDEA_o1_v01/, sh scripts/check_material_budget.sh), I'm using Thank you, |
-- Which is the xml file you use to feed the material scans? |
The xml file I use is FCCee_IDEA_o1_v01.xml, which then includes Vertex_IDEA_o1_v01.xml.
I think for reproducing the error, you could put the STL shape into any working file of a detector (e.g FCCee_o2_v02.xml, removing the other detector parts) with
using the Thank you for your time, |
Hi @armin-ilg Can you just set |
Hi @andresailer Ok, I did the following:
The output again is a When commenting out the DDCAD part, it runs without issue. Thank you for your time, |
Thanks for trying this out! Does the simulation always fail with the CAD geometry or does it only fail for geantinos or for |
If I summarize:
But it is not understood why.... |
It fails in the same way with |
I tried to reproduce the results of Armin with his file: |
@armin-ilg Armin, I do not exactly know what you are doing wrong, but something is very fishy in your setup. I did all stuff like material scan, overlap checks etc. using your STL file without problems. I do not see any problems. |
Thank you very much for your help @MarkusFrankATcernch and @andresailer. It is indeed an issue of my local setup. I must have done something wrong in the installation of my local k4geo repo.
Overlap checks work now. Thank you very much for your support, |
and then running material budget check with
Input: Files in
FCCee/compact/IDEA/IDEA_o1_v01/
of my local k4Geo/lcgeo installation, and this STL file:Assieme supporti carbonio_1.stl.zip
Output: full build build.log and log check_material_budget.log
Goal: I'm trying to import shapes via DDCAD and check for overlaps with the rest of the detector (see also How to check for overlaps when using DDCAD #1121) and to measure the material budget (this report). The material budget distribution however doesn't make sense at all. The material depth is absurdely large (see
depth.pdf) and dominates all other detector components. This results in a very large material budgetr as welli (x0.pdf).
What is strange is that also at eta=0 there is a non-zero material length, although there should clearly be nothing there:
The stl shape should be positioned correctly however (seen in teveDisplay).
I also tried to check the material budget with ddsim:
which however results in a seg fault (ddsim_material_budget.log).
I also tried to use the example STL file from examples/DDCAD/models/STL/IR_assy_all_colour.stl instead of my shape, and also the material budget check in ddsim doesn't run and the material depth is absurdely large (1800 cm, see
depth_IR.pdf).
Am I doing something wrong? I tried putting the DDCAD import inside of a box using
DD4hep_SingleShape
and tried using CAD_Assembly, CAD_MultiVolume and CAD_Shape, but to no avail.Thank you for your help!
The text was updated successfully, but these errors were encountered: