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: physmon: *almost* same settings for GX2F and KF #3248

Merged
merged 20 commits into from
Jun 7, 2024

Conversation

AJPfleger
Copy link
Contributor

@AJPfleger AJPfleger commented Jun 5, 2024

Have almost same settings for GX2F and KF makes it easier to understand in the physmon output and check if our results are good.

Why almost?

Had also 3 FPEs which fixed here, but did not choose this approach:

This issue only occurred for 2.5 < |eta| < 3.0. To get better physmon until the problem is fixed (maybe in a later stage of the GX2F-development), the eta-range is reduced. The full eta-range could be used after solving:

@AJPfleger AJPfleger added this to the next milestone Jun 5, 2024
@github-actions github-actions bot added the Component - Examples Affects the Examples module label Jun 5, 2024
@github-actions github-actions bot added the Infrastructure Changes to build tools, continous integration, ... label Jun 5, 2024
Copy link

codecov bot commented Jun 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.65%. Comparing base (c0acef7) to head (87f83b1).
Report is 275 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3248   +/-   ##
=======================================
  Coverage   47.65%   47.65%           
=======================================
  Files         509      509           
  Lines       29423    29423           
  Branches    14132    14132           
=======================================
  Hits        14023    14023           
  Misses       5285     5285           
  Partials    10115    10115           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@github-actions github-actions bot added Component - Core Affects the Core module Track Fitting labels Jun 5, 2024
@AJPfleger AJPfleger added the 🛑 blocked This item is blocked by another item label Jun 5, 2024
@github-actions github-actions bot removed the Component - Core Affects the Core module label Jun 7, 2024
@AJPfleger AJPfleger removed 🚧 WIP Work-in-progress 🛑 blocked This item is blocked by another item labels Jun 7, 2024
@AJPfleger AJPfleger changed the title refactor: physmon: same settings for gx2f and kalman refactor: physmon: *almost* same settings for GX2F and KF Jun 7, 2024
@kodiakhq kodiakhq bot merged commit c2ee464 into acts-project:main Jun 7, 2024
51 checks passed
@github-actions github-actions bot removed the automerge label Jun 7, 2024
@AJPfleger AJPfleger deleted the physmon-gx2f-kalman branch June 7, 2024 20:29
@acts-project-service acts-project-service added the Fails Athena tests This PR causes a failure in the Athena tests label Jun 7, 2024
kodiakhq bot pushed a commit that referenced this pull request Jun 8, 2024
Use a temporary track container for the propagation during the updates, to ensure the original track container stays untouched.

Until now, we were clearing the original container with `trackContainer.clear()`. This is fine, until we have more tracks in our container.

blocked by:
- #3248

edit:
After #3248 the physmon does not change, since we switched from 2 particles/event to 1. Therefore, we also have only one track/container.

Before we could see the effect stronger, like in the graphic. However, I don't see a reason to change physmon to catch this.
![image](https://github.com/acts-project/acts/assets/70842573/55eb47b2-e268-4a01-a618-8379d36bae49)
kodiakhq bot pushed a commit that referenced this pull request Jun 11, 2024
This PR allows to fully support measurements with non-diagonal covariance matrices.

## How?
Loop over track states after the propagation extract the needed information for the update. Before we used the `collector()` inside the actor for this task. The collector was too confining, since we had to convert all n-dimensional measurements into n 1-dimensional measurements, removing all non-diagonal information from their covariances.

Blocked by:
- #3247
- #3248
kodiakhq bot pushed a commit that referenced this pull request Jun 11, 2024
paulgessinger pushed a commit to paulgessinger/acts that referenced this pull request Jun 14, 2024
This PR allows to fully support measurements with non-diagonal covariance matrices.

## How?
Loop over track states after the propagation extract the needed information for the update. Before we used the `collector()` inside the actor for this task. The collector was too confining, since we had to convert all n-dimensional measurements into n 1-dimensional measurements, removing all non-diagonal information from their covariances.

Blocked by:
- acts-project#3247
- acts-project#3248
paulgessinger pushed a commit to paulgessinger/acts that referenced this pull request Jun 14, 2024
@andiwand andiwand modified the milestones: next, v35.2.0 Jun 16, 2024
Matthewharri pushed a commit to Matthewharri/acts that referenced this pull request Jun 18, 2024
…ct#3248)

Have *almost* same settings for GX2F and KF makes it easier to understand in the physmon output and check if our results are good.

## Why *almost*?
Had also 3 FPEs which fixed here, but did not choose this approach:
- acts-project#3254

This issue only occurred for `2.5 < |eta| < 3.0`. To get better physmon until the problem is fixed (maybe in a later stage of the GX2F-development), the eta-range is reduced. The full eta-range could be used after solving:
- acts-project#3267
Matthewharri pushed a commit to Matthewharri/acts that referenced this pull request Jun 18, 2024
Use a temporary track container for the propagation during the updates, to ensure the original track container stays untouched.

Until now, we were clearing the original container with `trackContainer.clear()`. This is fine, until we have more tracks in our container.

blocked by:
- acts-project#3248

edit:
After acts-project#3248 the physmon does not change, since we switched from 2 particles/event to 1. Therefore, we also have only one track/container.

Before we could see the effect stronger, like in the graphic. However, I don't see a reason to change physmon to catch this.
![image](https://github.com/acts-project/acts/assets/70842573/55eb47b2-e268-4a01-a618-8379d36bae49)
Matthewharri pushed a commit to Matthewharri/acts that referenced this pull request Jun 18, 2024
This PR allows to fully support measurements with non-diagonal covariance matrices.

## How?
Loop over track states after the propagation extract the needed information for the update. Before we used the `collector()` inside the actor for this task. The collector was too confining, since we had to convert all n-dimensional measurements into n 1-dimensional measurements, removing all non-diagonal information from their covariances.

Blocked by:
- acts-project#3247
- acts-project#3248
Matthewharri pushed a commit to Matthewharri/acts that referenced this pull request Jun 18, 2024
timadye pushed a commit to andiwand/acts that referenced this pull request Jun 27, 2024
This PR allows to fully support measurements with non-diagonal covariance matrices.

## How?
Loop over track states after the propagation extract the needed information for the update. Before we used the `collector()` inside the actor for this task. The collector was too confining, since we had to convert all n-dimensional measurements into n 1-dimensional measurements, removing all non-diagonal information from their covariances.

Blocked by:
- acts-project#3247
- acts-project#3248
timadye pushed a commit to andiwand/acts that referenced this pull request Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changes Performance Component - Examples Affects the Examples module Fails Athena tests This PR causes a failure in the Athena tests Infrastructure Changes to build tools, continous integration, ...
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants