Hello Luciano,
Great points. I wasn't really sure how to use the backtrace, but now following the addresses there I found that the problem was in the Outflow thorn. In fact, paying closer attention to the parfile you shared a while back, I see that you don't use the Outflow thorn. Is it possible to use it within Llama maybe tweaking the "coord_system" parameter or the interpolator? Or should I consider alternatives?
I would have expected that Outflow should work with Llama since it only has fairly basics use of the interpolator.
I can see that this may be triggered in your parfile since you set:
Outflow::extra_variables = " HydroBase::rho HydroBase::Y_e HydroBase::entropy HydroBase::temperature GRHydro::poynting_scalar "
and "rho" is already in the set of variables that Outflow interpolates all the time i.e. this matches the description ("same interpolation to be done into different output arrays.") of the trigger in the comment.
So you could try what happens if you make sure that you are not requesting any of the variables that Outflow already interpolates then this may work. I think this is only "rho" right now. You can see the full list of default variables in Outflow's source code einsteinanalysis/Outflow/src/outflow.c:
CCTK_STRING input_array_names[NUM_INPUT_ARRAYS] = { "ADMBase::gxx", "ADMBase::gxy", "ADMBase::gxz", "ADMBase::gyy", "ADMBase::gyz", "ADMBase::gzz",
"HydroBase::vel[0]", "HydroBase::vel[1]", "HydroBase::vel[2]", "HydroBase::rho",
"ADMBase::betax", "ADMBase::betay", "ADMBase::betaz", "ADMBase::alp", };
If you could create a ticket with this parfile and linking to this email conversation (via the email archive http://lists.einsteintoolkit.org/pipermail/users/2021-October/date.html) that would be great. This should be supported by Llama.
Yours, Roland