@Christopher2222 It is not ragged because of implicitplot, it is ragged due to undersampling the range in question.  That is, since no range is specified, you are zooming in on this:

which results in:
plots:-display(plot(x^3-4*x), view=[-5..5,-5..5]);

Which can be remedied by giving a range:

plots:-display(plot(x^3-4*x,x=-3..3), view=[-5..5,-5..5]);

You shouldn't need numpoints, since the curve is not being generated by implicitplot.

 a:=plot(x^3-4*x,x=-3..3):
 b:=plots:-implicitplot(1,x=-5..5,y=-5..5, 
                        coloring=[black,black],filledregions=true):
 plots:-display(a,b,view=[-5..5,-5..5],axis=[color=green]);

You would need it if you were trying to generate your curve with implicitplot

plots:-implicitplot(y=x^3-4*x,x=-5..5,y=-5..5);

John

You shouldn't need numpoints, since the curve is not being generated by implicitplot.

 a:=plot(x^3-4*x,x=-3..3):
 b:=plots:-implicitplot(1,x=-5..5,y=-5..5, 
                        coloring=[black,black],filledregions=true):
 plots:-display(a,b,view=[-5..5,-5..5],axis=[color=green]);

You would need it if you were trying to generate your curve with implicitplot

plots:-implicitplot(y=x^3-4*x,x=-5..5,y=-5..5);

John

I like it!

John

In case anyone is wondering why I chose to use a button to load the data instead of using the startup code region: For worksheets downloaded from the Maple Cloud in Maple 14, the default security settings prevent the automatic execution of the startup code region.  Since I wanted to post this worksheet to the cloud and have people be able to use it without saving it and then reloading it, I put the startup code in a button component.

@acer Scary.

@JacquesC Not to imply that I am disinterested.  I just can imagine myself being in the top 10.

@Robert Israel That is a really good point.  These tests are not able to detect deviation from randomness at that level so they should be combined with some other tests as well.  Which means the followup post to this one practically writes itself.

For people like me who are not among that ~10 in the world, the example on the help page doesn't really give a good idea of why you might want to use ::uneval. When I use it, it is mostly for testing or measuring the evaluation of expressions. So, for those people who might end up here, here is a small example:

 benchmark := proc(e::uneval)
 local t, b;
     t, b := time(), kernelopts(':-bytesused');
     eval(e);
     return (time() - t)*Unit(second), (kernelopts(':-bytesused') - b)*Unit(byte);
 end proc

This is a simple extention of ?time that also records the memory used to evaluate the expression 'e'.

(**) benchmark(solve(x^50-1));
                                0.201 [s], 10924456 [byte]

@Alejandro Jakubi I do not remember what my answer was exactly and I do not know why it was removed (perhaps it was inaudible in the recording from the studio mic too).  But I can say that I have visited with Al Rich and had fruitful discussions with him about his indefinite integration project. We are certainly looking at ways to improve some of the weaknesses his tests show.

When looking at the test results however, it is important to keep in mind the following from the Rubi test suite description:

Since Rubi was developed in conjunction with the test suite, its good performance is to be expected. And no doubt there are many problems Rubi is unable to integrate.

Also, if I recall correctly, the test suite doesn't address continuity of results so it is not clear how his work would apply to the problem of definite integration.

Or as a Vector constructor:

  v:= Vector(5, i->exp(i));

Or as a Vector constructor:

  v:= Vector(5, i->exp(i));

@gotamo You should be able to compute the variance using ?Statitics and ?ArrayTools in the following way.

(**) Statistics:-Variance( ArrayTools:-Reshape( img, 1..ArrayTools:-NumElems(img) ) );

Basically, ?Statistics:-Variance wants a one dimensional Array, and ?ArrayTools:-Reshape allows you to convert your two dimensional image into one. (In fact, it doesn't actually convert, it just provides an alias to the same piece of memory).

Hope that helps.

John

@gotamo You should be able to compute the variance using ?Statitics and ?ArrayTools in the following way.

(**) Statistics:-Variance( ArrayTools:-Reshape( img, 1..ArrayTools:-NumElems(img) ) );

Basically, ?Statistics:-Variance wants a one dimensional Array, and ?ArrayTools:-Reshape allows you to convert your two dimensional image into one. (In fact, it doesn't actually convert, it just provides an alias to the same piece of memory).

Hope that helps.

John

I don't work on the GUI team, and so I don't really have a horse in this race; I am just providing my honest advice on how to get the best Maple experience on a modern platform.