<?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: Understanding of MIP iteration approach in SAS Risk Management</title>
    <link>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/494075#M271</link>
    <description>&lt;P&gt;Thanks a lot for clarification, Andy!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Dmitry&lt;/P&gt;</description>
    <pubDate>Mon, 10 Sep 2018 10:23:48 GMT</pubDate>
    <dc:creator>DmitryErshov</dc:creator>
    <dc:date>2018-09-10T10:23:48Z</dc:date>
    <item>
      <title>Understanding of MIP iteration approach</title>
      <link>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/488871#M264</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question is about SAS MIP 2.4.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a test portfolio with 2 dates for 3 loans (01JUL and 01AUG), so I have 6 records in portfolio DS. I have economics scenario data set with only one (base) scenario. My As-of-date is 01JUL, Monte Carlo simulation is disabled, and number of horizons to simulate is 1. I created the following simple UDL to see MIP iteration approach:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;BEGINBLOCK LOAN_INIT;													
ENDBLOCK;

BEGINBLOCK MAIN;
	if (simulationhorizon eq 0) then do;		
	end; else do;
	end;
	
        put "SIMULATION_HORIZON=" simulationhorizon;
        put "InstId=" InstId;
        put "MCSimulationRep=" MCSimulationRep;
            		
	_VALUE_ = 1.0; 
ENDBLOCK;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;As a result I got the following output in log:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L2&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;/P&gt;&lt;P&gt;InstId= L2&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L3&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L3&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L2&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L2&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L2&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L2&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L3&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L3&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L3&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L3&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;But according to documentation I expected to see the following:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;SIMULATION_HORIZON= 0&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;InstId= L2&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;MCSimulationRep= 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L2&lt;BR /&gt;MCSimulationRep= 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L3&lt;BR /&gt;MCSimulationRep= 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;SIMULATION_HORIZON= 1&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;InstId= L3&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;MCSimulationRep= 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why does MIP perform so many iterations with the same combination of SIMULATION_HORIZON and InstId?&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Aug 2018 13:45:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/488871#M264</guid>
      <dc:creator>pierrevanstulov</dc:creator>
      <dc:date>2018-08-22T13:45:10Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding of MIP iteration approach</title>
      <link>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/489279#M265</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have been investigating your question, and I suspect that you have duplicate values for InstId&amp;nbsp;in your portfolio dataset and the values are required to be unique. Please check, correct and retest your portfolio dataset if that is the case.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;If you are still having issues, please open a SAS Technical Support track (link below) and I will investigate further.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.sas.com/en/support-home.html" target="_blank"&gt;https://support.sas.com/en/support-home.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Andy&lt;/P&gt;</description>
      <pubDate>Thu, 23 Aug 2018 14:26:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/489279#M265</guid>
      <dc:creator>AMSAS</dc:creator>
      <dc:date>2018-08-23T14:26:52Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding of MIP iteration approach</title>
      <link>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/491166#M269</link>
      <description>&lt;P&gt;Hi, Andy!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for reply. You are right. We can't load data for several dates to portfolio data set. After I removed duplicate values the&amp;nbsp;output was much more expectable:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#ff0000"&gt;&lt;STRONG&gt;SIMULATION_HORIZON= 0&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#ff0000"&gt;&lt;STRONG&gt;InstId= L1&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#ff0000"&gt;&lt;STRONG&gt;MCSimulationRep= 1&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;FONT color="#ff0000"&gt;&lt;STRONG&gt;SIMULATION_HORIZON= 0&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#ff0000"&gt;&lt;STRONG&gt;InstId= L2&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#ff0000"&gt;&lt;STRONG&gt;MCSimulationRep= 1&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L1&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SIMULATION_HORIZON= 0&lt;BR /&gt;InstId= L2&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SIMULATION_HORIZON= 1&lt;BR /&gt;InstId= L2&lt;BR /&gt;MCSimulationRep= 1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But, one question remains: &lt;STRONG&gt;why does&amp;nbsp;MIP iterate through all loans at SIMULATION_HORIZON = 0 (these iterations highlited with red &lt;FONT color="#ff0000"&gt;color&lt;/FONT&gt;)?&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Dmitry&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 11:11:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/491166#M269</guid>
      <dc:creator>DmitryErshov</dc:creator>
      <dc:date>2018-08-30T11:11:51Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding of MIP iteration approach</title>
      <link>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/493381#M270</link>
      <description>&lt;P&gt;Hi &lt;SPAN&gt;Dmitry,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Sorry for the delay getting back on this question - I've been testing and researching the answer&lt;BR /&gt;&lt;BR /&gt;SAS &amp;amp;reg Model Implementation Platform, generates and executes SAS &amp;amp;reg High-Performance Risk code. The behavior you are seeing is legacy code from SAS HP Risk. Customers who used earlier releases of HP Risk, used this behavior in their User Defined Logic, so to insure their UDL did not break in newer versions the behavior was maintained.&lt;BR /&gt;&lt;BR /&gt;There is a automatic variable that you can print to the log (_BASELINE_), for your 2 log lines in red this will be set to 0 (zero) and then&amp;nbsp;set to 1 for all&amp;nbsp;the remaining lines.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Andy&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2018 12:45:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/493381#M270</guid>
      <dc:creator>AMSAS</dc:creator>
      <dc:date>2018-09-07T12:45:46Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding of MIP iteration approach</title>
      <link>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/494075#M271</link>
      <description>&lt;P&gt;Thanks a lot for clarification, Andy!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Dmitry&lt;/P&gt;</description>
      <pubDate>Mon, 10 Sep 2018 10:23:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Risk-Management/Understanding-of-MIP-iteration-approach/m-p/494075#M271</guid>
      <dc:creator>DmitryErshov</dc:creator>
      <dc:date>2018-09-10T10:23:48Z</dc:date>
    </item>
  </channel>
</rss>

