<?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: Fast way to check for &amp;quot;wrong sensordata&amp;quot; in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/380180#M63043</link>
    <description>&lt;P&gt;Yet another idea:&amp;nbsp; If you know the bad data is always a negative number, or below some specific value, you could make a new column which is 1 if the values is 'bad' and then use tabulate to show the number of bad values for each level of KW.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Apr 2021 18:51:19 GMT</pubDate>
    <dc:creator>ih</dc:creator>
    <dc:date>2021-04-27T18:51:19Z</dc:date>
    <item>
      <title>Fast way to check for "wrong sensordata"</title>
      <link>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/378120#M62788</link>
      <description>&lt;P&gt;I have many different sensors (&amp;gt;&amp;gt;100) with many Data (continuous) each (&amp;gt;1mio) and update these each week.&lt;/P&gt;&lt;P&gt;Sometimes these sensors "glitch" and send wrong data (below/above a low/high threshold)&lt;/P&gt;&lt;P&gt;I want to calculate the number of "glitches" per week (KW=categorial) and need a fast way by JSL code.&lt;/P&gt;&lt;P&gt;Example: negative data for this sensor should be detected (low threshold 0)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MWalther_0-1618900705046.png" style="width: 400px;"&gt;&lt;img src="https://community.jmp.com/t5/image/serverpage/image-id/32198i25EC7004E7C5A7AA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MWalther_0-1618900705046.png" alt="MWalther_0-1618900705046.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;My Solutions are too slow:&lt;BR /&gt;1.) I set the threshold limits as "specification" in column properties and then perform process capability&lt;BR /&gt;"Observed outside" Spec per KW is the desired value, but it is quite slow&lt;/P&gt;&lt;P&gt;2.) Brute force: each row, each column, manual check, adding each cell (Excel style) takes forever.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a more efficient way to do this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 22:11:28 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/378120#M62788</guid>
      <dc:creator>MWalther</dc:creator>
      <dc:date>2023-06-09T22:11:28Z</dc:date>
    </item>
    <item>
      <title>Re: Fast way to check for "wrong sensordata"</title>
      <link>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/378263#M62807</link>
      <description>&lt;P&gt;I suggest that you use the Range Check column property.&amp;nbsp; It is quite efficient.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Apr 2021 13:07:07 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/378263#M62807</guid>
      <dc:creator>txnelson</dc:creator>
      <dc:date>2021-04-20T13:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: Fast way to check for "wrong sensordata"</title>
      <link>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/378305#M62811</link>
      <description>&lt;P&gt;In addition to&amp;nbsp;&lt;a href="https://community.jmp.com/t5/user/viewprofilepage/user-id/2687"&gt;@txnelson&lt;/a&gt;&amp;nbsp;'s suggestion, have you tried out the Explore Outliers utility as a means to finding the rows containing the suspicious observations? Here's a link to the utility in JMP documentation:&amp;nbsp;&lt;A href="https://www.jmp.com/support/help/en/15.2/index.shtml#page/jmp/launch-the-explore-outliers-utility.shtml" target="_self"&gt;Explore Outliers Utility&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Apr 2021 14:03:20 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/378305#M62811</guid>
      <dc:creator>P_Bartell</dc:creator>
      <dc:date>2021-04-20T14:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: Fast way to check for "wrong sensordata"</title>
      <link>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/379201#M62918</link>
      <description>&lt;P&gt;Thanks, sounds feasible.&lt;BR /&gt;So the way to go is use range check to set all data to missing, which do not comply, and the do a tabulate to "count" the missing values per calenderweek.&lt;/P&gt;&lt;P&gt;The only drawback ist, that all "wrong" data then are lost in the original data table.&lt;BR /&gt;I will need to use a copy, or is there a way to retrieve the (then) missing data in the original table?&lt;/P&gt;&lt;P&gt;Yours, Marten&lt;/P&gt;</description>
      <pubDate>Fri, 23 Apr 2021 09:16:45 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/379201#M62918</guid>
      <dc:creator>MWalther</dc:creator>
      <dc:date>2021-04-23T09:16:45Z</dc:date>
    </item>
    <item>
      <title>Re: Fast way to check for "wrong sensordata"</title>
      <link>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/380180#M63043</link>
      <description>&lt;P&gt;Yet another idea:&amp;nbsp; If you know the bad data is always a negative number, or below some specific value, you could make a new column which is 1 if the values is 'bad' and then use tabulate to show the number of bad values for each level of KW.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Apr 2021 18:51:19 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/380180#M63043</guid>
      <dc:creator>ih</dc:creator>
      <dc:date>2021-04-27T18:51:19Z</dc:date>
    </item>
    <item>
      <title>Re: Fast way to check for "wrong sensordata"</title>
      <link>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/380318#M63066</link>
      <description>You will need to create a complete Subset&lt;BR /&gt;     Tables=&amp;gt;Subset</description>
      <pubDate>Wed, 28 Apr 2021 03:42:04 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Fast-way-to-check-for-quot-wrong-sensordata-quot/m-p/380318#M63066</guid>
      <dc:creator>txnelson</dc:creator>
      <dc:date>2021-04-28T03:42:04Z</dc:date>
    </item>
  </channel>
</rss>

