Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TRD;) tracking task in mc workflow #1467

Merged
merged 7 commits into from
Mar 7, 2024

Conversation

nasirmehdimalik
Copy link
Contributor

No description provided.

Copy link
Collaborator

@martenole martenole left a comment

Choose a reason for hiding this comment

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

Thanks @nasirmehdimalik . I have only some minor comments

"cycleDurationSeconds": "60",
"dataSource": {
"type": "direct",
"query": "digits:TRD/DIGITS;tracklets:TRD/TRACKLETS;triggers:TRD/TRKTRGRD;noiseMap:TRD/NOISEMAP/0?lifetime=condition&ccdb-path=TRD/Calib/NoiseMapMCM;chamberStatus:TRD/CHSTATUS/0?lifetime=condition&ccdb-path=TRD/Calib/HalfChamberStatusQC;fedChamberStatus:TRD/FCHSTATUS/0?lifetime=condition&ccdb-path=TRD/Calib/DCSDPsFedChamberStatus"
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't think you need to query the digits for the tracklets task

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

"host": "ccdb-test.cern.ch:8080",
"username": "not_applicable",
"password": "not_applicable",
"name": "not_applicable"
Copy link
Collaborator

Choose a reason for hiding this comment

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

all these not_applicable entries can be removed

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm keeping them because all other JSON files have the same structure, and I'm unsure if they might be needed later

Copy link
Collaborator

Choose a reason for hiding this comment

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

But we should try to keep the json files as compact as possible. It makes maintenance easier. So please remove them. If there are other TRD QC json files where you find this you could even clean them up there as well :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

"moduleName": "QcTRD",
"detectorName": "TRD",
"cycleDurationSeconds": "60",
"maxNumberCycles": "-1",
Copy link
Collaborator

Choose a reason for hiding this comment

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

this is the default in any case, so not needed

Copy link
Contributor Author

Choose a reason for hiding this comment

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

without this lines gives error
`
std::exception::what: No such node (moduleName)

terminate called after throwing an instance of 'boost::wrapexceptboost::property_tree::ptree_bad_path'
what(): No such node (moduleName)

Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm quite sure Ole meant maxNumberCycles, not moduleName

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yes indeed. @nasirmehdimalik can you please remove maxNumberCycles?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed

Copy link
Collaborator

@martenole martenole left a comment

Choose a reason for hiding this comment

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

Approving only to start the CI

Copy link
Collaborator

@martenole martenole left a comment

Choose a reason for hiding this comment

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

Thanks @nasirmehdimalik ! Now that I look at it again, could you please also change the name trd-digits-task.json to something like trd-standalone-tasks.json? This would reflect that also the tracklets task is there and in the future all QC tasks not requiring any other detector could go there.

Copy link
Collaborator

@martenole martenole left a comment

Choose a reason for hiding this comment

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

Looks good to me now. Could you just also add the TPC-TRD matches please? Online we disable the TPC-TRD matching, but in the asynch. processing it is there, so we should also check the QC for it. Sorry didn't notice this earlier in you PR. But this is a tiny change and then we should be ready for merging it

"cycleDurationSeconds": "60",
"dataSource": {
"type": "direct",
"query": "trackITSTPCTRD:TRD/MATCH_ITSTPC;trigITSTPCTRD:TRD/TRGREC_ITSTPC"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you please add also TPC-TRD matches to the query here?

MC/config/QC/json/trd-tracking-task.json Outdated Show resolved Hide resolved
Copy link
Collaborator

@martenole martenole left a comment

Choose a reason for hiding this comment

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

Should be fine now, let's wait for the CI to finish

@nasirmehdimalik
Copy link
Contributor Author

@martenole since the checks fail and I pasted here the error "[ERROR] invalid workflow in o2-qc: No matching output found for <matcher query: (and origin:TRD (and description:MATCH_TPC (just startTime:$0 )))> as requested by data processor "qc-task-TRD-Tracking"". I think it is due to last commit.

@martenole
Copy link
Collaborator

@sawenzel it seems in the simulation check the matching of TRD to TPC tracks is disabled. Can you explain to me how the trd_track_sources are obtained in

trd_track_sources = anchorConfig.get('o2-trd-global-tracking-options', {}).get('track-sources', 'TPC,ITS-TPC')
?
Which configuration is used for the CI test here?

@benedikt-voelkel
Copy link
Contributor

From my side we can go ahead with this, @martenole @nasirmehdimalik

@martenole martenole merged commit 10b933c into AliceO2Group:master Mar 7, 2024
6 checks passed
noferini pushed a commit that referenced this pull request Apr 18, 2024
* TRD;) tracking task  in mc workflow

* rmove digit query from tracklet task

* removed not maxNumberCycles, applicable items

* trd-digit-task name change to trd-standalone-task

* Update MC/config/QC/json/trd-tracking-task.json

Co-authored-by: Ole Schmidt <[email protected]>

* Update MC/config/QC/json/trd-tracking-task.json

* readerCommand configured with TPC_TRD

---------

Co-authored-by: Ole Schmidt <[email protected]>
noferini pushed a commit that referenced this pull request Apr 19, 2024
* TRD;) tracking task  in mc workflow

* rmove digit query from tracklet task

* removed not maxNumberCycles, applicable items

* trd-digit-task name change to trd-standalone-task

* Update MC/config/QC/json/trd-tracking-task.json

Co-authored-by: Ole Schmidt <[email protected]>

* Update MC/config/QC/json/trd-tracking-task.json

* readerCommand configured with TPC_TRD

---------

Co-authored-by: Ole Schmidt <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants