-
Notifications
You must be signed in to change notification settings - Fork 30
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: eic/EICrecon
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4cd19d9
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: eic/EICrecon
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 8d654db
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 15 files changed
- 5 contributors
Commits on Jan 4, 2025
-
fix(ci): ubsan.supp: implicit-integer-sign-change in edm4hep::ObjectID (
#1685) ### Briefly, what does this PR introduce? This PR fixes an UBSan error external to our code, showing up e.g. https://github.com/eic/EICrecon/actions/runs/12128923399/job/33816533286?pr=1635#step:8:880 EDM4hep defines CollectionID as signed int32_t, https://github.com/key4hep/EDM4hep/blob/v00-10-05/edm4hep.yaml#L111, but podio defines it as unsigned uint32_t, https://github.com/AIDASoft/podio/blob/v01-01/include/podio/ObjectID.h#L25. This is an issue as of podio-0.17.1, AIDASoft/podio@ac086e0, and disappears with EDM4hep-0.99 which removed the edm4hep::ObjectID component. ### What kind of change does this PR introduce? - [x] Bug fix (issue https://github.com/eic/EICrecon/actions/runs/12128923399/job/33816533286?pr=1635#step:8:880) - [ ] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ ### Please check if this PR fulfills the following: - [ ] Tests for the changes have been added - [ ] Documentation has been added / updated - [ ] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? No. ### Does this PR change default behavior? No.
Configuration menu - View commit details
-
Copy full SHA for 3d882e5 - Browse repository at this point
Copy the full SHA 3d882e5View commit details
Commits on Jan 9, 2025
-
Change EventHeader check to be non fatal (#1698)
### Briefly, what does this PR introduce? Allows running of EICrecon on files without an EventHeader collection. Files with a single/small subset of output collections can have analysis continued without needing to manually persist EventHeader. A warning has been added. ### What kind of change does this PR introduce? - [ ] Bug fix (issue #__) - [x] New feature (issue #1696) - [ ] Documentation update - [ ] Other: __ ### Please check if this PR fulfills the following: - [ ] Tests for the changes have been added - [ ] Documentation has been added / updated - [ ] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? No ### Does this PR change default behavior? No --------- Co-authored-by: Dmitry Kalinkin <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 8fa634b - Browse repository at this point
Copy the full SHA 8fa634bView commit details -
Enable calorimeter hit merging by functions (#1668)
### Briefly, what does this PR introduce? This PR extends the functionality of the `CalorimeterHitsMerger` algorithm. Previously, reconstructed hits could only be merged across a given field of the readout of a calorimeter. This presents a challenge for calorimeters such as the Barrel HCal where 1. our readout has no segmentation beyond just eta & phi, and 2. it could be useful to study the response of the detector as a function of how many readout channels we gang together after reconstruction. This PR addresses this point by utilizing the `EvaluatorSvc` in a manner similar to the `adjacencyMatrix`, `peakNeighbourhoodMatrix` of the `CalorimeterIslandClustering` and the `sampFrac` of `CalorimeterHitReco`. Now the user has the ability to specify an (almost) arbitrarily complex transformation for a specific field of the readout via the `fieldTransformations` parameter, which defines both the field to transform and the function to map the indices of that field onto the desired reference indices. For example: ``` app->Add(new JOmniFactoryGeneratorT<CalorimeterHitsMerger_factory>( "HcalBarrelMergedHits", {"HcalBarrelRecHits"}, {"HcalBarrelMergedHits"}, { .readout = "HcalBarrelHits", .fieldTransformations = {"phi:phi-(5*((phi/5)-floor(phi/5)))"} }, app // TODO: Remove me once fixed )); ``` Here, the `HcalBarrelMergedHits` collection will merge 5 hits (i.e. scintillator tiles for the BHCal) adjacent in phi into a one with the position and cellID of the 1st of the 5, and no hits will be merged along eta. The previous behavior of the algorithm can be recovered by simply specifying the index to be mapped onto. For example: ``` app->Add(new JOmniFactoryGeneratorT<CalorimeterHitsMerger_factory>( "HcalEndcapNMergedHits", {"HcalEndcapNRecHits"}, {"HcalEndcapNMergedHits"}, { .readout = "HcalEndcapNHits", .fieldTransformations = {"layer:4", "slice:0"} }, app // TODO: Remove me once fixed )); ``` An example script of to change a transformation (and how to update the adjacency matrix accordingly) from the command-line is provided in the snippets repo [here](https://github.com/eic/snippets/blob/main/Calorimetery/CaloDebugTools/UtilityScripts/RunEICReconWithTileMerging.rb). ### What kind of change does this PR introduce? - [ ] Bug fix (issue #__) - [x] New feature (issue #1669 ) - [ ] Documentation update - [ ] Other: __ ### Please check if this PR fulfills the following: - [ ] Tests for the changes have been added - [ ] Documentation has been added / updated - [x] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? No. ### Does this PR change default behavior? No. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Dmitry Kalinkin <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d96cbff - Browse repository at this point
Copy the full SHA d96cbffView commit details
Commits on Jan 10, 2025
-
Configuration menu - View commit details
-
Copy full SHA for b953157 - Browse repository at this point
Copy the full SHA b953157View commit details -
Configuration menu - View commit details
-
Copy full SHA for 54a567e - Browse repository at this point
Copy the full SHA 54a567eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 74405a4 - Browse repository at this point
Copy the full SHA 74405a4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 525f5ba - Browse repository at this point
Copy the full SHA 525f5baView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8d654db - Browse repository at this point
Copy the full SHA 8d654dbView commit details
There are no files selected for viewing