To remove any ambiguity, it'd help if the rules were super explicit about how random seeds (if used) need to be unique across all runs. I think it's left somewhat implicit now, including via the requirement to run the package checker, but a clear statement which cannot be misinterpreted would help prevent any future debate.
In HPC weak-scaling submissions we are at the point where a submitter can accidentally have multiple common seeds because of the large number of models drawn and usage of a seed generator (e.g. $RANDOM) which can produce repeats.
To remove any ambiguity, it'd help if the rules were super explicit about how random seeds (if used) need to be unique across all runs. I think it's left somewhat implicit now, including via the requirement to run the package checker, but a clear statement which cannot be misinterpreted would help prevent any future debate.
In HPC weak-scaling submissions we are at the point where a submitter can accidentally have multiple common seeds because of the large number of models drawn and usage of a seed generator (e.g.
$RANDOM
) which can produce repeats.