<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Infeasibility in proc optmodel using milp in Mathematical Optimization, Discrete-Event Simulation, and OR</title>
    <link>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/652361#M3124</link>
    <description>Is there a way I can just proc print the infeasibility causing constraints than going through the entire log.</description>
    <pubDate>Mon, 01 Jun 2020 20:09:55 GMT</pubDate>
    <dc:creator>nithishsaji94</dc:creator>
    <dc:date>2020-06-01T20:09:55Z</dc:date>
    <item>
      <title>Infeasibility in proc optmodel using milp</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/651568#M3118</link>
      <description>&lt;P&gt;I want to get the constraints causing infeasibility and store it in a table for printing. SAS doesn't allow me to use IIS=on when using milp solver.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2020 14:06:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/651568#M3118</guid>
      <dc:creator>nithishsaji94</dc:creator>
      <dc:date>2020-06-01T14:06:28Z</dc:date>
    </item>
    <item>
      <title>Re: Infeasibility in proc optmodel using milp</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/651571#M3119</link>
      <description>&lt;P&gt;MILP IIS is available in SAS Optimization 8.5 (SAS Viya 3.5), released in November 2019:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://go.documentation.sas.com/?cdcId=pgmsascdc&amp;amp;cdcVersion=9.4_3.5&amp;amp;docsetId=casmopt&amp;amp;docsetTarget=casmopt_whatsnew_sect002.htm&amp;amp;locale=en"&gt;https://go.documentation.sas.com/?cdcId=pgmsascdc&amp;amp;cdcVersion=9.4_3.5&amp;amp;docsetId=casmopt&amp;amp;docsetTarget=casmopt_whatsnew_sect002.htm&amp;amp;locale=en&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For other releases, you might try using the RELAXINT option, in case the LP relaxation is infeasible:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;solve with lp relaxint / iis=on;&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 01 Jun 2020 14:06:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/651571#M3119</guid>
      <dc:creator>RobPratt</dc:creator>
      <dc:date>2020-06-01T14:06:52Z</dc:date>
    </item>
    <item>
      <title>Re: Infeasibility in proc optmodel using milp</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/651574#M3120</link>
      <description>&lt;P&gt;I have base sas 9.4 and SAS EG 7.1. Looks like I don't have that yet.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2020 14:07:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/651574#M3120</guid>
      <dc:creator>nithishsaji94</dc:creator>
      <dc:date>2020-06-01T14:07:09Z</dc:date>
    </item>
    <item>
      <title>Re: Infeasibility in proc optmodel using milp</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/651617#M3121</link>
      <description>&lt;P&gt;I don't quite understand.&amp;nbsp; Did you try the SOLVE statement that I recommended?&amp;nbsp; If so, did you get an error message?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2020 14:07:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/651617#M3121</guid>
      <dc:creator>RobPratt</dc:creator>
      <dc:date>2020-06-01T14:07:25Z</dc:date>
    </item>
    <item>
      <title>Re: Infeasibility in proc optmodel using milp</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/652353#M3122</link>
      <description>&lt;P&gt;Tried it with that, unfortunately it was still infeasible. I managed to predefine certain conditions which would make the problem unfeasible, as sort of a message to my users.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2020 19:46:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/652353#M3122</guid>
      <dc:creator>nithishsaji94</dc:creator>
      <dc:date>2020-06-01T19:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: Infeasibility in proc optmodel using milp</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/652358#M3123</link>
      <description>&lt;P&gt;OK, that result is a &lt;EM&gt;good&lt;/EM&gt; thing when you want to figure out why a problem is infeasible.&amp;nbsp; It means that even the linear programming relaxation is infeasible.&amp;nbsp; The following statement will then show you the resulting IIS found by the solver to help you diagnose the infeasibility:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;expand / iis;&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 01 Jun 2020 19:55:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/652358#M3123</guid>
      <dc:creator>RobPratt</dc:creator>
      <dc:date>2020-06-01T19:55:51Z</dc:date>
    </item>
    <item>
      <title>Re: Infeasibility in proc optmodel using milp</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/652361#M3124</link>
      <description>Is there a way I can just proc print the infeasibility causing constraints than going through the entire log.</description>
      <pubDate>Mon, 01 Jun 2020 20:09:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/652361#M3124</guid>
      <dc:creator>nithishsaji94</dc:creator>
      <dc:date>2020-06-01T20:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: Infeasibility in proc optmodel using milp</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/652376#M3125</link>
      <description>&lt;P&gt;You can use the Output Delivery System to write the EXPAND / IIS output to a data set:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;   ods output expand=myexpand;
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;You can then use PROC PRINT if you want, but it will look very similar.&amp;nbsp; Both ways display only the IIS (and not all the other variables and constraints) in the Results Viewer.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2020 21:30:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Infeasibility-in-proc-optmodel-using-milp/m-p/652376#M3125</guid>
      <dc:creator>RobPratt</dc:creator>
      <dc:date>2020-06-01T21:30:48Z</dc:date>
    </item>
  </channel>
</rss>

