Switch Gear to extension data in tracking algorithm
Control use which by option CEPCSW_USE_GEAR in cmake/CEPCSWOptions.cmake
Merge request reports
Activity
13 13 static const int TPC = 4; 14 14 static const int SET = 5; 15 15 static const int ETD = 6; 16 static const int DC = 7; 16 // same position -> same ID, just named as different in different stage 17 static const int ITKBarrel = 2; 18 static const int ITKEndcap = 3; 19 static const int DC = 4; 20 static const int OTKBarrel = 5; 21 static const int OTKEndcap = 6; - Comment on lines +17 to +21
Hi @fucd, I think it is not a good idea to reuse the same ID. For example, After TDR, we may need several detector options, which can combine these sub-detectors.
changed this line in version 2 of the diff
Hi @lintao Thanks! I have update ID for DC. But for ITKBarrel, ITKEndcap, OTKBarrel and OTKEndcap, they are same as SIT, SET, FTD, ETD in deed. The reason is that we didn't name them by ourselves in history. And the tracking algorithm is not in good flexible consider, so they also need to keep same. Maybe we can re-design them after implementing new tracking algorithm or optimize old tracking or implement new detector design. Is it feasible?
added 17 commits
-
ac430435...e5986663 - 16 commits from branch
cepc:master
- 7981863e - Merge branch 'master' into gearremove
-
ac430435...e5986663 - 16 commits from branch
@lintao Yes, it is ready to merge. Thanks!
mentioned in commit 086f20f2