<?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 PLS model develpment and predict in Statistical Procedures</title>
    <link>https://communities.sas.com/t5/Statistical-Procedures/PLS-model-develpment-and-predict/m-p/610484#M29566</link>
    <description>&lt;P&gt;Hello, I am building a PLS model using training dataset, and also have a dataset to do prediction (prediction dataset).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The training dataset is finalized and then the model configuration has been fixed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The prediction dataset is updated everyday, and this is reason why the datasets are managed separately.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issue is how can I code PLS procedure for this task.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The model code I am using is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PROC PLS CV=ONE DATA=&amp;amp;EM_IMPORT_DATA METHOD=PLS NOCENTER NOSCALE NFAC=6 MISSING=AVG;&lt;BR /&gt;&amp;nbsp;MODEL &amp;amp;Y1 = &amp;amp;X1 &amp;amp;X2 &amp;amp;X3 &amp;amp;X4 &amp;amp;X5 &amp;amp;X6 &amp;amp;X7 &amp;amp;X8 &amp;amp;X9 &amp;amp;X10 &amp;amp;X11 &amp;amp;X12 &amp;amp;X13;&lt;BR /&gt;QUIT;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is a complicated model and &amp;amp;Y1 have five variables, similar setting for &amp;amp;X1 and etc (using let to define &amp;amp;X1 ....&amp;amp;Y1).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The prediction dataset has same structure, but how can set&amp;nbsp;the prediction for prediction dataset?&amp;nbsp;&amp;nbsp;(prefer not to merge the training dataset and prediction dataset)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks&lt;/P&gt;</description>
    <pubDate>Mon, 09 Dec 2019 14:40:55 GMT</pubDate>
    <dc:creator>Jonison</dc:creator>
    <dc:date>2019-12-09T14:40:55Z</dc:date>
    <item>
      <title>PLS model develpment and predict</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/PLS-model-develpment-and-predict/m-p/610484#M29566</link>
      <description>&lt;P&gt;Hello, I am building a PLS model using training dataset, and also have a dataset to do prediction (prediction dataset).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The training dataset is finalized and then the model configuration has been fixed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The prediction dataset is updated everyday, and this is reason why the datasets are managed separately.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issue is how can I code PLS procedure for this task.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The model code I am using is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PROC PLS CV=ONE DATA=&amp;amp;EM_IMPORT_DATA METHOD=PLS NOCENTER NOSCALE NFAC=6 MISSING=AVG;&lt;BR /&gt;&amp;nbsp;MODEL &amp;amp;Y1 = &amp;amp;X1 &amp;amp;X2 &amp;amp;X3 &amp;amp;X4 &amp;amp;X5 &amp;amp;X6 &amp;amp;X7 &amp;amp;X8 &amp;amp;X9 &amp;amp;X10 &amp;amp;X11 &amp;amp;X12 &amp;amp;X13;&lt;BR /&gt;QUIT;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is a complicated model and &amp;amp;Y1 have five variables, similar setting for &amp;amp;X1 and etc (using let to define &amp;amp;X1 ....&amp;amp;Y1).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The prediction dataset has same structure, but how can set&amp;nbsp;the prediction for prediction dataset?&amp;nbsp;&amp;nbsp;(prefer not to merge the training dataset and prediction dataset)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2019 14:40:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/PLS-model-develpment-and-predict/m-p/610484#M29566</guid>
      <dc:creator>Jonison</dc:creator>
      <dc:date>2019-12-09T14:40:55Z</dc:date>
    </item>
    <item>
      <title>Re: PLS model develpment and predict</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/PLS-model-develpment-and-predict/m-p/611031#M29573</link>
      <description>&lt;P&gt;Some regression procedures support the STORE statement, which creates an item store for &lt;A href="https://blogs.sas.com/content/iml/2014/02/19/scoring-a-regression-model-in-sas.html" target="_self"&gt;future scoring by using the PLM procedure&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Unfortunately, the PLM procedure does not support the STORE statement, so I think your only choice is to &lt;A href="https://blogs.sas.com/content/iml/2014/02/17/the-missing-value-trick-for-scoring-a-regression-model.html" target="_self"&gt;use the missing response trick&lt;/A&gt;, which unfortunately requires concatenating the new data with the original. &lt;A href="https://go.documentation.sas.com/?docsetId=statug&amp;amp;docsetVersion=15.1&amp;amp;docsetTarget=statug_pls_gettingstarted01.htm&amp;amp;locale=en" target="_self"&gt;The Getting Started example&lt;/A&gt; in the PLS doc has an example of scoring.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Dec 2019 15:00:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/PLS-model-develpment-and-predict/m-p/611031#M29573</guid>
      <dc:creator>Rick_SAS</dc:creator>
      <dc:date>2019-12-11T15:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: PLS model develpment and predict</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/PLS-model-develpment-and-predict/m-p/611994#M29596</link>
      <description>&lt;P&gt;Thanks for your kind reply. I think this would be the solution to current version.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2019 11:48:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/PLS-model-develpment-and-predict/m-p/611994#M29596</guid>
      <dc:creator>Jonison</dc:creator>
      <dc:date>2019-12-16T11:48:40Z</dc:date>
    </item>
  </channel>
</rss>

