Skip to content

[MCH] Introduce DCS processor#5394

Merged
shahor02 merged 2 commits intoAliceO2Group:devfrom
aphecetche:muon-dcs-processor
Feb 12, 2021
Merged

[MCH] Introduce DCS processor#5394
shahor02 merged 2 commits intoAliceO2Group:devfrom
aphecetche:muon-dcs-processor

Conversation

@aphecetche
Copy link
Collaborator

Add two workflows and one check program to deal with MCH DCS data points :

  • o2-calibration-mch-dcs-sim-workflow to generate fake random DCS data points
  • o2-calibration-mch-dcs-processor-workflow to accumulate those data points, until some condition is satisfied (either on size or duration). Once satisfied, the accumulation is sent to output to be further consumed (typically by the ccdb populator)
  • o2-mch-dcs-check-ccdb small program to quickly dump the accumulated MCH DCS data points from the CCDB

@aphecetche aphecetche requested a review from a team as a code owner February 5, 2021 17:50
@aphecetche
Copy link
Collaborator Author

@shahor02 I assume here the fullCI failure has nothing to do with this PR ?

@davidrohr
Copy link
Collaborator

The full CI is currently failing since the container has too little SHM. This had actually been fixed, don't know why it appeared again. I am having a look and pinged also Timo. Hopefully we can fix this today for good...
The current failure is unrelated. The problem with force-merging with red full CI is that then the codechecker and the full system test have not run on the PR.

@aphecetche
Copy link
Collaborator Author

@davidrohr thanks for the info. Actually the fullCI for this PR was apparently attempted on Feb 10 so maybe before the fix ?

@davidrohr
Copy link
Collaborator

Indeed, but I have also seen in other new CI runs that it is failing again.

@shahor02 shahor02 merged commit 311bb14 into AliceO2Group:dev Feb 12, 2021
@aphecetche aphecetche deleted the muon-dcs-processor branch February 12, 2021 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants