-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Dark Bremsstrahlung backport to 10_6_X #38901
Conversation
Removed unneccesary include of G4GenericBiasingProcess
A new Pull Request was created by @revering for CMSSW_10_6_X. It involves the following packages:
@cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ccad8b/26540/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_5_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
@revering , please add in the beginning of the title of this PR: [10_6_X] |
for (G4int i = 0; i < nElements; i++) { | ||
cross += theAtomNumDensityVector[i] * | ||
ComputeCrossSectionPerAtom( | ||
particle, kineticEnergy, (*theElementVector)[i]->GetZ(), (*theElementVector)[i]->GetA(), cut); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@revering , better now than never. (*theElementVector)[i]->GetA() returns molar mass of the atom (see https://geant4.kek.jp/lxr/source/materials/include/G4Element.hh). You need to change to
(*theElementVector)[i]->GetN(). The same patch should be added in 12_4 and 12_5.
{ | ||
//Deactivate the process after one dark brem. Needs to be reactivated in the end of event action. If this is in the stepping action instead, more than one brem can occur within each step. | ||
G4bool state = false; | ||
G4String pname = "muDBrem"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@revering , it is a minor thing but better use G4 mass (avoiding problems in corner cases):
double muMass = dp->GetDefinition()->GetPDGMass(); // this is exact muon mass in internal units (MeV)
@revering , I put two comments to the model. Better to implement this just now and forward port in new PRs to 12_4 and 12_5. |
@revering Please note there is a comment raised in master PR: #38329 (comment) |
…le definition instead of hardcoded value and use GetN instead of GetA to get target nucleon number. Implement code-format fix for G4muDarkBremsstrahlungModel Change G4muDarkBremsstrahlungModel to use Geant4 muon mass for muon_mass_mev as well as GeV muon mass.
Pull request #38901 was updated. @cmsbuild, @civanch, @mdhildreth can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ccad8b/26633/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_5_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Backport of implementation of Dark Bremsstrahlung physics process from #38329 to CMSSW_10_6_X for run II MC generation.
CustomPhysics.cc in 10_6_30_patch1 is different from original CMSSW_12_5_X base, but git cms-rebase-topic successfully reapplied the necessary additions for the Dark Brem sim without including other changes. Needed to resolve a merge conflict in CustomPhysics/BuildFile.xml caused by differences in the spacing between <use name> and the ordering of includes between 10_6_X and 12_5_X. Used the 12_5_X spacing and order, should have no effect (as far as I'm aware).
Generated a small test sample with Dark Brem enabled, and the process biases the cross section and produces Dark photons as expected.