<?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: intersection points in LabVIEW</title>
    <link>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312524#M161908</link>
    <description>&lt;P&gt;One other method of finding intersections is to use a crossover analysis (assuming 2 functions are continuous), that is given a pair of points from each graph if the first point of graph A (X11, Y11) is greater than the first point of graph 2 (X21, Y21) but the case is flipped in the second point (X12, Y12) vs (X22, Y22) the there must be a crossover (intersection) between them, interpolation might give you a better guess at the exact location.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 18 Jan 2006 18:32:44 GMT</pubDate>
    <dc:creator>falkpl</dc:creator>
    <dc:date>2006-01-18T18:32:44Z</dc:date>
    <item>
      <title>intersection points</title>
      <link>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312273#M161797</link>
      <description>&lt;DIV&gt;hello. I'm looking for a solution for this problem: There are two continuous graphs which are plotted and displayed in one graph indicator.&amp;nbsp;Now, what&amp;nbsp;I need are&amp;nbsp;all intersection points&amp;nbsp;stored in an own&amp;nbsp;array. Is there a way to manage this problem in LabVIEW 7.1? &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Please help me. THX!&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Jan 2006 12:33:57 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312273#M161797</guid>
      <dc:creator>0123</dc:creator>
      <dc:date>2006-01-18T12:33:57Z</dc:date>
    </item>
    <item>
      <title>Re: intersection points</title>
      <link>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312278#M161801</link>
      <description>&lt;DIV&gt;i don't see a function in LV that you can find the intersection...&lt;/DIV&gt;
&lt;DIV&gt;if you can't find one either, try using a loop to get the intersection yourself&lt;/DIV&gt;
&lt;DIV&gt;depending on the size of the array, this might be slow&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Jan 2006 12:50:22 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312278#M161801</guid>
      <dc:creator>Elsa Fung</dc:creator>
      <dc:date>2006-01-18T12:50:22Z</dc:date>
    </item>
    <item>
      <title>Re: intersection points</title>
      <link>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312319#M161822</link>
      <description>Elsa's approach will not work if the intersection is not an exact equality.  For example if you had arrays representing two (non-parallel) straight lines which intersected between ponits in the array the equality test would not find it.&lt;BR /&gt;&lt;BR /&gt;A shift register and a subtraction might work.  If the sign of the difference between the arrays changes between elements [i] and [i+1], the intersecton is also between those elements.  I have not tried this nor thought it through carefully, so it may not work in all cases.  For signals which intersect multiple times {sin(x), cos(x)} the result will be an array of intersections.&lt;BR /&gt;&lt;BR /&gt;Lynn</description>
      <pubDate>Wed, 18 Jan 2006 13:39:31 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312319#M161822</guid>
      <dc:creator>johnsold</dc:creator>
      <dc:date>2006-01-18T13:39:31Z</dc:date>
    </item>
    <item>
      <title>Re: intersection points</title>
      <link>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312325#M161826</link>
      <description>&lt;P&gt;Just like float comparisons, you will not get an exact match but you can get "intersections by setting the distance between points to be less than some minimum value.&amp;nbsp; also depending on the functions, you might beable to solve the equality equations and find the zero points.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Paul&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Jan 2006 13:43:19 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312325#M161826</guid>
      <dc:creator>falkpl</dc:creator>
      <dc:date>2006-01-18T13:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: intersection points</title>
      <link>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312326#M161827</link>
      <description>&lt;P&gt;Just like float comparisons, you will not get an exact match but you can get "intersections by setting the distance between points to be less than some minimum value.&amp;nbsp; also depending on the functions, you might beable to solve the equality equations and find the zero points.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Paul&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Jan 2006 13:43:20 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312326#M161827</guid>
      <dc:creator>falkpl</dc:creator>
      <dc:date>2006-01-18T13:43:20Z</dc:date>
    </item>
    <item>
      <title>Re: intersection points</title>
      <link>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312499#M161896</link>
      <description>you can autoindex one array and call search 1D array function within&lt;BR /&gt;
For loop.&lt;BR /&gt;
It's true that speed depends upon array size, but seems from your&lt;BR /&gt;
attachment that by autoindexing both arrays you only compared the&lt;BR /&gt;
numbers with SAME index in two arrays, is that what you called&lt;BR /&gt;
intersection?&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Jan 2006 17:40:47 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312499#M161896</guid>
      <dc:creator>chenny</dc:creator>
      <dc:date>2006-01-18T17:40:47Z</dc:date>
    </item>
    <item>
      <title>Re: intersection points</title>
      <link>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312524#M161908</link>
      <description>&lt;P&gt;One other method of finding intersections is to use a crossover analysis (assuming 2 functions are continuous), that is given a pair of points from each graph if the first point of graph A (X11, Y11) is greater than the first point of graph 2 (X21, Y21) but the case is flipped in the second point (X12, Y12) vs (X22, Y22) the there must be a crossover (intersection) between them, interpolation might give you a better guess at the exact location.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Jan 2006 18:32:44 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/intersection-points/m-p/312524#M161908</guid>
      <dc:creator>falkpl</dc:creator>
      <dc:date>2006-01-18T18:32:44Z</dc:date>
    </item>
  </channel>
</rss>

