It's not just a question of the ordering of phi and theta, but which angle is called phi and which is called theta. Physicists almost always (I think) use phi for the longitude and theta for colatitude, mathematicians do it the other way around. There is no agreement among math textbooks on the ordering of phi and theta.

To get a version of the cube root of x that is real when x is real, use surd(x,3). Or use the RealDomain package.

Did you remember

with(VectorCalculus):

?

Did you remember

with(VectorCalculus):

?

Again, there are bugs here.

> solve(eval(F1,y=150), x);

25, 0 The 25 is correct, the 0 is not.

Again, there are bugs here.

> solve(eval(F1,y=150), x);

25, 0 The 25 is correct, the 0 is not.

Yes, just put it between "maple math" tags.

> Surface(< r,phi,theta>, phi = 0 .. Pi/2, 
    theta = 0 .. 2*Pi,coords=spherical[r,phi,theta]);

Surface(RTABLE(156566820,MATRIX([[r], [phi], [theta]],["x", "y", "z"]),Vector[column]),phi = 0 .. 1/2*Pi,theta = 0 .. 2*Pi,coords = spherical[r,phi,theta])

Yes, just put it between "maple math" tags.

> Surface(< r,phi,theta>, phi = 0 .. Pi/2, 
    theta = 0 .. 2*Pi,coords=spherical[r,phi,theta]);

Surface(RTABLE(156566820,MATRIX([[r], [phi], [theta]],["x", "y", "z"]),Vector[column]),phi = 0 .. 1/2*Pi,theta = 0 .. 2*Pi,coords = spherical[r,phi,theta])

... or more likely,

> solve(F1, x);

which unfortunately does not return anything. You might get an answer if you help Maple by putting some appropriate assumptions on y. For example:

> solve(F1, x) assuming y > 0;

-y+150 However, there are some bugs. Consider:

> expr := piecewise(x <= 0, 0, x <= 1, x^2, 0);
  solve(expr = 4, x);

-2

... or more likely,

> solve(F1, x);

which unfortunately does not return anything. You might get an answer if you help Maple by putting some appropriate assumptions on y. For example:

> solve(F1, x) assuming y > 0;

-y+150 However, there are some bugs. Consider:

> expr := piecewise(x <= 0, 0, x <= 1, x^2, 0);
  solve(expr = 4, x);

-2

See "Unassigning a Name Using Unevaluation Quotes" on p. 319 of the User Manual.

The simplest way to remove the assigned value from a symbolic variable is to assign the variable its name in 'quotes':

> x := 'x';

You could also use

> unassign('x');

To evaluate an expression with certain values for some of the variables, you can use eval. In your example:

> v := x^3;
  eval(v, x = 3);

To suppress output, use a colon instead of a semicolon to end your command. If you really need something that can do _everything_ Mathematica can do, I'm afraid the only way is to get Mathematica (and make sure you always have the latest version, and maybe some earlier versions too...) Maple and Mathematica both have their strengths and weaknesses.

I think "nops" has been in Maple from the very beginning, and you're not likely to get it changed now: better get used to it, if you're going to do any Maple programming. It's not just for lists, it's for any Maple object: nops returns the number of operands. "length" is already a Maple function, which returns the total length of an object. Mupad, BTW, also uses "nops". Maybe some other CAS's do too. Most computer languages, I think, don't deal so often with expressions that have an arbitrary number of operands.

These are four different implementations of what might loosely be called "interval arithmetic" (though the ScientificErrorAnalysis package explicitly says that it is _not_ interval arithmetic).

These are four different implementations of what might loosely be called "interval arithmetic" (though the ScientificErrorAnalysis package explicitly says that it is _not_ interval arithmetic).