Clone the submission tree e.g. under your home directory:
$ export SUBMISSION_ROOT=$HOME/submissions_inference_0_7
$ git clone [email protected]:mlperf/submissions_inference_0_7.git $SUBMISSION_ROOT
$ cd $SUBMISSION_ROOT
We recommend creating a new branch for every logically connected group of results e.g. all results from your System-Under-Test (SUT) or only relating to a particular benchmark. Prefix your branch name with your organization's name. Feel free to include the SUT name, implementation name, benchmark name, etc.
For example:
$ git checkout master && git pull
$ git checkout -b dividiti-closed-aws-g4dn.4xlarge-openvino
Populate your branch according to the submission rules.
You can inspect your changes:
$ git status
On branch dividiti-closed-aws-g4dn.4xlarge-openvino
Untracked files:
(use "git add <file>..." to include in what will be committed)
closed/dividiti/code/
closed/dividiti/compliance/
closed/dividiti/measurements/
closed/dividiti/results/
closed/dividiti/systems/
nothing added to commit but untracked files present (use "git add" to track)
and make intermediate commits as usual:
$ git add closed/dividiti
$ git commit -m "Dump repo:mlperf-closed-aws-g4dn.4xlarge-openvino."
Once you are happy with the tree structure, truncate the accuracy logs and run the submission checker, culminating in e.g.:
INFO:main:Results=2, NoResults=0
INFO:main:SUMMARY: submission looks OK
Once you and the submission checker are happy with the tree structure, you can push the changes:
$ git push
fatal: The current branch dividiti-closed-aws-g4dn.4xlarge-openvino has no upstream branch.
To push the current branch and set the remote as upstream, use
git push --set-upstream origin dividiti-closed-aws-g4dn.4xlarge-openvino
Do exactly as suggested:
$ git push --set-upstream origin dividiti-closed-aws-g4dn.4xlarge-openvino
If you now go to https://github.com/mlperf/submissions_inference_0_7/, you should see a notification
about your branch being recently pushed and can immediately create a pull request (PR).
You can also select your branch from the dropdown menu under <> Code
. (Aren't you happy you prefixed your branch's name with the submitter's name?)
As usual, you can continue committing to the branch until the PR is merged, with any changes being reflected in the PR.
See, for example, dividiti's PR created using similar steps.