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

feat: remaining Python examples can be chained #1174

Merged
merged 42 commits into from
Apr 1, 2022

Conversation

timadye
Copy link
Contributor

@timadye timadye commented Feb 25, 2022

Update the Python in Examples/Scripts/Python to allow configuration of various full-chain examples.

Continuing the work of #1098 in order to complete the proposal originally discussed in #1093.

@timadye timadye added the 🚧 WIP Work-in-progress label Feb 25, 2022
@timadye timadye added this to the WIP milestone Feb 25, 2022
@timadye
Copy link
Contributor Author

timadye commented Feb 25, 2022

I open this PR to track ongoing development and stop #1098 going stale 😄. So far I have mostly completed the digitization and seeding examples, though the latter will need more customisation options.

@codecov
Copy link

codecov bot commented Feb 25, 2022

Codecov Report

Merging #1174 (4539ad2) into main (8016339) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1174   +/-   ##
=======================================
  Coverage   47.86%   47.86%           
=======================================
  Files         372      372           
  Lines       19443    19443           
  Branches     9151     9151           
=======================================
  Hits         9306     9306           
  Misses       3806     3806           
  Partials     6331     6331           

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

@timadye timadye removed the 🚧 WIP Work-in-progress label Mar 31, 2022
Tim Adye added 2 commits March 31, 2022 16:50
…l, but keep same value (for now) in tests for compatibility
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.

Ok let's merge this bad boy then.

@kodiakhq kodiakhq bot merged commit b7d70c4 into acts-project:main Apr 1, 2022
paulgessinger pushed a commit to paulgessinger/acts that referenced this pull request Apr 11, 2022
Update the Python in `Examples/Scripts/Python` to allow configuration of various full-chain examples.

Continuing the work of acts-project#1098 in order to complete the proposal originally discussed in acts-project#1093.
kodiakhq bot pushed a commit that referenced this pull request Apr 13, 2022
This requires a couple of changes:
1. Turn off the log failure thresholds for the Python based tests
   (otherwise setup becomes too complicated)
2. Run the physmon step **before** the python based tests: if the tests
   fail, the physmon html page will still be uploaded and accessible
   this way

I also change the implementation of the CKF tracks example test: it's
now parametrized via pytest to run the three configurations (seeded,
truth estimated, truth smeared) from before, and in addition runs it
with the ODD and the generic detector. I had to drop the numerical event
count checks for that to work, but that should be covered by the hash
check anyway (if the count changes the hash changes).

I'm also bumping the number of events for these checks from 10 to 100.

Finally, sparked by #1174, I'm
switching the operation mode of the physics monitoring to not fail the
job even if the comparisons fail. Let's try this workflow instead:

1. We try to cover the physics monitoring scenarios with hash checks
   also
2. The hash checks notify us if the output changes
3. We manually check the physics monitoring HTML file to get an idea
   whether the output changes are expected / tolerable
kodiakhq bot pushed a commit that referenced this pull request Jul 28, 2022
…ith full_chain_itk example (#1331)

Since `itk_seeding.py` only reads the SP from csv files, and to avoid duplicated code, I decided to modify `itk_seeding.py` in the new chained style from #1174 to allow `full_chain_itk` to retrieve the ITk configuration from `itk_seeding.py` and execute the seeding in the full-chain example.

We still cannot use the complete strip **standalone** configuration (`useDetailedDoubleMeasurementInfo` needs to be False) in the full-chain example because we need the strip measurement information from the SPs. In case we want to run the full-chain seeding for strips we need to implement the calculation of these values in ACTS.

@paulgessinger @robertlangenberg @timadye
@paulgessinger paulgessinger modified the milestones: WIP, v18.0.0 Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants