Urania issueshttps://gitlab.cern.ch/lhcb/Urania/-/issues2021-06-24T22:51:31+02:00https://gitlab.cern.ch/lhcb/Urania/-/issues/40Is variable mu_CombDLLmu_isMuon_Brunel variable deprecated or not fully devel...2021-06-24T22:51:31+02:00Hangyi WuIs variable mu_CombDLLmu_isMuon_Brunel variable deprecated or not fully developed yet for PIDGen?I can successfully generate values for the `mu_CombDLLmu_IsMuon_Brunel` variable. However, this `IsMuon` is not actually a binary variable which is needed in my analysis. The PIDGen help message indicates it has another variable named `m...I can successfully generate values for the `mu_CombDLLmu_IsMuon_Brunel` variable. However, this `IsMuon` is not actually a binary variable which is needed in my analysis. The PIDGen help message indicates it has another variable named `mu_CombDLLmu_isMuon_Brunel` (note the _i_ here is now in lower case) which seems to be the desired variable, since usually TupleToolPid will provide branches with name xxx_isMuon also with a lower case _i_. However, if I run the same script for this variable, PIDGen script gives error `Unable to open file /eos/lhcb/wg/PID/PIDGen/Data/Run2/mu_CombDLLmu_isMuon_Brunel/MagDown_2016_distrib.root; No such file or directory`.
Both the `PIDGen` help message and [Run 2 control plots](https://lhcb-pid-wgp-plots.web.cern.ch/lhcb-pid-wgp-plots/PIDGen/Run2/) indicates the existence of such a variable, I'm wondering if I'm doing it wrong or PIDGen hasn't fully supported it yet.
I really appreciate your time of reading this issue.
Attachments:
PIDGen help message saved with command `python2 $PIDPERFSCRIPTSROOT/scripts/python/PIDGenUser/PIDGen.py >> pidgen_help.log`. You can see the `mu_CombDLLmu_isMuon_Brunel` is existed for Run 2.
[pidgen_help.log](/uploads/63a574595ab05d09a73e174e7d49c065/pidgen_help.log)https://gitlab.cern.ch/lhcb/Urania/-/issues/34Followups of !2772021-02-24T13:40:07+01:00Kevin HeinickeFollowups of !277The following discussion from !277 should be addressed:
- [ ] @jobutter started a [discussion](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3321015): (+1 comment)
> (already an issue before MR maybe): merge is not ...The following discussion from !277 should be addressed:
- [ ] @jobutter started a [discussion](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3321015): (+1 comment)
> (already an issue before MR maybe): merge is not given in the function...
- [ ] Make production/detection asymmetries floatable, see @miverone's discussion [here](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3321567) and [here](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3321587)
- [ ] Make CP fit parameter ranges configurable, see [this comment](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3321751)
- [ ] Reduce naming-dependency, see [this comment](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3321774) and [this comment](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3322328)
- [ ] [Make time error pdf binning](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3321818) and [MistagPDF binning](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3321904) configurable
- [ ] [revisit sign conventions of DecRateCoeff_Bd](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3322167)
- [ ] Allow to adjust merging and naming options if only signal component is generated, see @jobutter's [comment here](https://gitlab.cern.ch/lhcb/Urania/-/merge_requests/277#note_3322495)