Skip to content

[PWGCF] FT0 amplitude and flow vs Nch#9620

Closed
ilikmeta wants to merge 4 commits intoAliceO2Group:masterfrom
ilikmeta:origin
Closed

[PWGCF] FT0 amplitude and flow vs Nch#9620
ilikmeta wants to merge 4 commits intoAliceO2Group:masterfrom
ilikmeta:origin

Conversation

@ilikmeta
Copy link
Contributor

No description provided.

@github-actions github-actions bot added the pwgcf label Jan 30, 2025
@github-actions github-actions bot changed the title FT0 amplitude and flow vs Nch [PWGCF] FT0 amplitude and flow vs Nch Jan 30, 2025
@alibuild
Copy link
Collaborator

Error while checking build/O2Physics/o2 for 9bb9ae4 at 2025-01-30 04:52:

## sw/BUILD/O2Physics-latest/log
/sw/SOURCES/O2Physics/9620-slc9_x86-64/0/PWGCF/Flow/Tasks/FlowGFWPbPb.cxx:174:128: error: arithmetic between enumeration type 'FlowGFWPbPb::eventprogress' and floating-point type 'double' is deprecated [-Werror=deprecated-enum-float-conversion]
ninja: build stopped: subcommand failed.

Full log here.

@alibuild
Copy link
Collaborator

Error while checking build/O2Physics/o2 for 9c9ca05 at 2025-01-30 07:32:

## sw/BUILD/O2Physics-latest/log
CMake Error at cmake/O2PhysicsAddExecutable.cmake:113 (add_executable):
CMake Error at cmake/O2PhysicsAddExecutable.cmake:113 (add_executable):

Full log here.

Please consider the following formatting changes to AliceO2Group#9620
@alibuild
Copy link
Collaborator

Error while checking build/O2Physics/o2 for a49e2d0 at 2025-01-30 07:49:

## sw/BUILD/O2Physics-latest/log
CMake Error at cmake/O2PhysicsAddExecutable.cmake:113 (add_executable):
CMake Error at cmake/O2PhysicsAddExecutable.cmake:113 (add_executable):

Full log here.

@ilikmeta
Copy link
Contributor Author

ilikmeta commented Jan 30, 2025

Dear expert, from the first efford to push my taks, O2linter had few warnings regarding lower and upper case characters. So, I midified the name of the task from FlowGFWPbPb.cxx to flowGFWPbPb.cxx . Howevet when I do git status I still see the old name:

iris_antreas_likmeta@IrisAntreassMBP O2Physics % git status                                
On branch origin
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   PWGCF/Flow/Tasks/FlowGFWPbPb.cxx

Do you have any suggestion on how to resolve this? Thanks

@victor-gonzalez
Copy link
Collaborator

Dear expert, from the first efford to push my taks, O2linter had few warnings regarding lower and upper case characters. So, I midified the name of the task from FlowGFWPbPb.cxx to flowGFWPbPb.cxx . Howevet when I do git status I still see the old name:

iris_antreas_likmeta@IrisAntreassMBP O2Physics % git status                                
On branch origin
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   PWGCF/Flow/Tasks/FlowGFWPbPb.cxx

Do you have any suggestion on how to resolve this? Thanks

Not quite sure I understand your question
You refer to the name of the task but what you wrote is the name of the source file
In git, if you want to change the name of one of the files, it is recommended to use git mv because in that way the whole history is preserved. After that you have to commit the changes. All this at local repo level. Then you have to push your changes to your fork in gitHub and if you have an already open PR it will update automatically after that push

SOURCES FlowGFWPbPb.cxx
SOURCES flowGFWPbPb.cxx
PUBLIC_LINK_LIBRARIES O2::Framework O2Physics::AnalysisCore O2Physics::GFWCore
COMPONENT_NAME Analysis)
Copy link
Collaborator

Choose a reason for hiding this comment

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

The linter is suggesting you which name you should use according to the name of your workflow, flowGfwPbpb.cxx. Probably you can reconsider if you want PbPb in the name of either your workflow or your source code file. I guess, apart from configurations, nothing should prevent to run your task on pp or even in OO if available

#define O2_DEFINE_CONFIGURABLE(NAME, TYPE, DEFAULT, HELP) Configurable<TYPE> NAME{#NAME, DEFAULT, HELP};

struct FlowGFWPbPb {
struct flowGFWPbPb {
Copy link
Collaborator

Choose a reason for hiding this comment

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

If you modify your source file according with the linter you should use the same name but with the first letter capitalized for your task name

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.

As suggested in the linter check Details link, you can run the checks locally before pushing your changes

@ilikmeta ilikmeta closed this Jan 30, 2025
@ilikmeta ilikmeta deleted the origin branch January 30, 2025 18:30
@ilikmeta ilikmeta restored the origin branch January 30, 2025 18:30
@ilikmeta ilikmeta reopened this Jan 30, 2025
@ilikmeta ilikmeta closed this Jan 30, 2025
@ilikmeta
Copy link
Contributor Author

A new PR was produced from ilikmeta:master (by fault) and close this one.

@victor-gonzalez
Copy link
Collaborator

Please, don't close a PR that has been already commented
We have to start from zero has if nothing had passed before
That is a bit of waste of time

@ilikmeta
Copy link
Contributor Author

My git was completely messed up and I pushed another PR through master. I closed that one as well. I tried to push again, but same thing, it went on master (I did not made a PR for this one) What is your suggestion to do?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

3 participants