Add --external-config option to tools/torchscript_e2e_test.sh #347
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a simple way for externals to plug their backends into the test suite. They just implement the `TestConfig` class for their backend and write a small script that exposes it. I have a pending PR for iree-samples that successfully integrates this.
|
iree-samples PR: iree-org/iree-experimental#9 |
cathyzhyi
approved these changes
Oct 4, 2021
qedawkins
pushed a commit
to nod-ai/torch-mlir
that referenced
this pull request
Oct 3, 2022
* implementation Signed-off-by: chentong <[email protected]> * type check Signed-off-by: chentong <[email protected]> * add document Signed-off-by: chentong <[email protected]> * updatedocument Signed-off-by: chentong <[email protected]>
renxida
pushed a commit
that referenced
this pull request
Oct 8, 2024
# Description Implementation of the op for `torch.aten.unfold`: [TorchToLinalg Op Support #347](nod-ai/SHARK-ModelDev#849) Documentation of op can be found here: [PyTorch Docs](https://pytorch.org/docs/stable/generated/torch.Tensor.unfold.html) For this op, we apply a sliding window of some `size` along a single `dimension`, with `step` in between iterations. `Declaration: aten::unfold(Tensor(a) self, int dimension, int size, int step) -> Tensor(a)` The resulting `unfolded` tensor modifies the shape of `dimension` to be equal to the number of blocks that the sliding windows extracts/inserts, with an additional dimension of `size` appended (the number of cols of the output tensor directly translates from the size of the sliding window). So if we had a tensor of rank 3 (A x B x C), with dimension = 1, size = 2 and step = 2: (A x B x C) |=> (A x (B - size) // step + 1 x C x size) After extracting the window from the input tensor, we insert the (1 x size) slice into the output tensor. We can make this simpler by mapping the output indices from the input indices, like they do in the official implementation: [PyTorch Code](https://github.com/pytorch/pytorch/blob/main/torch/_inductor/lowering.py#L1694)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a simple way for externals to plug their backends into the test
suite. They just implement the
TestConfigclass for their backend andwrite a small script that exposes it.
I have a pending PR for iree-samples that successfully integrates this.