Closed nv-rborkar closed 2 years ago
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅
We are going to put this table in a policy doc. Are we sure that duplicating the information will be good?
We needn't duplicate if this is already in the policy doc somewhere. Is there an existing PR for this?
It's being created and will be on the website, not GitHub. And contain details for all the benchmark suites.
David
On Thu, Feb 3, 2022 at 1:21 PM Ritika Borkar @.***> wrote:
We needn't duplicate if this is already in the policy doc somewhere. Is there an existing PR for this?
— Reply to this email directly, view it on GitHub https://github.com/mlcommons/training_policies/pull/483#issuecomment-1029413644, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJXLOKYVCG2JFRYCLFJEQ6TUZLWW5ANCNFSM5NPM2KHA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
It will be useful to have a historical table in policies showing compatible MLPerf rounds for comparing performance as well as when models got /dropped/changed/introduced.