Am I just missing it, or is there no reference or link to ?Rounding from either the ?evalf or ?evalf,details help-pages? Also, maybe the ?Rounding page could benefit from an example such as,

> evalf[5](Pi);
                                    3.1416

> Rounding:=0:
> forget(evalf):
> evalf[5](Pi);
                                    3.1415

Yes, as Alec points out iquo (or irem) is usual. See also,

interface(verboseproc=3):
eval(`convert/base`);

acer

Am I just missing it, or is there no reference or link to ?Rounding from either the ?evalf or ?evalf,details help-pages? Also, maybe the ?Rounding page could benefit from an example such as,

> evalf[5](Pi);
                                    3.1416

> Rounding:=0:
> forget(evalf):
> evalf[5](Pi);
                                    3.1415

Yes, as Alec points out iquo (or irem) is usual. See also,

interface(verboseproc=3):
eval(`convert/base`);

acer

That's a good point, about the timing function. A more convenient version of Maple's time() command, which returns both the result and the elapsed time, would be useful.

As far as the speed goes, does anyone know how many pre-computed digits of Pi Mathematica has stored (hard-coded)? It's even more interesting if one knows that both systems had to compute the answer in full.

acer

That's a good point, about the timing function. A more convenient version of Maple's time() command, which returns both the result and the elapsed time, would be useful.

As far as the speed goes, does anyone know how many pre-computed digits of Pi Mathematica has stored (hard-coded)? It's even more interesting if one knows that both systems had to compute the answer in full.

acer

Nice.

My rather facile answer above was due to my mistaking it as a Student forum question, possibly an exercise from calculus. Sorry about that.

acer

Nice.

My rather facile answer above was due to my mistaking it as a Student forum question, possibly an exercise from calculus. Sorry about that.

acer

Well, it's easy to be fast when looking up precomputed results.

Fast lookup, even if it requires a base conversion, is about the opposite end of the interest spectrum for me as is the BBP research (or similar, where most earlier digits aren't even computed when searching for some high nth).

acer

Well, it's easy to be fast when looking up precomputed results.

Fast lookup, even if it requires a base conversion, is about the opposite end of the interest spectrum for me as is the BBP research (or similar, where most earlier digits aren't even computed when searching for some high nth).

acer

The default for Standard is a thing called a Document. But there is also a Worksheet.

One can always open a new one of either, using the File->Open menubar item.

I set my global preference to Worksheet (again, somewhere under Tools->Options).

One can use either 2D or 1D input in a Worksheet.

So, really, there are two sorts of option/choice for the Standard GUI. Both can be set separately. Bot can be set as a preference (globally, for all new sessions).

• 1D Maple input vs 2D Math input
• Worksheet vs Document

Writing cool applications with embedded components linked to live(!) tyepset 2D math equations is where I might use a Document and 2D Math input. But for everyday use, and especially for coding, I use a Worksheet and 1D Maple input.

I like 1D Maple input because what I see is what is actually there, unambiguously.

acer

The default for Standard is a thing called a Document. But there is also a Worksheet.

One can always open a new one of either, using the File->Open menubar item.

I set my global preference to Worksheet (again, somewhere under Tools->Options).

One can use either 2D or 1D input in a Worksheet.

So, really, there are two sorts of option/choice for the Standard GUI. Both can be set separately. Bot can be set as a preference (globally, for all new sessions).

• 1D Maple input vs 2D Math input
• Worksheet vs Document

Writing cool applications with embedded components linked to live(!) tyepset 2D math equations is where I might use a Document and 2D Math input. But for everyday use, and especially for coding, I use a Worksheet and 1D Maple input.

I like 1D Maple input because what I see is what is actually there, unambiguously.

acer

I understand, if you are saying the 2D Math input in the Standard GUI is radically different (and possibly very much not to your liking) from the input mode of the Classic GUI.

But how is 1D Maple input in Standard so much different from the input mode of Classic?

When you write that, "it's practically impossible to enter the commands in Standard," I can't help but think that perhaps you're only trying it with 2D Math input.

The 1D Maple input form of Standard, however, is pretty much the same (red, non-typeset) input that I'd known in Classic. No on-the-fly typesetting of input. No implicit multiplication. No special 2D Math parser. No subscripting of table entries (in the input). I use that, in Worksheet mode, and it's ok for me.

ps. The trick of using the 32bit Classic interface with the 64bit Linux Maple 12 installation will not work completely unless all the new (new specifically in M12) binaries are added to the set of symlinks (into the "new" directory, under that scheme). It was originally done for M10, and the posted scheme seems to work by symlinking all the 64bit binaries not used  by the TTY interface's libmclient.so. But new binaries have been added bewteen M10 and M12.

acer

I understand, if you are saying the 2D Math input in the Standard GUI is radically different (and possibly very much not to your liking) from the input mode of the Classic GUI.

But how is 1D Maple input in Standard so much different from the input mode of Classic?

When you write that, "it's practically impossible to enter the commands in Standard," I can't help but think that perhaps you're only trying it with 2D Math input.

The 1D Maple input form of Standard, however, is pretty much the same (red, non-typeset) input that I'd known in Classic. No on-the-fly typesetting of input. No implicit multiplication. No special 2D Math parser. No subscripting of table entries (in the input). I use that, in Worksheet mode, and it's ok for me.

ps. The trick of using the 32bit Classic interface with the 64bit Linux Maple 12 installation will not work completely unless all the new (new specifically in M12) binaries are added to the set of symlinks (into the "new" directory, under that scheme). It was originally done for M10, and the posted scheme seems to work by symlinking all the 64bit binaries not used  by the TTY interface's libmclient.so. But new binaries have been added bewteen M10 and M12.

acer

You can set the input mode in the Standard GUI to be 1D Maple input, in Worksheets, as a preference (globally) for all new sessions.

See Tools->Options->Display.  Apologies, if you already knew that.

acer

You can set the input mode in the Standard GUI to be 1D Maple input, in Worksheets, as a preference (globally) for all new sessions.

See Tools->Options->Display.  Apologies, if you already knew that.

acer

For reasons not altogether clear, the code posted is not accepted by the 2D Math parser in Maple 12.

I suggest entering it in 1D Maple input instead of 2D Math input. (See the Tools->Options->Display tab for control of this mode. It can also be toggled directly, using the F5 key I believe.)

acer