Skip to content

Commit

Permalink
mv the reference material added in #652 to the Analysis Result section
Browse files Browse the repository at this point in the history
Since `get_reports` is intended to be the general interface to get reports.
  • Loading branch information
aviatesk committed Aug 27, 2024
1 parent ff5bcd0 commit 4299067
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 8 deletions.
8 changes: 8 additions & 0 deletions docs/src/internals.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
8 changes: 0 additions & 8 deletions docs/src/optanalysis.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 4299067

Please sign in to comment.