|
3 | 3 | Analyzer(), |
4 | 4 | model, |
5 | 5 | optimizer = nothing,, |
6 | | -)</code></pre><p>The additional keyword argument <code>optimizer</code> is used to specify the optimizer to use for the IIS resolver.</p><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/a6368b786003261ff7c43e2ef35c64a194a1ac05/src/Infeasibility/structs.jl#L6-L22">source</a></div></details></article><p>The analysis will return issues of the abstract type:</p><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.AbstractInfeasibilitylIssue"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.AbstractInfeasibilitylIssue"><code>MathOptAnalyzer.Infeasibility.AbstractInfeasibilitylIssue</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">AbstractInfeasibilitylIssue</code></pre><p>Abstract type for infeasibility issues found during the analysis of a model.</p><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/a6368b786003261ff7c43e2ef35c64a194a1ac05/src/Infeasibility/structs.jl#L25-L30">source</a></div></details></article><p>Specifically, the possible issues are:</p><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.InfeasibleBounds"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.InfeasibleBounds"><code>MathOptAnalyzer.Infeasibility.InfeasibleBounds</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">InfeasibleBounds{T} <: AbstractInfeasibilitylIssue</code></pre><p>The <code>InfeasibleBounds</code> issue is identified when a variable has a lower bound that is greater than its upper bound.</p><p>For more information, run: <code>julia julia> MathOptAnalyzer.summarize(MathOptAnalyzer.Infeasibility.InfeasibleBounds)</code>`</p><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/a6368b786003261ff7c43e2ef35c64a194a1ac05/src/Infeasibility/structs.jl#L33-L43">source</a></div></details></article><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.InfeasibleIntegrality"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.InfeasibleIntegrality"><code>MathOptAnalyzer.Infeasibility.InfeasibleIntegrality</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">InfeasibleIntegrality{T} <: AbstractInfeasibilitylIssue</code></pre><p>The <code>InfeasibleIntegrality</code> issue is identified when a variable has an integrality constraint (like <code>MOI.Integer</code> or <code>MOI.ZeroOne</code>) that is not consistent with its bounds. That is, the bounds do not allow for any integer value to be feasible.</p><p>For more information, run:</p><pre><code class="language-julia hljs">julia> MathOptAnalyzer.summarize( |
| 6 | +)</code></pre><p>The additional keyword argument <code>optimizer</code> is used to specify the optimizer to use for the IIS resolver.</p><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/b57e26d56c2e2fcaea1093e846fc87af9f7246b0/src/Infeasibility/structs.jl#L6-L22">source</a></div></details></article><p>The analysis will return issues of the abstract type:</p><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.AbstractInfeasibilitylIssue"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.AbstractInfeasibilitylIssue"><code>MathOptAnalyzer.Infeasibility.AbstractInfeasibilitylIssue</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">AbstractInfeasibilitylIssue</code></pre><p>Abstract type for infeasibility issues found during the analysis of a model.</p><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/b57e26d56c2e2fcaea1093e846fc87af9f7246b0/src/Infeasibility/structs.jl#L25-L30">source</a></div></details></article><p>Specifically, the possible issues are:</p><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.InfeasibleBounds"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.InfeasibleBounds"><code>MathOptAnalyzer.Infeasibility.InfeasibleBounds</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">InfeasibleBounds{T} <: AbstractInfeasibilitylIssue</code></pre><p>The <code>InfeasibleBounds</code> issue is identified when a variable has a lower bound that is greater than its upper bound.</p><p>For more information, run: <code>julia julia> MathOptAnalyzer.summarize(MathOptAnalyzer.Infeasibility.InfeasibleBounds)</code>`</p><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/b57e26d56c2e2fcaea1093e846fc87af9f7246b0/src/Infeasibility/structs.jl#L33-L43">source</a></div></details></article><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.InfeasibleIntegrality"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.InfeasibleIntegrality"><code>MathOptAnalyzer.Infeasibility.InfeasibleIntegrality</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">InfeasibleIntegrality{T} <: AbstractInfeasibilitylIssue</code></pre><p>The <code>InfeasibleIntegrality</code> issue is identified when a variable has an integrality constraint (like <code>MOI.Integer</code> or <code>MOI.ZeroOne</code>) that is not consistent with its bounds. That is, the bounds do not allow for any integer value to be feasible.</p><p>For more information, run:</p><pre><code class="language-julia hljs">julia> MathOptAnalyzer.summarize( |
7 | 7 | MathOptAnalyzer.Infeasibility.InfeasibleIntegrality |
8 | | -)</code></pre><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/a6368b786003261ff7c43e2ef35c64a194a1ac05/src/Infeasibility/structs.jl#L54-L68">source</a></div></details></article><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.InfeasibleConstraintRange"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.InfeasibleConstraintRange"><code>MathOptAnalyzer.Infeasibility.InfeasibleConstraintRange</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">InfeasibleConstraintRange{T} <: AbstractInfeasibilitylIssue</code></pre><p>The <code>InfeasibleConstraintRange</code> issue is identified when a constraint cannot be satisfied given the variable bounds. This analysis only considers one constraint at a time and all variable bounds of variables involved in the constraint. This issue can only be found is all variable bounds are consistent, that is, no issues of type <code>InfeasibleBounds</code> were found in the first layer of analysis.</p><p>For more information, run:</p><pre><code class="language-julia hljs">julia> MathOptAnalyzer.summarize( |
| 8 | +)</code></pre><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/b57e26d56c2e2fcaea1093e846fc87af9f7246b0/src/Infeasibility/structs.jl#L54-L68">source</a></div></details></article><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.InfeasibleConstraintRange"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.InfeasibleConstraintRange"><code>MathOptAnalyzer.Infeasibility.InfeasibleConstraintRange</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">InfeasibleConstraintRange{T} <: AbstractInfeasibilitylIssue</code></pre><p>The <code>InfeasibleConstraintRange</code> issue is identified when a constraint cannot be satisfied given the variable bounds. This analysis only considers one constraint at a time and all variable bounds of variables involved in the constraint. This issue can only be found is all variable bounds are consistent, that is, no issues of type <code>InfeasibleBounds</code> were found in the first layer of analysis.</p><p>For more information, run:</p><pre><code class="language-julia hljs">julia> MathOptAnalyzer.summarize( |
9 | 9 | MathOptAnalyzer.Infeasibility.InfeasibleConstraintRange |
10 | | -)</code></pre><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/a6368b786003261ff7c43e2ef35c64a194a1ac05/src/Infeasibility/structs.jl#L82-L98">source</a></div></details></article><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.IrreducibleInfeasibleSubset"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.IrreducibleInfeasibleSubset"><code>MathOptAnalyzer.Infeasibility.IrreducibleInfeasibleSubset</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">IrreducibleInfeasibleSubset <: AbstractInfeasibilitylIssue</code></pre><p>The <code>IrreducibleInfeasibleSubset</code> issue is identified when a subset of constraints cannot be satisfied simultaneously. This is typically found by the IIS resolver after the first two layers of infeasibility analysis have been completed with no issues, that is, no issues of any other type were found.</p><p>For more information, run:</p><pre><code class="language-julia hljs">julia> MathOptAnalyzer.summarize( |
| 10 | +)</code></pre><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/b57e26d56c2e2fcaea1093e846fc87af9f7246b0/src/Infeasibility/structs.jl#L82-L98">source</a></div></details></article><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.IrreducibleInfeasibleSubset"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.IrreducibleInfeasibleSubset"><code>MathOptAnalyzer.Infeasibility.IrreducibleInfeasibleSubset</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">IrreducibleInfeasibleSubset <: AbstractInfeasibilitylIssue</code></pre><p>The <code>IrreducibleInfeasibleSubset</code> issue is identified when a subset of constraints cannot be satisfied simultaneously. This is typically found by the IIS resolver after the first two layers of infeasibility analysis have been completed with no issues, that is, no issues of any other type were found.</p><p>For more information, run:</p><pre><code class="language-julia hljs">julia> MathOptAnalyzer.summarize( |
11 | 11 | MathOptAnalyzer.Infeasibility.IrreducibleInfeasibleSubset |
12 | | -)</code></pre><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/a6368b786003261ff7c43e2ef35c64a194a1ac05/src/Infeasibility/structs.jl#L112-L127">source</a></div></details></article><p>These issues are saved in the data structure that is returned from the <code>MathOptAnalyzer.analyze</code> function:</p><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.Data"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.Data"><code>MathOptAnalyzer.Infeasibility.Data</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">Data <: MathOptAnalyzer.AbstractData</code></pre><p>The <code>Data</code> type is used to store the results of the infeasibility analysis. This type contains vectors of the various infeasibility issues found during the analysis, including <code>InfeasibleBounds</code>, <code>InfeasibleIntegrality</code>, <code>InfeasibleConstraintRange</code>, and <code>IrreducibleInfeasibleSubset</code>.</p><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/a6368b786003261ff7c43e2ef35c64a194a1ac05/src/Infeasibility/structs.jl#L136-L143">source</a></div></details></article></article><nav class="docs-footer"><a class="docs-footer-prevpage" href="../feasibility/">« Feasibility Analysis</a><a class="docs-footer-nextpage" href="../numerical/">Numerical Analysis »</a><div class="flexbox-break"></div><p class="footer-message">Powered by <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> and the <a href="https://julialang.org/">Julia Programming Language</a>.</p></nav></div><div class="modal" id="documenter-settings"><div class="modal-background"></div><div class="modal-card"><header class="modal-card-head"><p class="modal-card-title">Settings</p><button class="delete"></button></header><section class="modal-card-body"><p><label class="label">Theme</label><div class="select"><select id="documenter-themepicker"><option value="auto">Automatic (OS)</option><option value="documenter-light">documenter-light</option><option value="documenter-dark">documenter-dark</option><option value="catppuccin-latte">catppuccin-latte</option><option value="catppuccin-frappe">catppuccin-frappe</option><option value="catppuccin-macchiato">catppuccin-macchiato</option><option value="catppuccin-mocha">catppuccin-mocha</option></select></div></p><hr/><p>This document was generated with <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> version 1.16.0 on <span class="colophon-date" title="Saturday 15 November 2025 21:19">Saturday 15 November 2025</span>. Using Julia version 1.12.1.</p></section><footer class="modal-card-foot"></footer></div></div></div></body></html> |
| 12 | +)</code></pre><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/b57e26d56c2e2fcaea1093e846fc87af9f7246b0/src/Infeasibility/structs.jl#L112-L127">source</a></div></details></article><p>These issues are saved in the data structure that is returned from the <code>MathOptAnalyzer.analyze</code> function:</p><article><details class="docstring" open="true"><summary id="MathOptAnalyzer.Infeasibility.Data"><a class="docstring-binding" href="#MathOptAnalyzer.Infeasibility.Data"><code>MathOptAnalyzer.Infeasibility.Data</code></a> — <span class="docstring-category">Type</span></summary><div><pre><code class="language-julia hljs">Data <: MathOptAnalyzer.AbstractData</code></pre><p>The <code>Data</code> type is used to store the results of the infeasibility analysis. This type contains vectors of the various infeasibility issues found during the analysis, including <code>InfeasibleBounds</code>, <code>InfeasibleIntegrality</code>, <code>InfeasibleConstraintRange</code>, and <code>IrreducibleInfeasibleSubset</code>.</p><a class="docs-sourcelink" target="_blank" href="https://github.com/jump-dev/MathOptAnalyzer.jl/blob/b57e26d56c2e2fcaea1093e846fc87af9f7246b0/src/Infeasibility/structs.jl#L136-L143">source</a></div></details></article></article><nav class="docs-footer"><a class="docs-footer-prevpage" href="../feasibility/">« Feasibility Analysis</a><a class="docs-footer-nextpage" href="../numerical/">Numerical Analysis »</a><div class="flexbox-break"></div><p class="footer-message">Powered by <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> and the <a href="https://julialang.org/">Julia Programming Language</a>.</p></nav></div><div class="modal" id="documenter-settings"><div class="modal-background"></div><div class="modal-card"><header class="modal-card-head"><p class="modal-card-title">Settings</p><button class="delete"></button></header><section class="modal-card-body"><p><label class="label">Theme</label><div class="select"><select id="documenter-themepicker"><option value="auto">Automatic (OS)</option><option value="documenter-light">documenter-light</option><option value="documenter-dark">documenter-dark</option><option value="catppuccin-latte">catppuccin-latte</option><option value="catppuccin-frappe">catppuccin-frappe</option><option value="catppuccin-macchiato">catppuccin-macchiato</option><option value="catppuccin-mocha">catppuccin-mocha</option></select></div></p><hr/><p>This document was generated with <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> version 1.16.0 on <span class="colophon-date" title="Sunday 16 November 2025 09:10">Sunday 16 November 2025</span>. Using Julia version 1.12.1.</p></section><footer class="modal-card-foot"></footer></div></div></div></body></html> |
0 commit comments