-
Notifications
You must be signed in to change notification settings - Fork 11
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
Error Creating Alignment Tree for 2016 Data #966
Comments
There is a comment above hps-java/tracking/src/main/java/org/hps/recon/tracking/gbl/AlignmentStructuresBuilder.java Line 406 in 7e9a7ea
|
It might not be satisfied for 2016, no. You can just check if I'm hardcoding 7 layers in each volume. |
Appears like you are - can you point me to the place where I can extract how many layers there should be during the run from the detector model? hps-java/tracking/src/main/java/org/hps/recon/tracking/gbl/AlignmentStructuresBuilder.java Lines 319 to 343 in 7e9a7ea
|
hps-java/tracking/src/main/java/org/hps/recon/tracking/gbl/AlignmentStructuresBuilder.java Line 183 in 7e9a7ea
Looks like you hard code 7 layers, the 7th layer starts on line 183. |
Can you avoid calling this part by disabling the center of mass structure in the SimpleTrajAliDriver? |
You should be able to figure out what sensors are really there from the sensors passed to the method: hps-java/tracking/src/main/java/org/hps/recon/tracking/gbl/AlignmentStructuresBuilder.java Line 53 in 7e9a7ea
|
There are 36 sensors in the 2016 detector and 40 sensors in the 2019 detector. |
Yes, but then I get another error about how
Full Run Log
|
@cbravo135 The sensors that are available are listed below. I guess I could hack in a solution where if the L7 sensors aren't in the sensor list then they aren't added to the alignment structure tree? sensor_name - millepedeID
|
Hopefully this is an issue with how I've configured my run, but we shall see. I am running with hps-java:master (commit 7e9a7ea) and my branch of hps-mc developing an alignment workflow (tomeichlersmith:342-alignment-workflow-components commit 8e00404).
@cbravo135 @pbutti Do I need to provide some sort of detector map that was previously being provided automatically for the 2019 data I was test-running on? Or do I need to update the hps-java code to be able to handle the 2016 detector's alignment tree?
I am attempting to run the KF-based tracking and alignment over a subsample of 2016 data but I get the following error when attempting to run over a single partition.
I've tracked this down for us to look at.
hps-java/tracking/src/main/java/org/hps/recon/tracking/gbl/AlignmentStructuresBuilder.java
Lines 407 to 419 in 7e9a7ea
Full Run Log
The text was updated successfully, but these errors were encountered: