Skip to content
Snippets Groups Projects
Forked from atlas / athena
Source project has a limited visibility.
  • Savanna Shaw's avatar
    4f573e4a
    Adapt muon triggers to avoid duplicate processing · 4f573e4a
    Savanna Shaw authored
    Due to the way the input maker was configured for the EF SA muon triggers, we were duplicating processing of RoIs when running ms-only and combined muon chains in the same steps. In order to avoid this:
    - Have changed the input maker for the EF SA step to use the roi tool that fetches the RoIs from previous views (this allows us to use the same RoIs in both types of chains, instead of the using the L1 RoIs for ms-only chains and the L2 RoIs in the combined chains).
    - Change the input maker for the EF SA step to merge based on the initialRoI, which removes the duplication of views
    - Adjust the ViewCreatorFetchFromViewROITool to be able to fetch the RoIs from a specific view from earlier in the chain (default is to fetch from the view from the previous step)
    4f573e4a
    History
    Adapt muon triggers to avoid duplicate processing
    Savanna Shaw authored
    Due to the way the input maker was configured for the EF SA muon triggers, we were duplicating processing of RoIs when running ms-only and combined muon chains in the same steps. In order to avoid this:
    - Have changed the input maker for the EF SA step to use the roi tool that fetches the RoIs from previous views (this allows us to use the same RoIs in both types of chains, instead of the using the L1 RoIs for ms-only chains and the L2 RoIs in the combined chains).
    - Change the input maker for the EF SA step to merge based on the initialRoI, which removes the duplication of views
    - Adjust the ViewCreatorFetchFromViewROITool to be able to fetch the RoIs from a specific view from earlier in the chain (default is to fetch from the view from the previous step)
Code owners
Assign users and groups as approvers for specific file changes. Learn more.