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

Alignment updates #908

Merged
merged 16 commits into from
May 10, 2022
Merged

Alignment updates #908

merged 16 commits into from
May 10, 2022

Conversation

pbutti
Copy link
Contributor

@pbutti pbutti commented Apr 19, 2022

No description provided.

@pbutti pbutti changed the title Alignment updates - WIP Alignment updates Apr 19, 2022
@pbutti pbutti changed the title Alignment updates Alignment updates - WIP Apr 19, 2022
@pbutti
Copy link
Contributor Author

pbutti commented Apr 19, 2022

This PR modifies only files related to alignment and monitoring, with no impact on reconstruction chain.

  • I've added the support to pass the Energy from calorimeter clusters as momentum constraint, so the constraint can now be applied to all tracks and not only to FEEs.
  • I've added the support to form a combined trajectory to align and at the same time reconstruct particle vertices . This implementation doesn't break anything as it is not used.
  • I've made minor modifications to the monitoring plots for alignment.

@pbutti pbutti changed the title Alignment updates - WIP Alignment updates Apr 19, 2022
Copy link
Collaborator

@cbravo135 cbravo135 left a comment

Choose a reason for hiding this comment

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

Thank you PF for making some nice additions to the alignment monitoring.

@@ -105,12 +105,13 @@ protected void process(EventHeader event) {
//accumulatedTracks.add(track);
accumulatedBTracks.add(new BilliorTrack(track));

if (track.getTrackStates().get(0).getTanLambda() > 0) {
//Avoid tracks too close to the beamline to have a more reliable result on z from single volumes
if (track.getTrackStates().get(0).getTanLambda() > 0.035) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

In general, I think these configuration parameters should be put into a steering file and not hard coded. Hard coding selections should be avoided in general.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah. But this code is only for monitoring.

Copy link
Contributor

@bloodyyugo bloodyyugo left a comment

Choose a reason for hiding this comment

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

This seems fine

@pbutti
Copy link
Contributor Author

pbutti commented May 6, 2022

I have another iteration with the configurable selections. We should develop a trackSelector tool to keep those selections in a single place. At the moment they are copied everywhere multiple times.

@pbutti pbutti merged commit 097fb88 into master May 10, 2022
This pull request was closed.
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.

3 participants