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
Adding E, R and Z ranges to Close by gun generator #26229
Conversation
The code-checks are being triggered in jenkins. |
1 similar comment
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26229/8855
|
A new Pull Request was created by @tonydp03 (Tony Di Pilato) for master. It involves the following packages: IOMC/EventVertexGenerators @efeyazgan, @perrozzi, @civanch, @mdhildreth, @cmsbuild, @alberto-sanchez, @qliphy can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Please add a working snippet in Configuration/Generator/python, so that this can be linked easily with runTheMatrix/cmsDriver. This was suggested in #26065 |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26229/8856
|
Pull request #26229 was updated. @efeyazgan, @perrozzi, @civanch, @mdhildreth, @cmsbuild, @alberto-sanchez, @qliphy can you please check and sign again. |
please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
0f4e315
to
81521b5
Compare
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26229/8885
|
Pull request #26229 was updated. @efeyazgan, @perrozzi, @civanch, @mdhildreth, @cmsbuild, @alberto-sanchez, @qliphy can you please check and sign again. |
please test |
The tests are being triggered in jenkins. |
please abort |
Jenkins tests are aborted. |
@tonydp03 sorry, quickly looking at the generator fragment, it now looks ok, apart for the name (please use _cfi.py as for all other fragments). Anyway it looks you used cms-merge-topic to prepare this PR, which in general should be avoided. I see here 7 new files, but in practice 6 of them are from #26065, am I correct? I suggest that you close this PR and open a new one, where you just add the _cfi.py configuration fragment on top of the latest 10_6_X branch |
@fabiocos Indeed, but I modified the CloseByParticleGunProducer files in #26065 to handle a variable range in energy, R and z (that was the goal of the pull request), that's why I used cms-merge-topic. |
@tonydp03 fine, but please propose a clean PR with the snippet and the modification to the gun, without other cms-merge-topic |
Addressed in #26277. |
PR description:
This pull request is made because we wanted to introduce a range in Energy, R and Z in the CloseByParticleGunProducer Workflow. Now in the configuration file the energy, R and Z ranges must be specified, while the ParticleGun will select a random Energy, R and Z in those ranges.
PR validation:
This pull request adds a couple of features (as described before) on top of the pull request #26065 made by @rovere.
@felicepantaleo
@clelange