Currently, the seed checker within the package checker ensures that logged seeds are compliant. But it only raises a warning if seeds are not logged as stated here.
But we do not have a rule enforcing that all CLOSED submissions need to log the seed used although if seeds are logged, the package checker ensures that unique seeds are used in each run.
Since we expect all submissions to be run with different seeds and that the logged seed is proof that not all submission log files are run with the same seed, we need to make logging of seeds as a requirement instead of keeping it as an optional parameter.
(Creating this issues based on Training WG discussion on Sept 12th, 2024)
Currently, the seed checker within the package checker ensures that logged seeds are compliant. But it only raises a warning if seeds are not logged as stated here.
But we do not have a rule enforcing that all CLOSED submissions need to log the seed used although if seeds are logged, the package checker ensures that unique seeds are used in each run.
Since we expect all submissions to be run with different seeds and that the logged seed is proof that not all submission log files are run with the same seed, we need to make logging of seeds as a requirement instead of keeping it as an optional parameter.
(Creating this issues based on Training WG discussion on Sept 12th, 2024)