From f0a0a204ef21000ad0186b0abf7eeea61af929af Mon Sep 17 00:00:00 2001 From: pytorchbot Date: Wed, 24 Apr 2024 09:50:33 -0700 Subject: [PATCH] Fix a small inconsistency on the SDK debugging page (#3247) (#3290) Summary: Pull Request resolved: https://github.com/pytorch/executorch/pull/3247 so that the code is consistent with the text description Reviewed By: dbort Differential Revision: D56481274 fbshipit-source-id: f303b966ebf3e07b510ef825c7bc09eaecd89554 (cherry picked from commit ca8e5896438e6c7ea05f3f7f6713067ab9c9392c) Co-authored-by: Olivia Liu --- docs/source/sdk-debugging.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/sdk-debugging.md b/docs/source/sdk-debugging.md index 1563038eb5..45e50b44e8 100644 --- a/docs/source/sdk-debugging.md +++ b/docs/source/sdk-debugging.md @@ -20,7 +20,7 @@ For a real example reflecting the steps below, please refer to [sdk_example_runn Span buffer((uint8_t*)debug_buffer, debug_buffer_size); etdump_gen.set_debug_buffer(buffer); etdump_gen.set_event_tracer_debug_level( - EventTracerDebugLogLevel::kIntermediateOutputs); + EventTracerDebugLogLevel::kProgramOutputs); ``` - Intermediate outputs of executed (non-delegated) operations (will include the program level outputs too) @@ -28,7 +28,7 @@ For a real example reflecting the steps below, please refer to [sdk_example_runn Span buffer((uint8_t*)debug_buffer, debug_buffer_size); etdump_gen.set_debug_buffer(buffer); etdump_gen.set_event_tracer_debug_level( - EventTracerDebugLogLevel::kProgramOutputs); + EventTracerDebugLogLevel::kIntermediateOutputs); ``` 3. Build the runtime with the pre-processor flag that enables tracking of debug events. Instructions are in the [ETDump documentation](./sdk-etdump.md). 4. Run your model and dump out the ETDump buffer as described [here](./sdk-etdump.md). (Do so similarly for the debug buffer if configured above)