Are you just trying to test whether any entry of a Matrix is negative? Is each of the entries constant?

Or do you need to detect the minus sign inside an entry like, say, exp(-x) ?

acer

What do you see if you lprint it?

acer

@akiel123 Did you intend Pi/4 instead of 90 inside your calls to tan? Maple's trig functions work with radians.

Whether 90 or Pi/4, some of your constaints are evaluating to impossible inequalities, such as 0 <= -6 . You'll need to figure those out and correct.

@akiel123 Your defined it as minCorner but you call it as MinCorner.

Also, you can get a smaller form by forcing use of normal as the Normalizer (in say MatrixInverse).

Note that by itself this may produce an invalid result if a "hidden zero" is used as a pivot during elimination. LinearAlgebra will try to use a stronger zero detection (Testzero) and Normalizer, if it sees that Normalizer<>eval(normal), for example t->simplify(t,trig) if it detects trig stuff, or even simplify itself. So it might be safer to also force a stronger and "suitable" Testzero if one is going to forcibly dumb down Normalizer. I have seen examples involving trig terms where linalg produce wrong inverse results for just these reasons.

Download condnormal.mw

Perhaps a somewhat safer Testzero might be,

Testzero:=proc(z) evalb(simplify(z)=0); end proc:

in the case that one had set Normalizer as I did above. By default Testzero simply checks evalb(Normalizer(z) = 0) for input z.

@Markiyan Hirnyk 

Download resmore.mw

@Markiyan Hirnyk The exact results differ in form from session to session. At default working precision of Digits=10 they evaluate to slightly different floats due to roundoff, but at higher working precision they evaluate to results which agree to more decimal figures.

It is just as Preben has said.

Download res.mw

@akiel123 If you use the big green arrow in the Mapleprimes editor to upload your worksheet then we could work on it directly, thanks. It's quite difficult to make suggestions based on just an image of your code (at any resolution).

Also you can now see that there is no real need to have the procedure OptimizeSpring, since all it does it call Maximize. You might as well just call Maximize directly.

Your procedure is very strangely written.

I can't tell whether you are trying to use function calls as if they were local variables (via remember tables), or whether you are using a nonstandard syntax for operator definition.

What do you think that call to d__plP is supposed to be, used on the left hand side of an assignment statement inside that procedure OptimizeSpring?

Whichever it is, you defined d__plP as having 4 parameters, but then only call it with 2 when using it on the right-hand side of the assignment to d__min(...). You make this same mistake in several places.

Since you didn't get get an error about insufficient arguments then we can see that Maple thinks that you've assigned to function calls (remember table assignments), rather than that you've defined operators.

Define operators like this:

d__lpP := (P__1x,P__1y,P__2x,P__2y) -> some_expression_like_you_have_above;

Note that it's not very efficient to have your procedure OptimizeSpring redefine the same operators each time it's called. It's not clear whether you really want and need operators, at this point. Please clarify as your your intent.

Or if you just wanted to use function calls as if you had local variables (which is not a very usual thing to do) then make sure that 1) you declare your locals, 2) you always make the number of arguments match across all instances of each. Even better would be to not use function calls like local variables unless you completely understand all these aspects of usage. Use simple names, or indexed names, if you're just trying to use local variables.

acer

@software_c This appears to be merely a non-general variant of Joe's Answer.

@Carl Love It's some mysterious part of the GUI plot renderer that figure out how to draw the surface, given an ISOSURFACE structure. I don't know what interpolating mechanism it uses. I have wondered, whether in principal it could be converted to some MESH.

There was another beast for which I have a recollection that transforming might not work. Hmm. I suspect it may have been 3D contour plot structures. I recall having difficulty in doing a 3D->2D projection transformation on such (and possibly also for getting at the data otherwise).

@Carl Love An interesting example of "any two- or three-dimensional plot" might be,

plots:-implicitplot3d(r=(1.3)^x*sin(y), r=0.1..5, x=-1..2*Pi, y=0..Pi, coords=spherical);

Why not upload the worksheet that contains the plot, and we could then see what might be possible?

acer

@nMaple In Maple 2015 you can programmatically embed an inlined plot with a given width, height, scale (zoom), and pan (x- or y-offset).

But you cannot subsequently adjust those qualities programmatically, after it gets embedded.

I have previously submitted a Software Change Request that the scale and pan (as well as the rotation angles and projection for 3D plots) become new properties of the PlotComponent.

@nMaple Using Embedded Components you can programmatically change the delay (in millisec) between frames.

There is no facility in Maple 17 to programmatically change the plot "scale" or "pan".

Attached is a worksheet that uses a command to set an animation playing in an Embedded Component. There are commands shown to change whether it loops, and to change the frame delay mentioned above.

There is also a Slider, the "action" code for which also sets the Plot component's animation delay value.

See the relevan help pages for more information on Embedded Components.

animobj.mw