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

[QC-1112] Develop a task to monitor the TF/payload size #2388

Merged
merged 4 commits into from
Aug 21, 2024

Conversation

justonedev1
Copy link
Collaborator

I changed daq task regarding to the ticket. I think that everything requested from ticket is there, but obviously there might be better ways how to do things, so I am opening draft to check first.

@justonedev1 justonedev1 changed the title Qc 1112 Qc 1112: Develop a task to monitor the TF/payload size Aug 15, 2024
@Barthelemy Barthelemy changed the title Qc 1112: Develop a task to monitor the TF/payload size [WIP] [QC-1112] Develop a task to monitor the TF/payload size Aug 16, 2024
Copy link
Collaborator

@knopers8 knopers8 left a comment

Choose a reason for hiding this comment

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

Thanks, in general it's already very good, I would just propose to fix a few details.

Modules/Daq/src/DaqTask.cxx Outdated Show resolved Hide resolved
getIntParam("RdhPayloadSizeBins", 128),
getIntParam("RdhPayloadSizeMin", 0),
getIntParam("RdhPayloadSizeMax", 2047),
getIntParam("CRUidBins", 500),
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do you know what are CRU IDs normally? I mean, are they incremental IDs or some scattered numbers? If it's the second, we might need to find a better way to put them on an axis rather than just grouping them in bins.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

No, I don't know... I thought that you will tell me if there is going to be a problem. I did not even expect that there is going to be something weird, because in ticket is written just this:

New plots to add
    Distribution of the RDH payload sizes vs. CRU IDs (2D histo). Configurable X axis.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yes, I had this thought just now. We can check with Pippo then.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Pippo basically confirmed that it is 12 bits set by users, so it can be anything, as every detector team does their own thing.

Copy link
Collaborator

Choose a reason for hiding this comment

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

oh well. let's then leave it like this, but set the default max cru ID to 2^12-1. If we need something better, we will get a request.

getIntParam("numberRDHsMax", 100));
getObjectsManager()->startPublishing(mNumberRDHs.get(), PublicationPolicy::Forever);

mSumRDHSizesPerInputRecord = std::make_unique<TH1F>("sumRdhSizesPerInputRecord", "Sum of RDH sizes per InputRecord;bytes",
Copy link
Collaborator

Choose a reason for hiding this comment

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

It was not in the requirements in the ticket, but looking at the plots, it would be good to change the title to "Sum of RDH sizes in TF". Specifically:

  • A lot of people looking at this plot will not know what InputRecord is, so "TF" (for TimeFrame) should be clearer
  • Using "in TF" instead of "per TF" might make it clearer that the plot is 1D and would not be understood as "Sums of RDH sizes are on Y axis, TF IDs are on X axis".

Accordingly, the plot name and parameters could be changed, as well as uses of InputRecord in other plots.

@aferrero2707 would you agree?

Copy link
Contributor

Choose a reason for hiding this comment

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

@knopers8 @justonedev1 yes, I agree, and sorry for the late feedback!

Comment on lines 79 to 81
getIntParam("RdhPayloadSizeBins", 128),
getIntParam("RdhPayloadSizeMin", 0),
getIntParam("RdhPayloadSizeMax", 2047),
Copy link
Collaborator

Choose a reason for hiding this comment

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

These (RdhPayloadSize) are the parameters for X axis, while CRU IDs are Y. Can you flip the axes, so the contents correspond to the title ("RDH payload size per CRU", not "CRU IDs per RDH payload size")?

Modules/Daq/src/DaqTask.cxx Outdated Show resolved Hide resolved
Modules/Daq/src/DaqTask.cxx Show resolved Hide resolved
Modules/Daq/src/DaqTask.cxx Outdated Show resolved Hide resolved
Modules/Daq/src/DaqTask.cxx Outdated Show resolved Hide resolved
@knopers8
Copy link
Collaborator

Also, please update QC config example at QualityControl/Modules/Daq/daq.json with the new settings, make sure it works and move it to QualityControl/Modules/Daq/etc/daq.json.

@justonedev1 justonedev1 marked this pull request as ready for review August 20, 2024 16:23
@justonedev1 justonedev1 requested a review from knopers8 August 20, 2024 16:23
@justonedev1 justonedev1 changed the title [WIP] [QC-1112] Develop a task to monitor the TF/payload size [QC-1112] Develop a task to monitor the TF/payload size Aug 20, 2024
@knopers8 knopers8 enabled auto-merge (squash) August 21, 2024 06:35
@knopers8 knopers8 merged commit befd905 into AliceO2Group:master Aug 21, 2024
7 checks passed
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