SIMCOND issueshttps://gitlab.cern.ch/lhcb-conddb/SIMCOND/-/issues2021-09-23T15:02:13+02:00https://gitlab.cern.ch/lhcb-conddb/SIMCOND/-/issues/13Update of ECAL dead cells2021-09-23T15:02:13+02:00Giovanni CavalleroUpdate of ECAL dead cellsThere are 9 dead cells for ECAL in the MC as defined in https://gitlab.cern.ch/lhcb-conddb/SIMCOND/-/blob/master/Conditions/Ecal/Calibration/Quality.xml, as pointed out in !146. Checks of the real dead cells need to be performed and the ...There are 9 dead cells for ECAL in the MC as defined in https://gitlab.cern.ch/lhcb-conddb/SIMCOND/-/blob/master/Conditions/Ecal/Calibration/Quality.xml, as pointed out in !146. Checks of the real dead cells need to be performed and the file above to be updated.https://gitlab.cern.ch/lhcb-conddb/SIMCOND/-/issues/11Wrong datatypes in tag sim-20210423-vc-md100-Sim10-PbNe2021-06-25T11:06:23+02:00Marco Clemencicmarco.clemencic@cern.chWrong datatypes in tag sim-20210423-vc-md100-Sim10-PbNeThe tag https://gitlab.cern.ch/lhcb-conddb/SIMCOND/-/tags/sim-20210423-vc-md100-Sim10-PbNe declares data types as
```yaml
---
datatypes: [2018]
simtypes: [Sim10]
---
```
while it should be
```yaml
---
datatypes: ["#2018"]
simtypes: [Sim1...The tag https://gitlab.cern.ch/lhcb-conddb/SIMCOND/-/tags/sim-20210423-vc-md100-Sim10-PbNe declares data types as
```yaml
---
datatypes: [2018]
simtypes: [Sim10]
---
```
while it should be
```yaml
---
datatypes: ["#2018"]
simtypes: [Sim10]
---
```https://gitlab.cern.ch/lhcb-conddb/SIMCOND/-/issues/10Procedure for synchronisation of branches for special running conditions2021-05-06T11:52:01+02:00Gloria CortiProcedure for synchronisation of branches for special running conditionsThe following procedure has been agreed to minimise the work to propagate MR from one year reference branch to branches for special running conditions.
* A branch should be made from the reference for the different running condition o...The following procedure has been agreed to minimise the work to propagate MR from one year reference branch to branches for special running conditions.
* A branch should be made from the reference for the different running condition of the same `Sim-TYPE/YEAR`.
* Once a MR is accepted into the reference branch `Sim-TYPE/YEAR` a merge of the reference branch `Sim-TYPE/YEAR' will be made targeting the branch of the special running conditions instead of cherry-picking the initial MR
Example:
1. branch `Sim10/2018-PbPb` from `Sim10/2018`
2. merge changes in Velo Position in `Sim10/2018-PbPb`
2. merge change in dE/dx calo in `Sim10/2018`
2. merge change in IT dead channels map in `Sim10/2018`
2. make new tag in `Sim10/2018`
2. merge `Sim10/2018` into `Sim10/2018-PbPb`
2. make new tag in `Sim10/2018-PbPb`
This should also allow to keep track more easily of the difference between branches and should be applied also to the `YEAR-mu` branches.Marco Clemencicmarco.clemencic@cern.chMarco Clemencicmarco.clemencic@cern.ch