No change. It's just the bug submitting requires some time that I don't have. I don't feel that it is my "duty". I think it is the "duty" of people working at Maplesoft and getting paid for that.

If you are implying that the fact that I am not participating in beta is my fault - I don't think so.

Alec

remez is another one good old thing practically getting deprecated because arrays got deprecated. If I am not mistaken, it was developed by Keith Geddes and/or his students (I remember a couple of articles about that algorithm written by him/them.) Is there an analog of that for Arrays?

Alec

remez is another one good old thing practically getting deprecated because arrays got deprecated. If I am not mistaken, it was developed by Keith Geddes and/or his students (I remember a couple of articles about that algorithm written by him/them.) Is there an analog of that for Arrays?

Alec

A related question is what should -0.3 mod 1 be equal to? In mathematics, it is fractional part, and equal to 0.7, but in Maple frac is different, and gives -0.3 in this example.

Alec

That's OK with me. It is more fun with the bug in then out.

Alec

Axel,

Background still doesn't seem to be white. Did you try to open it in Paint?

Builds for XP and for Vista seem to be different.

Alec

PS You didn't upgrade to SP3? -Alec

I didn't mean exactly this one for kindergarten - just a similar one with smaller numbers. Say, there are not more than 3 apples. Tom and Jerry got one or more apples each. How many apples they could have? The answer is - either each got 1 apple, or one of them got 1 apple and another one - 2. Now, try that with isolve,

isolve({a+b<=3,a>0,b>0});
                           {b = 1 + _NN2~}

Jerry seems to be able to get as many apples as he want, and nothing is known about Tom. Same if only 2 apples were there, or less,

isolve({a+b<=2,a>0,b>0});
                           {b = 1 + _NN3~}

And even with 1 apple or less,

isolve({a+b<=1,a>0,b>0});
                           {b = 1 + _NN4~}

Some problems work OK though,

isolve({a>=1, a<=3});

                      {a = 1}, {a = 2}, {a = 3}

Alec

The calculus taught for undergraduate students shouldn't be very hard to implement. It is very algorithmic.

Maple has problems with that, I think, becase of working with complex numbers.

Generaly, the educational steps developed during hundreds, or maybe thousands years, have big sense, and they were ignored in Maple.

Starting from natural numbers and kindergarten problems, then covering elementary school, then high school problems, then Calculus with real numbers, and only after that starting to think about implementing complex numbers properly beyond quadratic equations (where they should be introduced in high school) would be an easy and natural way of building a CAS.

Currently, there are a lot of kindergarten problems (like solving inequalities with small integer solutions) which can't be solved in maple easily, like, say, using isolve command. Not talking about elementary and high school problems.

Alec

You could try adding bounds instead of initial points. For example,

with(Optimization):
Maximize(40*a+60*b, {40*a+60*b <= 150}, a=0..3, b=0..2, 
    assume = nonnegint, depthlimit=10);

                        [140, [a = 2, b = 1]]

Alec

This problem has only 8 feasible points: (0,0), (0,1), (0,2), (1,0), (1,1), (2,0), (2,1), (3,0) - in such cases the simplest solution would be to evaluate the function in all the feasible points, and then choose the maximum. It is strange that such a simple thing was not implemented.

Alec

I guess you don't have any other choice as to upgrade to Maple 12.

_______________
Alec Mihailovs
Maplesoft Member

I open it in standard Paint (in Accessories) in Vista, and it has a black background. I made the png posted using Paint (saving the wmf file in the png format.).

It is interesting that you got so different size of the output in the same Maple version. Was it in XP or in Vista? In the document mode?

Edit: Just looked at it in Paint in Windows XP. Also black background. In Windows Picture and Fax Viewer (in XP) it looked better - without any background. In Microsoft Office 2007 Picture Manager (in Vista) it also looked like if the picture didn't have any background. Probably, that explains the situation - the wmf file seems to be lacking the background, and some viewers replace it with their own backgrounds, while Paint (the default wmf viewer and editor in Vista and the default wmf editor in XP) shows the black background.  

Alec 

David, I just uploaded the file. It is 135_wmf.zip It was produced in a newly opened Standard Maple, in Document mode, without doing anything else before that, by copying and pasting the code from my original post.

None (or almost none) of the bugs that I reported were fixed, so it would be better if somebody else reported the bug. I stopped doing that a couple of years ago.

Alec

In Maple 12, it works with increased depthlimit. For example,

with(Optimization):
Maximize(40*a + 60*b, {40*a + 60*b <= 150}, 
    assume=nonnegint, depthlimit=10);

                        [140, [a = 2, b = 1]]

Alec

Axel,

You mean the file that I uploaded, or the export produced on your computer?

Alec