Unfortunate channel naming can lead to mixed up hyperparameters in budget allocator about robyn

[gufengzhou]

thanks very much for raising this! we didnt consider this case and will include a fix soon. Have you observed similar sorting issues for the modelling itself? If you run the model with "standard naming" and same setting, do you get the same results? I'm trying to get a sense if I need to check more places regarding sorting.

[m4x3]

Hi! Thanks for looking into this. I now ran different iterations to check on the consistency of the results:

1. Running the same model with "standard naming", i.e. no varname is a substring of another varname.
2. Running the same model with "unfortunate naming", i.e. some varnames are substrings of other varnames.
3. Running the same model with "standard naming" but with minor changes to the initial varnames.

Version 1 and 2 produce different model results. This indicates that the sorting issue also occurs somewhere in the modeling and/or output generation process.

Version 1 and 3 produce identical results. This was expected, but I wanted to rule out that changing names, in general, can produce different results.

For now, I will continue using standard names to rule out any issues for my project.