fix inference docs

[sanbuphy]

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.

Motivation

Please describe the motivation of this PR and the goal you want to achieve through this PR.

Modification

Please briefly describe what modification is made in this PR.

BC-breaking (Optional)

Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.

Use cases (Optional)

If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.

Checklist

1. Pre-commit or other linting tools are used to fix the potential lint issues.
2. The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
3. If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMCls.
4. The documentation has been modified accordingly, like docstring or example tutorials.

[ZwwWayne]

Hi @sanbuphy ,

Thanks for your kind PR. It seems that your branch is out of date and causes much difference.

Now, we require all the PRs to be merged into the development branch, i.e., dev branch for MMDet 2.x and dev-3.x branch for MMDet 3.x.

If your modification is not checkout from these two branches, they may cause conflicts and you should add your modification based on these two branches.

If your modification is checkout from these two branches, your branch might be out of date. In such a case
Please rebase your branch to the target dev or dev-3.x branch. You can simply do that by modifying your pull behavior:

git config --local --add pull.rebase true  # make rebase a default behavior in pull

Then you can git pull and rebase the dev branch by

git pull dev-3.x  # if your modification is for MMDet 3.x
git pull dev  # if your modification is for MMDet 2.x

After rebase, you might need to add --force option when pushing code, e.g.,

git push [remote name] [you branch] --force

[sanbuphy]

Hi @sanbuphy ,

Thanks for your kind PR. It seems that your branch is out of date and causes much difference.

Now, we require all the PRs to be merged into the development branch, i.e., dev branch for MMDet 2.x and dev-3.x branch for MMDet 3.x.

If your modification is not checkout from these two branches, they may cause conflicts and you should add your modification based on these two branches.

If your modification is checkout from these two branches, your branch might be out of date. In such a case Please rebase your branch to the target dev or dev-3.x branch. You can simply do that by modifying your pull behavior:

git config --local --add pull.rebase true  # make rebase a default behavior in pull

Then you can git pull and rebase the dev branch by

git pull dev-3.x  # if your modification is for MMDet 3.x
git pull dev  # if your modification is for MMDet 2.x

After rebase, you might need to add --force option when pushing code, e.g.,

git push [remote name] [you branch] --force

Thank you, I have solved the problem.