Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Refactor] Refactor backend API #1869

Open
wants to merge 35 commits into
base: dev-1.x
Choose a base branch
from

Conversation

grimoire
Copy link
Member

@grimoire grimoire commented Mar 10, 2023

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

Motivation

  • IR Manager: Utils to export IR
  • Backend Param: data structure to support model export and backend inference
  • from_param: to_backend and build_wrapper can be called with backend parameter now.
  • add_arguments: console argument can be parsed from docstring of backend params.
  • easy argparse: Console tools can be create by backendmanager.main()
  • docs

to backend

param = backend_manager.build_param(....)
backend_manager.to_backend_from_param(ir_path, param)

inference

param = backend_manager.build_param(....)
wrapper = backend_manager.build_wrapper_from_param(param)

output = wrapper({input: tensor ....})

console

if __name__ == '__main__':
    backend_manager.main()

mmdeploy entry

python -m mmdeploy list --backend

python -m mmdeploy run tensorrt convert ....

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 repositories?
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 tests to ensure the correctness.
  3. If the modification has a dependency on downstream projects of a newer version, this PR should be tested with all supported versions of downstream projects.
  4. The documentation has been modified accordingly, like docstring or example tutorials.

@grimoire grimoire changed the title [Refactor][WIP] Refactor backend API [Refactor] Refactor backend API Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant