Skip to content

Commit

Permalink
chore: move onnx_svg_to_gitbook.svg to gitbook assets
Browse files Browse the repository at this point in the history
  • Loading branch information
RomanBredehoft committed Jan 18, 2024
1 parent 5a4e984 commit 64ee9d4
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/developer-guide/onnx_pipeline.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ All Concrete ML built-in models follow the same pattern for FHE conversion:

Moreover, by passing a user provided `nn.Module` to step 2 of the above process, Concrete ML supports custom user models. See the associated [FHE-friendly model documentation](../deep-learning/fhe_friendly_models.md) for instructions about working with such models.

![Torch compilation flow with ONNX](../_static/compilation-pipeline/torch_to_numpy_with_onnx.svg)
![Torch compilation flow with ONNX](../.gitbook/assets/torch_to_numpy_with_onnx.svg)

Once an ONNX model is imported, it is converted to a `NumpyModule`, then to a `QuantizedModule` and, finally, to an FHE circuit. However, as the diagram shows, it is perfectly possible to stop at the `NumpyModule` level if you just want to run the PyTorch model as NumPy code without doing quantization.

Expand Down

0 comments on commit 64ee9d4

Please sign in to comment.