In this example, you can get out of the standard math after y = \xB1 and then add 6. Or use the multiplication sign, y = \xB1*6 - treat it as if it was a name, something like x. It would also work without a space between \xB1 and 6, but they would be too close to each other and 6 would be italicized. The problem is not with \xB1 - it would be the same problem, say, for y = x 6.

Another example - the quadratic formula can be entered as

x[1,2] =(-b*\xB1*sqrt(b^2-4*a*c))/2/a

Alec

If you are already in standard math (inside text), then \xB1 will produce the plus-minus sign.

Alec

It should be %% instead of %%% above.

convert(104/Pi^4,rational) gives 104/Pi^4, but

convert(evalf(104/Pi^4),rational);

                              2494128918
                              ----------
                              2336065681

Alec

It should be %% instead of %%% above.

convert(104/Pi^4,rational) gives 104/Pi^4, but

convert(evalf(104/Pi^4),rational);

                              2494128918
                              ----------
                              2336065681

Alec

Just returned home from a trip to Champaign, IL (not related to Mathematica). Seems to be a nice place. Not exactly London, England, but may be better than Jackson, TN.

It is great to see that SearchAll may work better in the next Maple release. If things worked like that, the maple patch library would not be necessary (or interesting). Wiki still may be useful though. I plan to put this thread there (probably, tomorrow) in some form that doesn't infringe (is this a correct word?) with copyright - but if people posting in the thread could do that themselves, that would certainly be better (and less work for me.)

Alec

John,

That's an interesting example.

It also shows the weakness of select in this case.  Unfortunately, select is built-in so the source code is not available.

By the way, I didn't mean to say that using select is the best way of doing that. It was just the first one that came to mind, and it worked OK in the real life example in which  I needed it while SearchAll was too slow. It was a sequence of 0s and 1s, so there were many repetitions.

It can be easily improved using standard tricks - writing it as a sequence, compiling etc.

By the way, [seq](...) is slower than [seq(...)],

time([seq](1..10^7));
                                0.405

time([seq(1..10^7)]);
                                0.218
Alec

Please test version 1 (or, maybe, 0.001 :) of maple format in MapleTest, and LaTeX input, as well as new commands $\mi{ ... }$ and $$\mo{ ... }$$ (names suggested by Alejandro Jakubi) for Maple input and output, correspondingly, in JsMathTest1.

In addition to current text there, I tested code from Joe Riel's blog, Faster Permutations, by copying it from there and pasting in the middle of

{{{#!maple 

}}}

Seemed to look good.

Comments are very welcomed.

Alec

Also, comments can be entered (in wiki) in C-style, as /* a comment */ . Then they are usually invisible on a page, but clicking Comments at the top of the page (next to Edit) makes them visible.

If you visit wiki, take a look at recent Alejandro Jakubi articles, in particular, about Inert forms, Spherical coordinates, and Sets in Maple. I've added tables of Math characters and Delimeters available in the wiki.

Alec

I've discovered that the same way - looking at the sqrt code and trying to improve it for integers - thus far, the code that I wrote works about twice faster (for integers) than current sqrt , but I'd like to have something, say, 10 times faster, and without using compiled code.

Such magic numbers - in this case, it is the product of prime numbers from 2 to 149, should be mentioned on the help pages, I think.

Alec

Maple can be run in Latex filter mode, see ?maple . Then you can process the latex output.

Alec

Maple can be run in Latex filter mode, see ?maple . Then you can process the latex output.

Alec

Yes, I meant inplace. In these examples it doesn't seem to make much of a difference though.

Perhaps, the sqrt code for integers could be improved?

Alec

Yes, I meant inplace. In these examples it doesn't seem to make much of a difference though.

Perhaps, the sqrt code for integers could be improved?

Alec

datatype=float[8] and evalhf option in map make the difference. Why is it not fair?

Alec

datatype=float[8] and evalhf option in map make the difference. Why is it not fair?

Alec