Items tagged with trace

Any one know if it possible to see the steps used by the limit() function as one does with many other functions such as dsolve and int ?  This is what I tried

restart;
infolevel[limit]:=5;
interface(verboseproc=3);
limit(x^2 *log(x),x=0);

But I see no steps, only the final answer. Are not all Maple functions possible to trace? How does one know which functions can generate trace and which do not?

I am using Maple 2016.1

I wanted to see something like:

let x=1/t, hence expression becomes  (-ln t)/t^2, now taking limit as t->infinity. Applying L'Hopital rule, limit t->infinity of -1/(2 t^2) which gives zero.

I assumed this is something what Maple does internally, (but there are other ways also) and wanted to see what Maple does.

 

I understand how Browse() works. Sometimes Maple crashes or fails for some programs. Is it possible to add print("here" ) into the the mla files in the library to identify why and where Maple fails?

 

Thanks

 

Dear Friends, I work with physics paсkage. I have a quation. I don't understend how one works with metrics. For example, let:

Nice!
Very good!

1) It doesn't work. Why? (I want exactly gamma_[A,B], rather than g_[A,B], because as i guess gamma_[A,B] has a signature [1,1,1] but g_[A,B] has a signature [-1,-1,-1])

 2) And how may I see what is matrices g_[A, B], gamma_[A, B] explicitly? That is I know how to see what is g_[mu, nu], for this one needs write "g_[];".  But how may I see g_[A, B] and gamma_[A, B] in explicitly forms?

3) Why command Trace(g_[mu, nu]))  does not work?"

The following code is part of my attempt to answer the recent Question about the bifurcation of the map f:= x-> exp(x^2*(a-x)). Two very weird things are happening. They can be seen by applying trace to f. The first is that the input argument to f seems to be changed to a very large integer. The second is that for some real values of a and x, I get imaginary results from this obviously real-valued function. Why are these things happening?

restart:

f:= x-> exp(x^2*(a-x)):

trace(f):

Iterate:= proc(a, x0:= 1., n:= 2000)
local A:= hfarray(1..n, [x0]), f:= subs(:-a= a, eval(:-f));          
     #evalhf(
          proc(f, A, n)
          local k;
               for k from 2 to n do A[k]:= f(A[k-1]) end do
          end proc
          (f, A, n);
     #);
     evalf[4]~(convert(A[1000..], set))
end proc:

Iterate(1.05);

{--> enter f, args = 4607182418800017408

 

HFloat(1.0512710963760241)

 

<-- exit f (now in unknown) = 4607413323290551347}
{--> enter f, args = 4607413323290551347

 

HFloat(0.9985962074909431)

 

<-- exit f (now in unknown) = 4607169774561176020}
{--> enter f, args = 4607169774561176020

 

HFloat(1.0525960836530153)

 

Warning,  computation interrupted

 

Iterate(.75);

{--> enter f, args = 4607182418800017408

 

.754589752755861+.192678397202388*I

 

<-- exit f (now in unknown) = HFloat(0.7545897527558614)+HFloat(0.19267839720238844)*I}

Error, (in unknown) unable to store 'HFloat(0.7545897527558614)+HFloat(0.19267839720238844)*I' when datatype=float[8]

 

 

 

Download bifurcation.mw

I try to repeat lines (25)-(28) at

 

http://www.maplesoft.com/support/help/maple/view.aspx?path=Physics%2fTrace#commentform

 

I use Maple 14. However, instead of (28) I get the following result:

 

It means that Maple 14 does not perceive p_\mu, k_\nu and m as scalar quantities. I would like to ask how to define these variables correctly.

 

Thank you in advance!

I always find it difficult to debug maple codes. I'm used to the debug feature in programing laguages like C#, VB.Net, JAVA even MATLAB. They all have one thing in common which is the use of breakpoints. Breakpoints are inserted at different parts of a code so as to follow the program execution and to trace out errors. Is any similar feature in Maple? I only know the DEBUB() function and not that helpful to me.

Page 1 of 1