How to submit a metric

  1. What reviewers look for
  2. What to have ready
  3. How to submit on GitHub
  4. What happens next

Step 4 of 4 What happens next

Everything from here happens on your pull request — the page GitHub opened when you created it — and you will be emailed.

  • An automated check reports back

    It confirms the mechanical details — one file, correctly named, correctly formatted. It runs on a schedule rather than the moment you submit, so expect a result within the hour. If something is off it says exactly what to change; correct it and the check runs again.

    • within an hour

  • A reviewer makes first contact

    That is when review starts, not when it concludes. If two weeks pass with no response, you are welcome to add a comment on your submission as a reminder.

    • about two weeks

  • Discussion happens in the open

    Reviewers may ask questions or request changes, and may bring in subject-matter experts. To revise, edit the file in your copy — your submission updates automatically, and there is nothing to resubmit.

    • varies

  • Accepted, or closed with an explanation

    Accepted submissions are merged and considered for publication on the AI Metrology Center in a later update. If a submission is not a fit it is closed with an explanation, and you are welcome to respond.

    • outcome

Turn on GitHub email notifications

That is how reviewers reach you. Without them you will not know a question has been asked, and a submission usually needs one round of questions. Check your notification settings

You can run the same checks yourself

The checks NIST runs are two commands you can run yourself, and the repository explains how. Useful before you push a revision; optional either way, because the automated check reports back on its own. How to check it yourself