Skip to content
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

refactor!: Template algorithms on track container frontend TrackContainer #3193

Conversation

andiwand
Copy link
Contributor

@andiwand andiwand commented May 16, 2024

Instead of pulling all the track container template parameters into the algorithms we can template on the TrackContainer and get the details from there.

blocked by

@andiwand andiwand added the 🛑 blocked This item is blocked by another item label May 16, 2024
@andiwand andiwand added this to the v36.0.0 milestone May 16, 2024
@andiwand andiwand force-pushed the refactor-template-on-track-container-fontend branch 2 times, most recently from 50f05ac to 7bee8eb Compare May 16, 2024 12:53
Copy link

github-actions bot commented May 16, 2024

📊: Physics performance monitoring for 1bbfb64

Full contents

physmon summary

Copy link
Member

@paulgessinger paulgessinger left a comment

Choose a reason for hiding this comment

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

We can do this in principle, of course.

The main reason I didn't, was to lock down the template parameters a bit, as blanket "accept everything" parameters can be a bit confusing sometimes.

I suppose this can be alleviated by using a concept? There are already track container backend and multitrajectory backend concepts, so it should be fairly simple to assemble a combined track container concept. We could then use that to constrain the template types in these cases.

@andiwand
Copy link
Contributor Author

andiwand commented Jun 5, 2024

My primary reason was to break the template param dependency chain a bit. For example the fitters / finder / ambi res should not have to carry through the holder type and the mutability flag.

Concepts would be great here I think! In principle the user should be able to create their own high level track container and proxy objects. Not sure if this is useful but I think the decoupling would be nice.

I think this one is actually not critical at all for v36 btw. I am happy to push this a bit further if we cannot make it until we want to cut the major release.

@github-actions github-actions bot added the Stale label Jul 5, 2024
@andiwand andiwand modified the milestones: v36.0.0, next Jul 10, 2024
@github-actions github-actions bot removed the Stale label Jul 10, 2024
@andiwand andiwand force-pushed the refactor-template-on-track-container-fontend branch from 0c47ad0 to 3c050df Compare July 23, 2024 08:34
@andiwand andiwand removed the 🛑 blocked This item is blocked by another item label Jul 23, 2024
@andiwand andiwand changed the title refactor!: Template on track container frontend TrackContainer refactor!: Template algorithms on track container frontend TrackContainer Jul 23, 2024
This was referenced Aug 29, 2024
@andiwand andiwand removed the 🚧 WIP Work-in-progress label Aug 30, 2024
@andiwand andiwand modified the milestones: v37.0.0, next Sep 3, 2024
@andiwand andiwand marked this pull request as ready for review September 3, 2024 06:20
@acts-project-service acts-project-service added the Fails Athena tests This PR causes a failure in the Athena tests label Sep 3, 2024
@andiwand andiwand removed the Fails Athena tests This PR causes a failure in the Athena tests label Sep 3, 2024
Copy link
Member

@paulgessinger paulgessinger left a comment

Choose a reason for hiding this comment

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

Let's go

Copy link

sonarqubecloud bot commented Sep 4, 2024

@kodiakhq kodiakhq bot merged commit 1e855a2 into acts-project:main Sep 4, 2024
42 checks passed
@github-actions github-actions bot removed the automerge label Sep 4, 2024
@andiwand andiwand deleted the refactor-template-on-track-container-fontend branch September 5, 2024 05:27
@paulgessinger paulgessinger modified the milestones: next, v37.0.0 Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants