<rss xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" version="2.0">
  <channel>
    <title>MaplePrimes - answers and comments on Question, Problem by plotting of a function</title>
    <link>http://www.mapleprimes.com/questions/144546-Problem-By-Plotting-Of-A-Function</link>
    <language>en-us</language>
    <copyright>2026 Maplesoft, A Division of Waterloo Maple Inc.</copyright>
    <generator>Maplesoft Document System</generator>
    <lastBuildDate>Wed, 10 Jun 2026 19:00:44 GMT</lastBuildDate>
    <pubDate>Wed, 10 Jun 2026 19:00:44 GMT</pubDate>
    <itunes:subtitle />
    <itunes:summary />
    <description>The latest answers and comments added to the Question, Problem by plotting of a function</description>
    <image>
      <url>http://www.mapleprimes.com/images/mapleprimeswhite.jpg</url>
      <title>MaplePrimes - answers and comments on Question, Problem by plotting of a function</title>
      <link>http://www.mapleprimes.com/questions/144546-Problem-By-Plotting-Of-A-Function</link>
    </image>
    <item>
      <title>numeric error</title>
      <link>http://www.mapleprimes.com/questions/144546-Problem-By-Plotting-Of-A-Function?ref=Feed:MaplePrimes:Problem by plotting of a function:Comments#answer144548</link>
      <itunes:summary>&lt;p&gt;The problem is numeric (floating-point) evaluation error. Under the fast (hardware float) `evalhf` interpreter your `L` evaluates to Float(undefined) for values of `k` closer to 100.&lt;/p&gt;
&lt;p&gt;Even under regular (software float) `evalf` there are numeric issues when done at lower working precision (ie. Digits).&lt;/p&gt;
&lt;p&gt;There are several ways around this. The attached worksheet shows three related and relatively simple ways of getting around it by avoiding evalhf mode computation.&lt;/p&gt;
&lt;p&gt;&lt;a href="/view.aspx?sf=144548/455961/error1.mw"&gt;Download error1.mw&lt;/a&gt;&lt;/p&gt;
&lt;form name="worksheet_form"&gt;&lt;/form&gt;&lt;!--break--&gt;
&lt;p&gt;acer&lt;/p&gt;</itunes:summary>
      <description>&lt;p&gt;The problem is numeric (floating-point) evaluation error. Under the fast (hardware float) `evalhf` interpreter your `L` evaluates to Float(undefined) for values of `k` closer to 100.&lt;/p&gt;
&lt;p&gt;Even under regular (software float) `evalf` there are numeric issues when done at lower working precision (ie. Digits).&lt;/p&gt;
&lt;p&gt;There are several ways around this. The attached worksheet shows three related and relatively simple ways of getting around it by avoiding evalhf mode computation.&lt;/p&gt;
&lt;p&gt;&lt;a href="/view.aspx?sf=144548/455961/error1.mw"&gt;Download error1.mw&lt;/a&gt;&lt;/p&gt;
&lt;form name="worksheet_form"&gt;&lt;/form&gt;&lt;!--break--&gt;
&lt;p&gt;acer&lt;/p&gt;</description>
      <guid>144548</guid>
      <pubDate>Wed, 13 Mar 2013 13:36:30 Z</pubDate>
      <itunes:author>acer</itunes:author>
      <author>acer</author>
    </item>
    <item>
      <title>Thank you for your quick answer, it was very</title>
      <link>http://www.mapleprimes.com/questions/144546-Problem-By-Plotting-Of-A-Function?ref=Feed:MaplePrimes:Problem by plotting of a function:Comments#comment144549</link>
      <itunes:summary>&lt;p&gt;Thank you for your quick answer, it was very useful.&lt;/p&gt;
&lt;p&gt;Best,&lt;/p&gt;
&lt;p&gt;ssteve&lt;/p&gt;</itunes:summary>
      <description>&lt;p&gt;Thank you for your quick answer, it was very useful.&lt;/p&gt;
&lt;p&gt;Best,&lt;/p&gt;
&lt;p&gt;ssteve&lt;/p&gt;</description>
      <guid>144549</guid>
      <pubDate>Wed, 13 Mar 2013 13:52:02 Z</pubDate>
      <itunes:author>ssteve</itunes:author>
      <author>ssteve</author>
    </item>
  </channel>
</rss>