<?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: PSMatch Optimal Match Performance in Statistical Procedures</title>
    <link>https://communities.sas.com/t5/Statistical-Procedures/PSMatch-Optimal-Match-Performance/m-p/528922#M26723</link>
    <description>&lt;P&gt;You might try specifying "caliper=." in the match statement to see if the caliper requirement is making the optimal matching infeasible. By default a value of caliper=0.25 is used, so specifying the missing value is necessary to remove the requirement. You can also look at the plots produced by the ASSESS statement to compare the range and distribution of LPS values between the treatment and control condition to see if the caliper might be the cause.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 21 Jan 2019 22:19:44 GMT</pubDate>
    <dc:creator>MichaelL_SAS</dc:creator>
    <dc:date>2019-01-21T22:19:44Z</dc:date>
    <item>
      <title>PSMatch Optimal Match Performance</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/PSMatch-Optimal-Match-Performance/m-p/414974#M21784</link>
      <description>&lt;P&gt;I have yet to get an optimal match to run without a failure.&amp;nbsp; &amp;nbsp;If I have control with M (#cols=VC) and Treatment with N(# cols=VT) (observations, how can I estimate how much resources the optimal match will take?&amp;nbsp; &amp;nbsp;Every optimal match that I've tried&amp;nbsp; failed due to non-existence of a good match.&amp;nbsp; Most variables are binary variables, and distance is defined by LPS (log propensity score).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Obviously there are a LOT of factors that would affect the ability to create an optimal match.&amp;nbsp; Without knowing much more about my data, are there any general guidelines we should be aware of?&amp;nbsp; Are there any bounds above which an optimal match would be extremely unlikely?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here's my error:&lt;/P&gt;
&lt;P&gt;ERROR: A feasible optimal fixed ratio matching that has the specified parameters does not exist.&lt;/P&gt;
&lt;P&gt;NOTE: The data set WORK.OUTGS has 0 observations and 87 variables.&lt;/P&gt;
&lt;P&gt;NOTE: PROCEDURE PSMATCH used (Total process time):&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2017 22:08:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/PSMatch-Optimal-Match-Performance/m-p/414974#M21784</guid>
      <dc:creator>mftuchman</dc:creator>
      <dc:date>2017-11-20T22:08:13Z</dc:date>
    </item>
    <item>
      <title>Re: PSMatch Optimal Match Performance</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/PSMatch-Optimal-Match-Performance/m-p/502257#M25858</link>
      <description>I am getting the same error?  Any suggestions for troubleshooting tips? Many thanks.&lt;BR /&gt;&lt;BR /&gt;proc psmatch data=Preop&lt;BR /&gt; region=allobs;&lt;BR /&gt;class first20 diseaseseverity site surgeon left_1 female;&lt;BR /&gt;psmodel first20= age  ;&lt;BR /&gt;&lt;BR /&gt;match method=optimal(k=1) stat=lps caliper=0.9;&lt;BR /&gt;&lt;BR /&gt;assess lps var=(age   ) / weight=none plots=(boxplot barchart);&lt;BR /&gt;output out(obs=all)=Outgs lps=_Lps matchid=_MatchID;</description>
      <pubDate>Sun, 07 Oct 2018 14:45:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/PSMatch-Optimal-Match-Performance/m-p/502257#M25858</guid>
      <dc:creator>mhtoto</dc:creator>
      <dc:date>2018-10-07T14:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: PSMatch Optimal Match Performance</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/PSMatch-Optimal-Match-Performance/m-p/528922#M26723</link>
      <description>&lt;P&gt;You might try specifying "caliper=." in the match statement to see if the caliper requirement is making the optimal matching infeasible. By default a value of caliper=0.25 is used, so specifying the missing value is necessary to remove the requirement. You can also look at the plots produced by the ASSESS statement to compare the range and distribution of LPS values between the treatment and control condition to see if the caliper might be the cause.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jan 2019 22:19:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/PSMatch-Optimal-Match-Performance/m-p/528922#M26723</guid>
      <dc:creator>MichaelL_SAS</dc:creator>
      <dc:date>2019-01-21T22:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: PSMatch Optimal Match Performance</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/PSMatch-Optimal-Match-Performance/m-p/590571#M28877</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am facing the similar issue with both OPTIMAL and VARRATIO matching. Is there any method to change the caliper value for optimal with fixed/variable ratio matching. The issue with default value of 0.25 is - it does not give balanced cohorts. Can you suggest me something on this?&lt;/P&gt;</description>
      <pubDate>Sat, 21 Sep 2019 05:10:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/PSMatch-Optimal-Match-Performance/m-p/590571#M28877</guid>
      <dc:creator>KK_Mangla</dc:creator>
      <dc:date>2019-09-21T05:10:06Z</dc:date>
    </item>
  </channel>
</rss>

