You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is meant to remind that, after the merge of #44044 (and its 14_0_X backport), the PPS relvals 1043,1044,1045, which run PPS AlCaReco producer on a 2022 dataset, would be getting complains about missing product (Cannot unpack: no FEDRawDataCollection found) as the product now expected by the gtStage2Digis in this PR is missing in those 2022 data. That error message had been silenced in the log, but it makes no sense to have in the matrix relvals that cannot upack the data.
As soon as we will have new data this year one should add similar relvals which test PPSAlCaRecoProcuder on the 2024 data, and remove those obsolete relvals 1043-45 as they won’t make any sense with the code currently in CMSSW_14_1_X and CMSSW_!4_0_X.
This must be done as soon as PPS will confirm that a suitable data file with the updated products in it becomes available.
The text was updated successfully, but these errors were encountered:
This issue is meant to remind that, after the merge of #44044 (and its 14_0_X backport), the PPS relvals 1043,1044,1045, which run PPS AlCaReco producer on a 2022 dataset, would be getting complains about missing product (
Cannot unpack: no FEDRawDataCollection found
) as the product now expected by the gtStage2Digis in this PR is missing in those 2022 data. That error message had been silenced in the log, but it makes no sense to have in the matrix relvals that cannot upack the data.As soon as we will have new data this year one should add similar relvals which test PPSAlCaRecoProcuder on the 2024 data, and remove those obsolete relvals 1043-45 as they won’t make any sense with the code currently in CMSSW_14_1_X and CMSSW_!4_0_X.
This must be done as soon as PPS will confirm that a suitable data file with the updated products in it becomes available.
The text was updated successfully, but these errors were encountered: