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

Add new displaced muon gun #17775

Merged
merged 3 commits into from Apr 3, 2017
Merged

Add new displaced muon gun #17775

merged 3 commits into from Apr 3, 2017

Conversation

dildick
Copy link
Contributor

@dildick dildick commented Mar 4, 2017

This muon gun was designed for Phase-2 L1 trigger studies.

  • It fires muons (1 or 2 per event) with distributions flat in impact parameter d0(dxy), pT, eta and phi.
  • Each muon has its own production vertex. The production vertex of the extra muon is located at (-x, -y, -z) of the primary muon.
  • Along z-axis muon, muon vertex z is generated according to a gaussian.
  • Muon momentum along xy and z is generated such that muons are not flying back to the beamspot (pxy * Lxy > 0 and pz * Lz > 0)
  • Muons that are produced at too large vz but small Lxy are vetoed. Such muons are not likely to be triggered.

@dildick, @tahuang1991 @kpedro88

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 4, 2017

A new Pull Request was created by @dildick (Sven Dildick) for master.

It involves the following packages:

Configuration/Generator
IOMC/ParticleGuns

@cmsbuild, @govoni, @perrozzi, @thuer, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald this is something you requested to watch as well.
@Muzaffar, @davidlange6, @smuzaffar you are the release manager for this.

cms-bot commands are listed here #13028

@dildick dildick closed this Mar 4, 2017
@dildick dildick reopened this Mar 4, 2017
@perrozzi
Copy link
Contributor

perrozzi commented Mar 4, 2017

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 4, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/18144/console Started: 2017/03/04 23:48

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 4, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 4, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 5, 2017

@perrozzi
Copy link
Contributor

perrozzi commented Mar 5, 2017

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 5, 2017

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @Muzaffar, @davidlange6, @smuzaffar

@dildick
Copy link
Contributor Author

dildick commented Mar 20, 2017

Can this code be integrated please?

@govoni
Copy link
Contributor

govoni commented Mar 20, 2017

+1

pz = pt * sinh(eta);
//vz = fabs(fRandomGaussGenerator->fire(0.0, LzWidth_/2.0));
float ConeTheta = ConeRadius_/ConeH_;
for (int j=0; j<100; j++){
Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @dildick - so after 100 tries the loop gives up and throws at random? Sounds rather dangerous. Why should this not be 100^2 or ^3 tries before issuing some sort of error message?

Copy link
Contributor

Choose a reason for hiding this comment

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

ok, i gather this is caught below at line 115. but unclear why 100 is the right scale to avoid bias?

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 not sure if we explicitly checked how many times a new vz needs to be thrown in order for it to be a good one. @tahuang1991: do you have an idea?

Copy link
Contributor Author

@dildick dildick Mar 27, 2017

Choose a reason for hiding this comment

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

@davidlange6 we tested the code. 100 tries is more than enough to ensure that a vz is thrown such that it is in the region where we expect displaced muons to appear from physics signals that we can actually trigger on. On both sides of the beamspot we exclude vz's in cones close to the beamline and opening up towards high-eta. Muons that are generated here will most likely not be triggered on anyway.

@cmsbuild
Copy link
Contributor

Pull request #17775 was updated. @cmsbuild, @govoni, @perrozzi, @thuer, @davidlange6 can you please check and sign again.

@perrozzi
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 29, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/18773/console Started: 2017/03/29 10:45

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@kpedro88
Copy link
Contributor

assign upgrade

@cmsbuild
Copy link
Contributor

New categories assigned: upgrade

@kpedro88 you have been requested to review this Pull request/Issue and eventually sign? Thanks

@cmsbuild
Copy link
Contributor

@kpedro88
Copy link
Contributor

+1

@perrozzi
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @Muzaffar, @davidlange6, @smuzaffar

@kpedro88
Copy link
Contributor

kpedro88 commented Apr 2, 2017

@davidlange6 please merge

@davidlange6
Copy link
Contributor

+1

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

Successfully merging this pull request may close these issues.

None yet

7 participants