allow direct method setting to support custom layers #460
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, converters may only be written for methods with modules visible by
torch2trt.py
. In addition, converter methods must be specified by full string path, like@tensorrt_converter('torch.relu')
.This PR allows the user to specify converters for custom methods.
@tensorrt_converter
will now automatically determine and import the needed module. For example,@tensorrt_converter("my_package.my_module.my_activation")
now works, assuming my_package is installed.@tensorrt_converter
will now accept non-builtin methods directly. This helps for locally defined functions, or if it is difficult to determine the full function string name. For example, a local functionmy_activation
can now be converted