Skip to content

[WIP] Acts Geo Gen3 DD4hep conversion#36

Open
tmadlener wants to merge 55 commits intokey4hep:mainfrom
tmadlener:dd4hep-acts-gen3-geo
Open

[WIP] Acts Geo Gen3 DD4hep conversion#36
tmadlener wants to merge 55 commits intokey4hep:mainfrom
tmadlener:dd4hep-acts-gen3-geo

Conversation

@tmadlener
Copy link
Member

@tmadlener tmadlener commented Dec 4, 2025

BEGINRELEASENOTES

  • Thank you for writing the text to appear in the release notes. It will show up
    exactly as it appears between the two bold lines
  • ...

ENDRELEASENOTES

This is a work in progress with the main purpose of being able to share ongoing efforts. So far the efforts focus on getting (parts) of the MAIA_v0 geometry conversion tested and evaluated against upstream work happening at currently living on https://github.com/paulgessinger/acts/tree/feat/dd4hep-gen3

For the MAIA_v0 geometry, this needs key4hep/k4geo#549


/// A simple struct to hold configuration to build a tracker that is nested
/// such that a simple stacking in z does not work.
struct NestedInnerTrackerSpec {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think something like this should exist at the library level?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not entirely sure. I don't see a way to make this general enough to be useful without inventing another semi DSL just for this purpose. This specific thing works for our case, where there is one (or a few) endcap layers that protrude into the cylinder formed by the outermost barrel layer(s). However, we currently only have this nesting once (in a subdetector). As soon as we have, e.g. two different levels of protrusion it no longer works. The way out would be to simply call this thing twice with different configurations, but then one would have to potentially add more config, e.g. to allow for "empty" layers.

Given that it's fairly straight forward to build this on our end on top of the proposed API, I would keep it in "userland" and see if it's common enough there to merit upstreaming later.

@tmadlener tmadlener force-pushed the dd4hep-acts-gen3-geo branch from 5933a8a to 8197a6e Compare March 10, 2026 14:07
@tmadlener
Copy link
Member Author

With the changes in paulgessinger/acts#33 we now also support planar geometries, like LUXE

tmadlener and others added 29 commits March 10, 2026 19:52
Either absorbed by other services or not part of the context of this PR
@tmadlener tmadlener force-pushed the dd4hep-acts-gen3-geo branch from 8197a6e to 17edab4 Compare March 10, 2026 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants