Hello all ... FYI, our site master Will Spaetzel is getting married this weekend. Please join me in congratulating him and his new bride Laura-Lee on their new life together! Many happy wishes to you two! The bad news is, during his absence (for a couple of weeks), some technical issues with this site may be a bit slower in resolving. We have back-up editors for Will but Will has special talents that are hard to match. Thanks for your patience. Tom 4.

Hello all, I'm new here and I don't know if it is the right place to report a bug. I do not own Maple by myself, I'm just using our campus-net installation of Maple 9. I have no access to more recent versions right now. I was typing a functioning old Maple 4 sheet, but got a different result with Maple 9 (see below)! However, I found to introduce a simplify() before the int()-call fixes the problem (see last command). Do higher versions of Maple have the same problem with this code? Thanks, Klaus > restart: with(linalg): Warning, the protected names norm and trace have been redefined and

I have just released the new version of the FourierTrigSeries package. Some bugs were fixed and new procedures were added. This package provides new data structure for the representation of trigonometric series and also several procedures to manipulate with trigonometric series and to compute Fourier series. Previous package name FourierSeries was changed to FourierTrigSeries to be distinguished from the FourierSeries package made by Wilhelm Werner.

I have the following:

>                 /             /         2          \\    
>              1  | 2    2      |/ 2    2\       2  2||    
>       eqn := - +\b  + a , sqrt\\b  + a /  - 4 a  c // - c
>              2                                           
                                                     (1/2)    
        1  2   1  2   1 / 4      2  2    4      2  2\         
 eqn := - b  + - a  + - \b  + 2 b  a  + a  - 4 a  c /      - c
        2      2      2                                       
>                          solve(eqn, c)
                               2    2

Here are some possible bugs or limitations that I have come across while working with Tensors in the new physics package. I have done best of my efforts looking into the documentation, but it is still possible that the bugs I am listing are not bugs at all but outcome of lack of my knowledge in using Maple. My intention of creating this blog is to not to criticize but to help the Physics package development team in making updates. I appreciate their efforts for developing a much needed package for areas like fluid mechanics, continuum mechanics, theory relativity etc. Platform I am using: Maple Ver 11.01 on Mac OS X 10.4.10

On Monday, Aug. 13, I will be at a big optimization conference at McMaster University in Hamilton, Ontario. It's the joint International Conference on Continuous Optimization (ICCOPT) and Modeling and Optimization: Theory and Applications (MOPTA) conference. I'll be running a session with three Maple-related talks given by Jan Bakus of Maplesoft, Andrew Curtis of the University of Western Ontario, and myself. If any of you are attending the conference (and I

Here's a question I was asked very recently: "When creating a plot, is it possible to specify the points at which the input expression should be evaluated?" The answer is "yes" for 2-D plots, and this is done with the 'sample' option. Use the command plot(f(x), x=a..b, sample=[x1, x2, ..., xn]) to have f(x) evaluated at points x1, x2, ..., xn. Note this produces a plot that includes points with x-values x1, x2, ..., xn. To produce a plot that contains only these points, you need to add the adaptive=false option as well.

The first example below seems OK. But, should I be expecting the different behaviour in the second example?


> restart:
> p := module() option package; export foo;
> foo:=proc(x) x; end proc;
> end module:

> foo := proc(x) cos(x); end proc:

> foo(3.2);
-0.9982947758

> p:-foo(3.2);
3.2

> evalhf(p:-foo(3.2)); # OK
3.20000000000000018

> restart:
> p := module() option package; export sin;

Dear all, I recently had to solve the following integral: A:=(x,m)->(-m^2-2*x*m+1)/(sqrt(x)*sqrt((m+x)^2-1)*(x+sqrt((m+x)^2-1))); IntegralA:=(m)->Int(A(x,m),x=0..infinity); When I used evalf(IntegralA(1)); I get -2.828427125 But when I use int(A(x,1),x=0..infinity); to get a symbolic answer I get a complicated expression involving the function MeijerG function. Mathematica, on the other hand gives -2sqrt(2) exactly for the symbolic value. Does anybody know why? I'm curious even though the decimal values are the same. I was using Maple 11 and Mathemtica (I think) 5. Regards, Drew

Hi folks, When I use a command like: implicitplot3d(f(x,y,z)=0,x=...,y=...,z=...) obviously maple has to compute all the points in the given range which satisfy the equation. Does anybody know which numerical method it uses to do this? Regards, Drew

This is what I have so far, I would prefer that the globe be animated with the animate code, also if there is a way to tilt the globe slightly. I also want to be able to have the moon and sun go around the globe as it is rising and falling. While the Sphere is rotating. I want to try and do this with animate or rotate commands Packages: with(plots):with(plottools): Globe: sphere: globe:=sphere([0, 0, 0], 1/3): display(globe,scaling=constrained,style=patch,axes=none): animation: globe := sphere([0,0,0], 1/3): n := 80: plt[0] := globe: for i to n-1 do

I am trying to animate a sphere/ so that it kinda looks like the globe rotating. This is what I have so far. Also if any body knows how to tilt a sphere so that it is on an angle. that would greatly help. with(plots):with(plottools): globe:=sphere([2.0, 1.5, 1.5], 1): display(globe,scaling=constrained,style=patch,axes=normal):

Here's a substitution that briefly surprised me. It makes sense once you understand what is going on.

subs(true = false, proc() local i; for i to 3 do true; end do end proc);
 
           proc()  end proc

A little under two years ago, I started working on a little project we have here at NCSU. I should perhaps devote another blog entry to discussing that lovely little project... Anyway, there's a lot of Maple code in this project (as it is based in Maple), and I've had to untangle and understand what multiple programmers have done over the years. Last year, I came across one piece of code that I thought was exploiting a bug in Maple: We would take a long string of commands and parse the entire string with a single parse() command. I could never get a Maple worksheet to reproduce those results obtained from piping the command into Maple from the command line. Weird, no?

It's just a silly, simple thing, but I'm going to call attention to it anyway: fopen("file", w); Produces the error message "Error, (in fopen) file mode must be READ or WRITE." This is incorrect. The file mode must be READ, WRITE, or APPEND. Like I said: silly, but worth noting.