W. David Dagenhart

These are done and the PRs are submitted now: DQM/EcalPreshowerMonitorModule (PR #39616): - ESDaqInfoTask ecalPreshowerDaqInfoTask - ESDataCertificationTask ecalPreshowerDataCertificationTask - ESDcsInfoTask ecalPreshowerDcsInfoTask DQMServices/FwkIO (PR #39541): - DummyReadDQMStore reader

I just did L1Trigger/L1TMuonOverlap. I was just starting L1TriggerConfig, your comment was just in time. I'll do RecoJets/JetAnalyzers next.

@makortel Is the decision to use a GPU to produce products with a certain branch name one that applies to an entire process? Or can the decision be different for...

@makortel I made a first pass at this. I know it is not done and there are issues that need to be resolved before we even think about merging this....

I agree. I will try to modify it to only run when any other product is produced. That is a better criteria than associating it to TriggerResults or the existence...

Is there anything that exists to get the hardware chip names from in CMSSW or should I just start from scratch and try to figure out how to get this...

FYI A step forward in addressing this issue. Just submitted and waiting for review comments from anyone interested. #37831. The information collected by the new service is the information that...

I spent yesterday afternoon and this morning looking at this issue and I am not sure how to proceed with this and the related PR. But here are some comments...

The last time we discussed this issue, one question that came up was whether our design for storing parentage of products could be useful for storing the information we are...

I believe this is an incorrectly coded spin lock. If b is false on the first try, it works as it should. But if it is not, then expected is...