Skip to content

Commit e8b4de5

Browse files
rtj1svekars
andauthored
Fix broken links to torch.export documentation (#3747)
## Summary - Fixes broken 404 links to `pytorch.org/docs/main/export.html` which have moved to `docs.pytorch.org/docs/stable/user_guide/torch_compiler/export.html` ## Files Updated - `recipes_source/torch_export_challenges_solutions.rst` - Fixed link to existing-frameworks section - `unstable_source/openvino_quantizer.rst` - Fixed link to torch export mechanism Fixes #3712 Co-authored-by: Svetlana Karslioglu <svekars@meta.com>
1 parent c15619d commit e8b4de5

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

recipes_source/torch_export_challenges_solutions.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ handle the unsupported code, and then resumes capturing the graph. This break in
3333
One of the key differences between ``torch.export`` and ``torch.compile`` is that ``torch.export`` doesn’t support graph breaks
3434
which means that the entire model or part of the model that you are exporting needs to be a single graph. This is because handling graph breaks
3535
involves interpreting the unsupported operation with default Python evaluation, which is incompatible with what ``torch.export`` is
36-
designed for. You can read details about the differences between the various PyTorch frameworks in this `link <https://pytorch.org/docs/main/export.html#existing-frameworks>`__
36+
designed for. You can read details about the differences between the various PyTorch frameworks in this `link <https://docs.pytorch.org/docs/stable/user_guide/torch_compiler/export.html#existing-frameworks>`__
3737

3838
You can identify graph breaks in your program by using the following command:
3939

unstable_source/openvino_quantizer.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ OpenVINO backend compiles the FX Graph generated by TorchDynamo into an optimize
2424

2525
The quantization flow mainly includes four steps:
2626

27-
- Step 1: Capture the FX Graph from the eager Model based on the `torch export mechanism <https://pytorch.org/docs/main/export.html>`_.
27+
- Step 1: Capture the FX Graph from the eager Model based on the `torch export mechanism <https://docs.pytorch.org/docs/stable/user_guide/torch_compiler/export.html>`_.
2828
- Step 2: Apply the PyTorch 2 Export Quantization flow with OpenVINOQuantizer based on the captured FX Graph.
2929
- Step 3: Lower the quantized model into OpenVINO representation with the `torch.compile <https://docs.openvino.ai/2024/openvino-workflow/torch-compile.html>`_ API.
3030
- Optional step 4: : Improve quantized model metrics via `quantize_pt2e <https://openvinotoolkit.github.io/nncf/autoapi/nncf/experimental/torch/fx/index.html#nncf.experimental.torch.fx.quantize_pt2e>`_ method.

0 commit comments

Comments
 (0)