-
Notifications
You must be signed in to change notification settings - Fork 33
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
Further issues in builds of other SUSY processes #820
Comments
…5#820 Now HRDCOD=0 builds of susy_gg_gogo.sa are successful and runTest.exe succeeds against the HRDCOD=1 reference
…HRDCOD=0 builds madgraph5#820 Now HRDCOD=0 builds of susy_gg_gogo.sa are successful and runTest.exe succeeds against the HRDCOD=1 reference
…pParam, improving HRDCOD=0 builds madgraph5#820
I think I have essentially fixed all of these issues. Now cross checking them one by one.
This is fixed. The HRDCOD=1 results were right, the HRDCOD=0 results were wrong but are now fixed (some value assignments were missing).
This is also fixed
These are also fixed. Since this is a true and simple SUSY process, I aded this to the repo (and I removed susy_gg_tt, which just includes susy contrubtions to an existing SM process)
This is also fixed. All codegen, builds and basic tests for the processes above are all succeeding and giving internally consistent results. -- Summary: this is fixed in PR #824 - closing for simplicity |
…aph5#820 and more - will rerun the CI and all manual tests
The builds for one simple process gg>tt~ in the SUSY model is now fixed by PR #625 (for both HRDCOD=0 and HRDCOD=1).
I tried to investigate a few more SUSY processes, and unfortunately I still found other issues (which sometimes look very similar to those I already fixed).
In "import model MSSM_SLHA2; define q = u c d s u~ c~ d~ s~; generate g q > t t~ q", the HRDCOD=0 and HRDCOD=1 builds succeed and give the same results as each other. This is true in both P1 subdirectories.
In "import model MSSM_SLHA2; generate g g > go go", the HRDCOD=1 build succeeds, but the HRDCOD=0 build fails
I suggest that PR #625 can be merged first, and these issues investigated later on.
The text was updated successfully, but these errors were encountered: