mlcommons/logging

Remove weight init checking from compliance checker

Closed this issue · 0 comments

In the 17-November, 2022 Training WG meeting it was decided that weight init logging should no longer be required.

For the new benchmarks (LLM and DLRMv2) the mlperf_logging/compliance_checker/training_3.0.0/closed_*.yaml files simply won't include a KEY with NAME weights_initialization.

For the other benchmarks that are staying stable from v2.1 to v3.0 (bert, maskrcnn, resnet, rnnt, ssd, unet3d) we need to remember to remove the KEY with NAME weights_initialization from the training_3.0.0/closed_*.yaml files.