-
Notifications
You must be signed in to change notification settings - Fork 60
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
Adding IDEA_o1_v02 and its vertex detector #273
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @armin-ilg ! Thanks! Could you
- move everything from
FCCee/compact/FCCee_IDEA_o1_v01/
toFCCee/compact/IDEA/IDEA_o1_v01
- Add a
README.md
underdetector/tracker
explaining briefly what the new detector builders do together with a link to a recent reference (a talk is ok) describing the detector we are trying to model? You can just add two "entries" in the README to describe the two new builders, more will come to describe the other ones.
Can you add a test for the newly introduced detectors, as in https://github.com/key4hep/k4geo/blob/master/lcgeoTests/CMakeLists.txt#L67 ? |
Hi Armin, I did not anticipate that we were going to have scripts and utilities here, but it is perfectly ok. I would then just propose a modification in the folder organization because the |
.swp files are deleted. |
It's better to continue here where there is already discussion. For flattening you can always force push to your branch and then not use merge and use rebase. At the end the commits will be squashed (if the squash button is pressed, which should) and then it doesn't really matter if the history is linear or not since it will just be another commit on top of the current one |
Done |
…nts, ability to tilt whole modules.
…ake good assembly structure
…im and fccRec_e4h with vertex digitisation, but no vertices reco'd yet, bad hierarchy again
<detectors> | ||
<detector id="0" name="VTXIBSupport" type="DD4hep_TestShape_Creator"> | ||
<check> | ||
<shape type="CAD_MultiVolume" ref="${K4GEO}/share/k4geo/FCCee/IDEA/compact/IDEA_o1_v01/VertexSupport_o1_v01.obj" unit="mm"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are saying, you cannot use a relative path here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, just using ref="VertexSupport_o1_v01.obj" will only work if it's run inside of the FCCee/IDEA/compact/IDEA_o1_v01 folder. I can open a ticket in DD4hep for that if you think this should be fixed (would be useful I think)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please open an issue. We must not depend on running in the same folder or having the full path.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done: AIDASoft/DD4hep#1166
…, change name when they differ)
… The test will only run once the IDEA folder is in the nightly Key4hep software stack
…lume names can be assigned. Furthermore changed DetElements in barrel constructor so that they can be properly accessed in k4RecTracker
… This is applied in the IDEA vertex detector. Other than this, also the width of the sensor support in the vertex barrel was corrected to be only 4.4 mm wide (instead of 8.8)
…, only end-cap missing
…ponents. Multiple components can be added per stave and the name will be used to name the corresponding assembly. Furthermore fixed the sensitive/periphery regions in VTXIB layers 2 and 3 to be correct
This is going to conflict with #282 for the IDEA_o1_v01 |
|
Hi. So I have done the last additions to the IDEA vertex. It's now also possible to do some very simple (and by far not final) digitisation using k4RecTracker (my fork is here) without needing to use the k4MarlinWrapper. The IDEA vertex detector is now quite accurately described. In comparison to the MDI note, also the end-of-stave/ladder structures have been implemented. Only the large holder structure for the disks is missing. Anything else that needs to be changed @andresailer ? |
What Brieuc posted above again. |
Also check yourself why the tests are failing please. |
…pport as it will fail the test, since the CAD file cannot be found. After the IDEA detector is in a nightly release, then the CAD file will be found and we can include these lines in the xml again
Done. I commented the vertex inner barrel support for the moment, as this would prevent the test from passing.
|
@andresailer : So if I understand Brieuc's comment correctly
this means that we can merge this PR now and then the other open PR will build on this IDEA version, right? So we can go ahead and merge this PR from your side @BrieucF ? |
Hi Armin, sorry I was not clear. No, we should first rename the folder |
Ah, sorry for the confusion. Changed now! |
BEGINRELEASENOTES
ENDRELEASENOTES
To do's still:
Longer term: