<?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: SavePredicteds is slow and wrong in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/SavePredicteds-is-slow-and-wrong/m-p/666633#M85469</link>
    <description>&lt;P&gt;Try adding a Wait(0) to force separation between the two sections - I believe that would be sufficient.&amp;nbsp; The issue is that versions of JMP prior to JMP 17 run the initial analysis on the full data prior to applying the filter.&amp;nbsp; Some platforms will still do that, but starting in JMP 17 Bivariate and others that are designed to work with empty tables will apply the filter on the first pass.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Aug 2023 13:49:46 GMT</pubDate>
    <dc:creator>danschikore</dc:creator>
    <dc:date>2023-08-08T13:49:46Z</dc:date>
    <item>
      <title>SavePredicteds is slow and wrong</title>
      <link>https://community.jmp.com/t5/Discussions/SavePredicteds-is-slow-and-wrong/m-p/666620#M85468</link>
      <description>&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;		// section 1
		bivar = dt &amp;lt;&amp;lt; Bivariate( Y( :PolarRadius ), X( :PolarThetaRound ),
			Fit Spline( 0.008, {Line Color( {212, 73, 88} )} ),
			Local Data Filter( Add Filter( columns( :PolarRadius, :i ),
					Where( :PolarRadius &amp;gt;= 22.5 &amp;amp; :PolarRadius &amp;lt;= 26.5 ),
					Where( :i &amp;gt;= 0.4 &amp;amp; :i &amp;lt;= 0.41 )
				)
			)
		);
		
		//	section 2
		bivar &amp;lt;&amp;lt; (curve[1] &amp;lt;&amp;lt; savePredicteds);&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;I am using JMP 14.3.0 on Windows 10. I am working in a table with 5M rows - a photograph of a disc, I am trying to find the edge. When I run the above code as one block, it takes over two minutes and the new column ("Spline Predictor for PolarRadius") is full of incorrect values; the formula for the column includes an array [9980x5].&amp;nbsp; If I run section 1 alone, it takes a 5 seconds.&amp;nbsp; And then if I run section 2 alone, it takes 2 seconds, and the new column is correct and includes an array 10x smaller: [971x5].&amp;nbsp; I have tried inserting a few lines between section 1 and 2, but nothing changes.&amp;nbsp; How do I get that "SavePredicteds" function to do the right thing without babysitting it?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Aug 2023 13:31:10 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/SavePredicteds-is-slow-and-wrong/m-p/666620#M85468</guid>
      <dc:creator>mann</dc:creator>
      <dc:date>2023-08-08T13:31:10Z</dc:date>
    </item>
    <item>
      <title>Re: SavePredicteds is slow and wrong</title>
      <link>https://community.jmp.com/t5/Discussions/SavePredicteds-is-slow-and-wrong/m-p/666633#M85469</link>
      <description>&lt;P&gt;Try adding a Wait(0) to force separation between the two sections - I believe that would be sufficient.&amp;nbsp; The issue is that versions of JMP prior to JMP 17 run the initial analysis on the full data prior to applying the filter.&amp;nbsp; Some platforms will still do that, but starting in JMP 17 Bivariate and others that are designed to work with empty tables will apply the filter on the first pass.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Aug 2023 13:49:46 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/SavePredicteds-is-slow-and-wrong/m-p/666633#M85469</guid>
      <dc:creator>danschikore</dc:creator>
      <dc:date>2023-08-08T13:49:46Z</dc:date>
    </item>
  </channel>
</rss>

