-
Notifications
You must be signed in to change notification settings - Fork 2
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
Dilepton target fails due to Unstable Particle and HAFT issues #86
Comments
I do not think D*(2007)⁺ exists. My guess is that it being merged with D∗(2010)+ does not work. Removing the pdgcode for D∗(2010)+ might fix it. |
I followed this advice and gave the dilepton target another particle list, but now it complains about D*(2460) with the same error. I also realised that probably there is no issue with HAFT, it's only compiler warnings. Therefore, it seems we have to figure out what the correct particle lists and decaymodes are for the dilepton target after the recent changes. |
My guess is that the particles.txt/decaymodes.txt are not correct for the dilepton target. I'll take a look. |
Yeah, this error happens because we did not update https://github.com/smash-transport/smash-analysis/blob/develop/test/dileptons/decaymodes.txt, I believe that the fix is just copying the files from the release branch. This should be done for other targets as well (if this is not automatic), because of Carl's changes to resonance properties. |
Normally, the targets use the default of SMASH: Targets which do not use either custom particle or decay list: energy scan, afterburner, FOPI, angular_distributions,cross_sections, densities I am copying the decay file for the dileptons, but for other targets I need someone with knowledge of the matter to tell me if something should be modified, and if yes, in which way. |
also the config files for dileptons require the "Oscar2013_bin" format, instead of the old "Binary". I think these were not properly implemented in the release branch @AxelKrypton, as SMASH throws
Should we deal with this on the SMASH side? Or leave the smash-analysis with "Binary"? I prefer the former for consistency. |
If I understood your error correctly, does this mean replacing "Binary" with "Oscar2013_bin" caused this issue? |
Of course, maybe I missed something. @Carl-Rosenkvist did your changes affect meson resonances?
Yeah I think so. For now, just revert the configs back to "Binary" in case you get the same error, since this is a key change and would not affect the analysis outcome. |
Okay I will test the dilepton target. For the other two, I will wait for @Carl-Rosenkvist to confirm which changes are needed. |
No, I only changed nucleon resonances parameters.
But then one would need to specify quantities? Empty quantities and Binary would produce a throw, right? |
Regarding possible changes for detailed balance, I just noticed that we never changed the particle and decay lists since at least SMASH 1.6. Should we really start that now? |
Yes, actually we should've started whenever there was a change to the default input particles. For most targets this is the case automatically, but the abovementioned ones were hardcoded, so I imagine we just forgot to update them. |
According to the present documentation ![]() the quantities can be specified for Particles and Collisions only and |
During the rc analysis run, the following issues occured:
It looks to me like two distinct issues:
I have never myself worked with HAFT, nor do I have an overview of the changes in the decaymodes. I tag everyone here whom I suspect to have more knowledge about this issue, and I would appreciate any form of support in fixing this.
The text was updated successfully, but these errors were encountered: