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

Create a system to define converters that are written in python #56

Closed
narendasan opened this issue May 15, 2020 · 7 comments
Closed

Create a system to define converters that are written in python #56

narendasan opened this issue May 15, 2020 · 7 comments
Labels
component: api [Python] Issues re: Python API help wanted Extra attention is needed No Activity priority: low Will be handled, but not in the near term

Comments

@narendasan
Copy link
Collaborator

It would be nice if we are able to define converters in python for users to add support for a custom operator

@narendasan narendasan added help wanted Extra attention is needed priority: low Will be handled, but not in the near term component: api [Python] Issues re: Python API labels May 15, 2020
@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue has not seen activity for 30 days, Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot closed this as completed Jan 5, 2021
frank-wei pushed a commit that referenced this issue Jun 4, 2022
Summary:
Pull Request resolved: https://github.com/pytorch/fx2trt/pull/56

ATT

Reviewed By: khabinov

Differential Revision: D35649693

fbshipit-source-id: b3ef48142bdbeeca24cf12791f5946d8362d0564
mfeliz-cruise added a commit to mfeliz-cruise/Torch-TensorRT that referenced this issue Oct 6, 2022
# Description

Adds converter support for aten::squeeze(Tensor) which will remove any static dimension of size 1. An existing converter supports aten::squeeze(Tensor, int dim).

Fixes # (issue)

## Type of change

Please delete options that are not relevant and/or add your own.

- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- This change requires a documentation update

# Checklist:

- [ ] My code follows the style guidelines of this project (You can use the linters)
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas and hacks
- [ ] I have made corresponding changes to the documentation
- [ ] I have added tests to verify my fix or my feature
- [ ] New and existing unit tests pass locally with my changes
- [ ] I have added the relevant labels to my PR in so that relevant reviewers are notified
gs-olive pushed a commit to gs-olive/TensorRT that referenced this issue Oct 11, 2022
# Description

Adds converter support for aten::squeeze(Tensor) which will remove any static dimension of size 1. An existing converter supports aten::squeeze(Tensor, int dim).

Fixes # (issue)

## Type of change

Please delete options that are not relevant and/or add your own.

- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- This change requires a documentation update

# Checklist:

- [ ] My code follows the style guidelines of this project (You can use the linters)
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas and hacks
- [ ] I have made corresponding changes to the documentation
- [ ] I have added tests to verify my fix or my feature
- [ ] New and existing unit tests pass locally with my changes
- [ ] I have added the relevant labels to my PR in so that relevant reviewers are notified
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: api [Python] Issues re: Python API help wanted Extra attention is needed No Activity priority: low Will be handled, but not in the near term
Projects
None yet
Development

No branches or pull requests

1 participant