From eccdb67d8de0c372c7ad7fcbe04e29af80b760bb Mon Sep 17 00:00:00 2001 From: Shuhei Kadowaki Date: Tue, 27 Aug 2024 22:31:52 +0900 Subject: [PATCH] mv the reference material added in #652 to the `Analysis Result` section Since `get_reports` is intended to be the general interface to get reports. --- docs/src/internals.md | 8 ++++++++ docs/src/optanalysis.md | 8 -------- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/src/internals.md b/docs/src/internals.md index 4783db3e4..56e6a1b3a 100644 --- a/docs/src/internals.md +++ b/docs/src/internals.md @@ -48,6 +48,14 @@ JET.JETToplevelResult JET.JETCallResult ``` +### [Splitting and filtering reports](@id optanalysis-splitting) + +Both `JETToplevelResult` and `JETCallResult` can be split into individual failures for integration with tools like Cthulhu: +```@docs +JET.get_reports +JET.reportkey +``` + ## Error Report Interface ```@docs diff --git a/docs/src/optanalysis.md b/docs/src/optanalysis.md index da5ce2329..0ea1c2628 100644 --- a/docs/src/optanalysis.md +++ b/docs/src/optanalysis.md @@ -237,14 +237,6 @@ JET.@test_opt JET.test_opt ``` -### [Splitting and filtering reports](@id optanalysis-splitting) - -The output of `JET.@report_opt` can be split into individual failures for integration with tools like Cthulhu: -```@docs -JET.get_reports -JET.reportkey -``` - ### [Top-level Entry Points](@id optanalysis-toplevel-entry) By default, JET doesn't offer top-level entry points for the optimization analysis, because it's usually used for only a