Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Comments

Close side panel

Provide TPC Tracking QA to QC (Part 1)#4810

Merged
davidrohr merged 6 commits intoAliceO2Group:devAliceO2Group/AliceO2:devfrom
davidrohr:dev_pull_requestdavidrohr/AliceO2:dev_pull_requestCopy head branch name to clipboard
Nov 11, 2020
Merged

Provide TPC Tracking QA to QC (Part 1)#4810
davidrohr merged 6 commits intoAliceO2Group:devAliceO2Group/AliceO2:devfrom
davidrohr:dev_pull_requestdavidrohr/AliceO2:dev_pull_requestCopy head branch name to clipboard

Conversation

@davidrohr
Copy link
Collaborator

This PR contains some preparation and goes the easy way to ship the QA histograms that can optionally be created during the tracking to QC.
The current output can be seen on https://qcg-test.cern.ch/?page=objectTree under TPC/MO/External-1 (There are some old intermediate histograms from 22:07 today pushed there accidentaly, no idea how to remove them, please ignore them). Secondaries and z-resolution is currently broken / missing, but independently from the export to QC.

In order to run: (Needs AliceO2Group/QualityControl#545)

o2-tpc-reco-workflow --infile tpcdigits.root --output-type clusters,tracks,qa | o2-qc --config json:/${QUALITYCONTROL_ROOT}/etc/tpcQCTrackingFromExternal_direct.json

(this will write to the test ccdb and overwrite what I just pushed there)

This PR already separates the extraction of the statistics and the postprocessing into individual steps.
However, currently they are just executed both one after another when the histograms are created. This can be changed easily later on to have a full chain with parallel aggregation -> merging -> postprocessing. Will not need any change in the TPC QA code, just in the DPL / QC / routing part.

In a second step, I'll provide a separate QC task, which will be able to run the resolution and the efficiency QA using the qc-tpc-track-reader as input, but this requires some more work. But it will basically provide a subset of what is created by the variant in this PR, since the separate QC task will not have access to the full information from during the tracking, but I think it will be useful nonetheless.

There are also some cuts / options already configurable via configKeyValues, will document them in the QC task once that is ready.

Ping @wiechula @shahor02 @stheckel @tklemenz @Barthelemy

wiechula
wiechula previously approved these changes Nov 11, 2020
Copy link
Collaborator

@wiechula wiechula left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @davidrohr , looks good. That was quick action! I guess the details we can then discuss. These are quite many histograms, so I think we will need to see how to deal with this in a good way. Most probably we simply can define a couple Layouts combining the relevant plots.

@davidrohr
Copy link
Collaborator Author

@wiechula : Note that ~50% of what I uploaded will not be there finally, the website currently contains also some bogus intermediate histograms. For myself, I am usually already arranging them in canvases, see the plots in this file:
plots.tar.gz

I am not sure if QC can work with canvases, if yes I could perhaps already provide them in this way.

@davidrohr
Copy link
Collaborator Author

@TimoWilken : I just saw that the macOS see doesn't use the new nice HTML log feature. Is there a reason for this, or can this be changed? :)

@TimoWilken
Copy link
Contributor

@davidrohr: that should change soon! :)

@Barthelemy
Copy link
Collaborator

I am not sure if QC can work with canvases, if yes I could perhaps already provide them in this way.

You can publish any TObject.

@knopers8
Copy link
Collaborator

But will QCG correctly display a canvas with multiple plots?

@davidrohr
Copy link
Collaborator Author

I have no idea about the canvas, it was just an idea, since I have them anyway to create PDFs directly.
Also, I am not sure if adding the canvas to the TCollection would work, or if I need also to all the histogrems / pads / legends themselves.
I am not sure if this is an important use case for QC, but if it could be done easily, perhaps it is worth it to find out.

@Barthelemy
Copy link
Collaborator

https://alice.its.cern.ch/jira/browse/QC-482
David, you could just publish the canvas to the QCDB and we can see what is the result ? out of curiosity.

@davidrohr davidrohr merged commit 658cd1e into AliceO2Group:dev Nov 11, 2020
@davidrohr
Copy link
Collaborator Author

https://alice.its.cern.ch/jira/browse/QC-482
David, you could just publish the canvas to the QCDB and we can see what is the result ? out of curiosity.

OK, sure, I can just give it a try and let's see what happens :)

@davidrohr
Copy link
Collaborator Author

@Barthelemy : For reference, it seems to work, the test object I pushed to the TPCTrackingQA folder is a TCanvas and it seems to show the contained histogram correctly. Currently trying with some more complicated Canvas, but I am having some issue with ROOT ownership, let's see.

@Barthelemy
Copy link
Collaborator

@davidrohr Nice ! I see them. I am not surprised that ROOT ownership comes in the way. FYI the objects you publish are owned by you, so the QC framework will not try to delete them behind your back.

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.

5 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.