Draft:Add muonDLL
Add muonDLL into Hlt reconstruction. Needs LHCb!3498 (closed) and ParamFiles!45
Merge request reports
Activity
added RTA label
Does this use the CondDB for the MuonDLL? I thought we agreed here Moore#402 (comment 5367016) to put it into
ParamFiles
, which is easier.An example of an algorithm doing this would be here: https://gitlab.cern.ch/lhcb/Rec/-/blob/master/CaloFuture/CaloFuturePIDs/src/CaloChargedBremAlg.cpp
Edited by Michel De CianI guess you have your new conditions in your own repository? My guess is you have to (manually) set your local conddb environment variable
GITCONDDBPATH
(that is, in case in your log fileToolSvc.GitSIMCOND
won't show your local repo)Edited by Maarten Van Veghel@marco, I put things in LHCBCOND because I thought that was the place were constants were taken, but that was a mistake. I will inspire from @mveghel to put them in the right place, but I will move all the parameters as they will not change either, not only the ones related to the DLL.
anything I try to add as conditions, even changing the xml file to PARAMFILES, does not work.
I keep on getting the error when compiling Moore
MuonIDHlt1AlgPr ERROR ConditionDerivation failed to retrieve PARAM/ParamFiles/data/MuonIDGlobal.xml StatusCode=INVALID_ROOT
This is the same thing I was getting when using SIMCOND, so there must be something profoundly wrong that I am doing, that I am not able to understand here.
Others can correct me, but I don't think you should put the
xml
file inPARAMFILES
, as this is essentially just a folder one can put in whatever one wants. It is not a DB in the sense of the CondDB.https://gitlab.cern.ch/lhcb-datapkg/ParamFiles/-/tree/master/data
Looking at what other algorithms do, you could:
- Put the context of your
xml
file in ajson
file, and then read this in the algorithm to fill thestd::vector
s (like here: https://gitlab.cern.ch/lhcb/Allen/-/blob/master/main/src/InputReader.cpp#L121) - Or if you have the original histograms, you can also directly use this (this is e.g. what is done for the Calo, https://gitlab.cern.ch/lhcb/Rec/-/blob/master/CaloFuture/CaloFuturePIDs/src/CaloChargedBremAlg.cpp#L105)
Edited by Michel De Cian- Put the context of your
I think it's not a matter of the format of the file, in
PARAMFILES
there are plenty of different formats. The problem is that whatever I add seems to be not picked up properly (even without adding any new functionality).I will adopt the first option as there are no histograms for the muonID, just some vectors of numbers. I will keep digging.
Also note that I spent some time to fix the other issues with the flags here: Moore!1455 (merged) !2785 (merged) LHCb!3468 (merged)
It might be easier to start from this set of MRs than from yours, as it will avoid that you have to merge them in. I included everything from your latest MR, except the access to the DB / PARAMFILES.
added 184 commits
-
7f516094...35e118ca - 180 commits from branch
master
- a0487045 - add MuonDLL
- ac740b05 - change name of conditions
- 3557b3bb - Fixed formatting
- 978bc0b9 - read parameters from paramFiles
Toggle commit list-
7f516094...35e118ca - 180 commits from branch
@rvazquez I See that you started committing things to this MR. As said before, I made quite some updates to the class to fix other issues, so you should start from !2785 (merged) to put things in, otherwise merging will be a bit of a pain I am afraid.
mentioned in merge request LHCb!3498 (closed)
mentioned in issue Moore#421 (closed)