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

Full compatibility with Segment Anything #1544

Open
astnmsn opened this issue Mar 27, 2024 · 12 comments
Open

Full compatibility with Segment Anything #1544

astnmsn opened this issue Mar 27, 2024 · 12 comments
Labels
blocked Should not be tackled right now feature The feature request onnx

Comments

@astnmsn
Copy link

astnmsn commented Mar 27, 2024

I have not found any equivalent request

Feature description

Addition of support for necessary operators to utilize the vit_b SAM Model which can be found here:

Pth Direct download

ONNX file sam_vit_b.onnx.zip

I have inspected the model using Netron and compared the nodes to the support list here

Below is the list of operators in the network that are partially or fully missing from the support list
Operator (missing support)

  • Mul (Import)
  • MatMul (Import)
  • Sin (Import)
  • Shape (Import)
  • Expand (Import)
  • Not (Import)
  • ReduceMean (Import)
  • ConstantOfShape (Full)
  • Where (Import)
  • Slice (Import)
  • OneHot (Import)
  • Tile (Import)
  • LayerNormalization (Import)
  • Gemm (Import)
  • ReduceMax (Import)
  • Floor (Full)

Feature motivation

I am currently trying to load and run an onnx model segment-anything inside an image editing app in an effort to provide a masking experience similar to the demo available here. I am integrating it into an existing rust codebase using wgpu that compiles to wasm and runs in the browser.

Before I can select burn as the ml library to support this workflow, I need to be sure that it supports the operators specified in the model.

@antimora antimora added onnx feature The feature request labels Mar 27, 2024
@antimora
Copy link
Collaborator

Thanks for filing this. This is helpful as we prioritize ONNX ops. If you have a direct link to the ONNX file, can you also link this?

@antimora
Copy link
Collaborator

Updating Expand to Import, since we just added this op. I need to update the docs.

@antimora
Copy link
Collaborator

Submitted a PR to fix the supported OPs document: #1547

@astnmsn
Copy link
Author

astnmsn commented Mar 27, 2024

This is the model download link provided by the SAM repo - I have also added to the original post

@antimora
Copy link
Collaborator

I think it might be faster to implement the model manually in Burn and load the pth weights file, which we now support.

You can check out an existing model to see how it's done: https://github.com/tracel-ai/models/tree/main/resnet-burn

We also have a YOLOX object detection PR in the works: tracel-ai/models#24

@laggui has written a great tutorial on this subject: https://dev.to/laggui/transitioning-from-pytorch-to-burn-45m

Recently, we made tons of enhancements to the PyTorchFileRecorder: https://discord.com/channels/1038839012602941528/1144670451763785769/1216788417984335872

image

@laggui, @nathanielsimard, @ashdtu, would this be worth implementing ourselves? Should we move this ticket to the models repo?

@laggui
Copy link
Member

laggui commented Mar 28, 2024

The community is always one step ahead 😄

We've actually discussed adding SAM to our models and this was in the plans following the release.

We still haven't decided whether we want to reimplement it and use the PyTorch file recorder to import the weights or use the ONNX import.

@antimora
Copy link
Collaborator

@laggui, if we decide to work on this, I am more inclined to adding ONNX OPs. It will be biggest bang for the buck instead of spending time to come up with the model by hand (although I am not sure how complex it is).

@laggui
Copy link
Member

laggui commented Apr 9, 2024

Btw, not sure if anyone has delved into the SAM code for ONNX export but it doesn't include all the operations to actually run the model for an input image. The encoder part is totally left out of the ONNX export and the exported ONNX model expects image embeddings as input.

In their example they still use their pytorch implementation to provide the embeddings to the ONNX runtime.

So even if we support the missing operations in this issue, SAM support will still not be complete. Is this what you expected @astnmsn?

@astnmsn
Copy link
Author

astnmsn commented Apr 9, 2024

@laggui Thanks for asking, and yes that is expected. We plan to run the first half of the model to generate the embeddings on the backend using pytorch. Only the second half, which produces the masks from the embeddings and the cursor/click positions, will be run on the client

@antimora
Copy link
Collaborator

Regarding Tile Op. We need to rename our current repeat op to repeat_dim and implement a proper repeat for all dimensions at once.

@antimora
Copy link
Collaborator

Resolving this ticket will resolve #1560 as well.

@laggui laggui added this to Burn 🔥 Apr 19, 2024
@laggui laggui moved this to In Progress in Burn 🔥 Apr 19, 2024
@nathanielsimard nathanielsimard moved this from In Progress to Todo in Burn 🔥 Apr 30, 2024
@nathanielsimard nathanielsimard moved this from Todo to In Progress in Burn 🔥 Apr 30, 2024
@laggui
Copy link
Member

laggui commented Apr 30, 2024

Current state of required ops based on the latest PRs:

op_type Burn Import
Add
Cast
Concat
Constant
ConstantOfShape
Conv
ConvTranspose
Cos
Div
Equal
Erf
Expand
Floor
Gather
Gemm
LayerNormalization ✔️
MatMul ✔️
Mul
Not ✔️
OneHot
Pow
Reciprocal
ReduceMax ✔️
ReduceMean ✔️
Relu
Reshape
Resize
Shape ✔️
Sin ✔️
Slice
Softmax
Sqrt
Sub
Tile
Transpose
Unsqueeze
Where ✔️

@antimora antimora added the blocked Should not be tackled right now label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Should not be tackled right now feature The feature request onnx
Projects
Status: In Progress
Development

No branches or pull requests

3 participants