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

PWGCF: fixed QA flags #7962

Merged
merged 3 commits into from
Oct 12, 2024
Merged

PWGCF: fixed QA flags #7962

merged 3 commits into from
Oct 12, 2024

Conversation

abilandz
Copy link
Contributor

No description provided.

Copy link
Collaborator

@victor-gonzalez victor-gonzalez left a comment

Choose a reason for hiding this comment

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

Please, check that you are not rolling back changes done for standardization and converting compiler warnings to errors
I pointed them out for you to check them

Also

  • there was an issue with the abs function which started to return an int as it should. But this caused a lot of unexpected behaviors because people had extensively used it. Check that you are using std::abs instead
  • Prefix your PR and commit titles with PWGCF:

@@ -189,7 +189,7 @@ struct MultiparticleCorrelationsAB // this name is used in lower-case format to
// -------------------------------------------

// C) Process only simulated data:
void processSim(CollisionSim const& /*collision*/, aod::BCs const&, TracksSim const& /*tracks*/)
void processSim(CollisionSim const& collision, aod::BCs const&, TracksSim const& tracks)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please, don't remove the commented out collisions and tracks
We are in the process of converting all warnings to errors and this is a not used variable warning
They were changed in the past directly on gitHub so probably you are still having locally an old version

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was rolled back by mistake - I pushed a new commit, which brings this back!

@@ -216,7 +216,7 @@ struct MultiparticleCorrelationsAB // this name is used in lower-case format to
// -------------------------------------------

// F) Process only converted simulated Run 2 data:
void processSim_Run2(CollisionSim const& /*collision*/) // TBI 20240517 extend this subscription eventually
void processSim_Run2(CollisionSim const& collision) // TBI 20240517 extend this subscription eventually
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here

@@ -234,7 +234,7 @@ struct MultiparticleCorrelationsAB // this name is used in lower-case format to
// -------------------------------------------

// H) Process both converted reconstructed and corresponding MC truth simulated Run 1 data;
void processRecSim_Run1(CollisionRecSim_Run1 const& /*collision*/, aod::BCs const&, TracksRecSim const& /*tracks*/, aod::McParticles const&, aod::McCollisions const&)
void processRecSim_Run1(CollisionRecSim_Run1 const& collision, aod::BCs const&, TracksRecSim const& tracks, aod::McParticles const&, aod::McCollisions const&)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here

@@ -2080,7 +2105,7 @@ void BookParticleCutsHistograms()
if (pc.fUseParticleCuts[ePtDependentDCAxyParameterization]) {
pc.fPtDependentDCAxyFormula = new TFormula("fPtDependentDCAxyFormula", pc.fsParticleCuts[ePtDependentDCAxyParameterization].Data());
// As a quick insanity check, try immediately to evaluate something from this formula:
if (std::isnan(pc.fPtDependentDCAxyFormula->Eval(1.44))) {
if (isnan(pc.fPtDependentDCAxyFormula->Eval(1.44))) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Any reason for removing the std:: on isnan?
I think this was introduced directly on gitHub to standardize the code and perhaps you are still using an old local version. Please, check it

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 didn't pull these changes in my class done directly on GitHub, that's the only reason. In the latest commit, I switched back to std::

// *) std::isnan() check (remember that 'nan' is 0./0., inf-inf, etc. However 'inf' itself is NOT a 'nan', therefore std::isnan(1./0.) is false, std::isnan(0./0.) is true, etc.):
if (std::isnan(track.phi()) || std::isnan(track.pt()) || std::isnan(track.eta())) {
// *) isnan() check (remember that 'nan' is 0./0., inf-inf, etc. However 'inf' itself is NOT a 'nan', therefore isnan(1./0.) is false, isnan(0./0.) is true, etc.):
if (isnan(track.phi()) || isnan(track.pt()) || isnan(track.eta())) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here

@victor-gonzalez victor-gonzalez changed the title fixed QA flags PWGCF: fixed QA flags Oct 12, 2024
@victor-gonzalez
Copy link
Collaborator

Thanks!

@victor-gonzalez victor-gonzalez enabled auto-merge (squash) October 12, 2024 14:49
@victor-gonzalez victor-gonzalez merged commit 206a1fc into AliceO2Group:master Oct 12, 2024
12 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.

2 participants