HP Prime undef for Limes. Maybe a Bug?

10102018, 08:58 PM
Post: #1




HP Prime undef for Limes. Maybe a Bug?
Hello
I try to calculate the limit for a certain expression. Unfortunately i dont get a result with the prime. It should be 0.285 See here: https://www.symbolab.com/solver/limitca...D%5Cright) Do i have to set some settings? Or what can i do to solve the problem? Thank you 

10102018, 09:32 PM
Post: #2




RE: HP Prime undef for Limes. Maybe a Bug?  
10112018, 06:47 AM
Post: #3




RE: HP Prime undef for Limes. Maybe a Bug?
THank you so much!
I never thought that decimal numbers could be a problem. Is there an obvious reason to not allow decimal numbers or to force the user to enter it as a fraction? Just for others: you can also use exact(2.5) instead of 25/10. It should not be very hard for the HPTeam to implement the usage of the exact function behind the lim operation. Anyway thank you very much Now i can do the excercises from our math lessons... 

10112018, 07:01 AM
Post: #4




RE: HP Prime undef for Limes. Maybe a Bug?
Of course there is a reason:)
The reason is that limit requires exact input to make simplifications (this is required here otherwise you get 0.0/0.0 or 0/0), with approx input, you could have rounding errors. 

10112018, 07:05 AM
Post: #5




RE: HP Prime undef for Limes. Maybe a Bug?
Ok i see
I also understand the requirement for exact inputs. But sometimes, 2.5 is already exact as possible ^^ Here i would be happy if the HP would automatically convert the input to an exact fraction by themself. 

10112018, 08:39 AM
Post: #6




RE: HP Prime undef for Limes. Maybe a Bug?
I got an answer in the oficcial HP Forum.
There is also an even simpler way to do this. You first enter the "unexact" form of the lim with 2.5 Then press enter. You get the undef answer Now click on the lim in the history once and then press the a b/c key. Now you see a converted version of the expression. Click the converted expression and press enter twice. Now you see the correct result. 

10112018, 10:22 AM
(This post was last modified: 10112018 10:24 AM by Tim Wessman.)
Post: #7




RE: HP Prime undef for Limes. Maybe a Bug?
Glad my answer over there was helpful.
Really is more just a way to quickly get to "exact" forms when you have decimals to ensure the cas behaves nicely when decimals are involved. TW Although I work for HP, the views and opinions I post here are my own. 

10122018, 06:17 AM
Post: #8




RE: HP Prime undef for Limes. Maybe a Bug?
(10112018 07:05 AM)blevita Wrote: Ok i see This is dangerous. I added automatic conversion of floating points that look like integers (I mean for example 2.0, that looks like the integer 2 especially in Home), but 2.5 is *never* considered to be exact in the CAS, it might represent any real in a small interval around 2.5. If 2.5 is exact in your problem, you must enter it as 5/2. 

10122018, 03:11 PM
Post: #9




RE: HP Prime undef for Limes. Maybe a Bug?
You can always make a CAS program to do that, such as:
Code: #cas limit_exact(((52*x)/(2*x^23*x5)),x,2.5,0) will return 2/7. road 

10122018, 08:08 PM
Post: #10




RE: HP Prime undef for Limes. Maybe a Bug?
(10122018 03:11 PM)roadrunner Wrote: You can always make a CAS program to do that, such as: It works only if I subst retrun with return ;) VPN 

10132018, 07:04 PM
Post: #11




RE: HP Prime undef for Limes. Maybe a Bug?
Hi, roadrunner
On your limit_exact(), why is subst(...) needed ? Also, I think limit_exact() had a bug: f(x) := ((52x) + sin(52x)) / (2x^2  3x  5) limit(f(x), x, 5/2, 0) ==> 4/7 limit_exact(f(x), x, 2.5, 0) ==> undef limit_exact(f(x), x, 5/2, 0) ==> undef BTW, exact(...) may not always return exactly what you wanted. Returned rationals were an approximation (based on config epsilon setting) of float. Example, with epsilon = 1e6, exact(500000.5) return 500001 

10142018, 12:18 AM
Post: #12




RE: HP Prime undef for Limes. Maybe a Bug?
Hi Albert,
You are right. It's not working for your function, f(x). The call to limit in the function seems to be getting the second parameter incorrectly. I'm not sure why; it seems to be getting a "b" instead an "x" I thought using the subst command fixed that, but apparently not in all cases. road 

10142018, 01:42 AM
(This post was last modified: 10142018 02:46 AM by Albert Chan.)
Post: #13




RE: HP Prime undef for Limes. Maybe a Bug?
This work, but first argument had to be function of 1 argument ...
Code: limit_exact(f, v, d) := 

10142018, 02:17 PM
Post: #14




RE: HP Prime undef for Limes. Maybe a Bug?
Check out this version:
Code: #cas Now, f(x) := ((52x) + sin(52x)) / (2x^2  3x  5) limit_exact(f(x), x, 2.5, 0) returns 4/7 limit_exact(f(t), t, 2.5, 0) also returns 4/7 It should work with any independent variable. road 

10142018, 04:29 PM
Post: #15




RE: HP Prime undef for Limes. Maybe a Bug?
(10142018 02:17 PM)roadrunner Wrote: Check out this version: Great!  No coyote can catch you! 

10142018, 04:58 PM
Post: #16




RE: HP Prime undef for Limes. Maybe a Bug?
Hi, roadrunner
I suggest not using x for the symbolic local variable. Preferably some name that will never be used ... limit_exact(x + y, x, 1, 0) ==> y+1, OK limit_exact(x + y, y, 1, 0) ==> 2, BAD 

10152018, 12:04 PM
Post: #17




RE: HP Prime undef for Limes. Maybe a Bug?  
10162018, 09:35 PM
Post: #18




RE: HP Prime undef for Limes. Maybe a Bug?
(10142018 04:58 PM)Albert Chan Wrote: Hi, roadrunner Code:
Try that with any example. CHAR(172) is that "hook" character. 

« Next Oldest  Next Newest »

User(s) browsing this thread: 1 Guest(s)