Corryvreckan issueshttps://gitlab.cern.ch/corryvreckan/corryvreckan/-/issues2020-08-27T10:55:03+02:00https://gitlab.cern.ch/corryvreckan/corryvreckan/-/issues/104Follow-up from "Add new module: TrackingMultiplet": Add GBL compatibility2020-08-27T10:55:03+02:00Paul Jean SchutzeFollow-up from "Add new module: TrackingMultiplet": Add GBL compatibilityThe following discussion from !273 should be addressed:
- [ ] @simonspa started a [discussion](https://gitlab.cern.ch/corryvreckan/corryvreckan/-/merge_requests/273#note_3329601): (+7 comments)
> Sorry, it's three in the end.
...The following discussion from !273 should be addressed:
- [ ] @simonspa started a [discussion](https://gitlab.cern.ch/corryvreckan/corryvreckan/-/merge_requests/273#note_3329601): (+7 comments)
> Sorry, it's three in the end.
>
> Currently your module only allows to create `Mutliplet` tracks. In principle there is nothing that is against also allowing other tracks to be formed based on the track candidates you find - or am I mistaken?
In its current implementation, `TrackingMultiplet` only supports the `TrackModel` `Multiplet`. With some changes it should be possible and would be worth extending this with a `GblTrack` compatibility, utilizing the known material budget of e.g. the `DUT` or parsing the material budget via the configuration. As a first step, this applies to known scatterers only, such as e.g. present in Telescope+DUT studies. Unknown scatterers are somewhat more tricky and to my knowledge require more changes in the `GblTrack` implementation.2.0Simon SpannagelPaul Jean SchutzeLennart HuthSimon Spannagelhttps://gitlab.cern.ch/corryvreckan/corryvreckan/-/issues/61Multiple track reconstructions modules with different pixel ranges2019-09-19T10:30:22+02:00Lennart HuthMultiple track reconstructions modules with different pixel rangesI am wondering how to implement an analysis flow like presented here (slide 15):
https://indico.cern.ch/event/731649/contributions/3237289/attachments/1778200/2891938/BTTB_Corryvreckan_tutorial_final.pdf
My idea is to read in data, perf...I am wondering how to implement an analysis flow like presented here (slide 15):
https://indico.cern.ch/event/731649/contributions/3237289/attachments/1778200/2891938/BTTB_Corryvreckan_tutorial_final.pdf
My idea is to read in data, perform clustering and then use each layer as DUT, asking for a track fit without the dut.
Is this possible? It would significantly reduce the computation time in our case, as most time is spent reading in the data.