Propagate LHCbApp.CondDBtag based on .Simulation
Compare changes
@@ -127,8 +127,10 @@ class LHCbApp(LHCbConfigurableUser):
GitLab service scheduled maintenance on Friday, March 21st 2025 as of 08h00 Geneva time for an estimated period of 1 hour. Further information under OTG0154918.
This avoids always adding two entries in CondDB.Tags, one for LHCBCOND and one for SIMCOND.
I discovered this bug since at
the moment there is no SIMCOND tag for DataType 2018 and
I set CondDBtag = "<latest:2018>"
, which in turn tries to
resolve the latest SIMCOND tag with this DataType.
This should be cherry picked in master
. I'm not sure it needs to be propagated back to 2017, etc.