Closed jaelpark closed 4 years ago
Thanks for the feedback. I mention @doliinychenko here, since he is the one most familiar with using SMASH as part of JETSCAPE and I will also ask around if we have experienced a similar issue before.
Can you please go to SMASH code, JETSCAPE/external_packages/smash/smash_code/src/isoparticletype.cc:324 and print out which resonance is causing the problem?
if (XS_RK_tabulation_ == nullptr) {
const auto res = states_[0]->iso_multiplet();
+ std::cout << res->name() << " is causing a problem" << std::endl;
XS_RK_tabulation_ = &RK_tabulations.at(res->name());
}
My first impression is that this is about some resonance table mismatch between sampler and SMASH.
Ok, I got "Δ̅ is causing a problem". It is unlikely to be a particle table mismatch. I'm looking into it.
It's not a SMASH problem, it's a problem of the SMASH wrapper in the JETSCAPE. The tabulations are simply not initialized there -- I'm working on it. The wrapper was written for an older SMASH version, where these tabulations were initialized inside SMASH in a different way. Let me fix that. Please open a JETSCAPE issue. This one can be closed.
Ok, thanks! I will open an issue there and refer to this one.
I have fixed it in the wrapper. Before it's merged to master you can use the oliiny/fix_smash_wrapper_bug in my fork https://github.com/doliinychenko/JETSCAPE.
Again, the issue can be closed here, as the problem is not SMASH-related.
Thanks Dmytro, the problem seems to be solved.
Thanks @doliinychenko for taking care of it.
I'm trying to use smash for hadronic rescattering as a part of JETSCAPE framework (integrated). However, it seems to always crash while performing some table look-ups and going out of range (see backtrace below). I'm using the default configuration for smash, and JETSCAPE should also be properly configured for the afterburner stage.
Here's a minimal JETSCAPE config to reproduce. The problem seems to disappear when I remove
<TransInputs>
section from the Trento configuration. Is this a smash bug or some misconfiguration issue from JETSCAPE side?