-
Notifications
You must be signed in to change notification settings - Fork 0
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
iDM Phase Space #14
Comments
I feel like we may need to generate the dark sector widths before we can faithfully generate events (since the dark sector widths are parameters for those events). I tried using MG/ME to calculate these widths but the values were so far off from the values listed by default in the parameters that I am uncertain on if that is the correct procedure.
This width as reported by MG/ME for zp is different from the width as defined by default in the model.
Lines 349 to 355 in de6f74e
|
Going to log a lot more detail here to help debug in the future. Various Runs of Full iDM ModelThe runs I studied here are focused on varying the parameters of the beam and the dark sector model. Hopefully this can lead to more information about how the idm model should be used. I generated the MadEvent directory using MadGraph5 v3.4.1 and idm subdirectory of commit 3e727b6 of this repository.
I then immediately changed the Runs
|
I tried a few other parameter points without changing the run card. The electron beam energy is still 2.3GeV while and tungsten target is 174GeV so it is stationary. 10k events were requested.
|
For future reference, the model I am exploring produces the attached Feynman diagrams when the dark brem + iDM decay chain is |
While the above is a decent sign that the model is functional, it does not remove the question of how big the phase space is. If it is very small, then there won't be very many As the table lays out, I was seeing some odd behavior and so to double check I made a new MadEvent workspace and started testing in larger batches.
How did I get this table?Some bash nonsense... for r in idm-1-no-restrict/Events/* idm-3-seed-success-density/Events/*; do
[ -f $r/unweighted_events.lhe ] || gunzip $r/unweighted_events.lhe.gz;
seed=$(grep iseed $r/unweighted_events.lhe | awk '{print $1}');
nevents=$(grep -c '</event>' $r/unweighted_events.lhe);
echo "$r | $seed | $nevents";
done And then I used |
Chat with Stefania and Tim notes
Tests to Learn More
|
|
|
run | iseed | nevents | xsec | description |
---|---|---|---|---|
1 | 21 | 10k | 2.48e-10 | default parameters ( |
2 | 30 | 10k | 2.24e-10 |
|
3 | 36 | 3 | 3e+31 |
|
4 | 45 | 0 | NA |
|
5 | 51 | 10k | 3.21e-8 |
GZPN |
6 | 60 | 0 | NA |
|
I'm not sure if the high xsec (or "Integrated Weight" as MG calls it) is accurate or if it is tell-tale of some phase-space bug.
Removing the dark photon - nucleus coupling makes things work as expected now 🎉 and removed the issue causing #15 Going to move to putting this into hps-mc. |
The default parameters that came with the MG model assume a much higher energy beam than what HPS uses. I am studying the 2016 data set with a 2.3GeV electron beam hitting tungsten (at rest with a mass set to 174GeV). This has pushed me to lower the masses of the DM substantially (mZP = 1GeV, mChi = 0.1GeV, and dMChi = 0.001 GeV), but even in this low mass configuration, MG is still struggling to find any phase space available. In fact, I am only getting zero-events, zero-cross section runs. Is it just a difficult phase space to access and I should be more patient? Am I changing the wrong parameters?
Near the end of running, I get this error.
The text was updated successfully, but these errors were encountered: