I understood your suggested change of variable to be the following, but perhaps I misunderstood -- I now realize your system is a little different (some square root on x has disappeared), so I'm not sure if the following is what you meant:

newxdot := diff(x(tau),tau) = rhs(eval(xdot,t=tau))*rhs(eval(xdot,t=tau)):

newcdot := diff(c(tau),tau) = rhs(eval(cdot,t=tau))*rhs(eval(xdot,t=tau)):

newqdot := diff(q(tau),tau) = rhs(eval(qdot,t=tau))*rhs(eval(xdot,t=tau)):

If it's not what you meant, what I wrote probably doesn't make sense.

Remark. Hopefully mapleprimes will respect my linebreaks this time.

and not C(400/9) = 40/9 and Q(400/9) = 1/80, as you write

1/80 = 0.0125

1/40 = 0.025  --> my boundary condition specified in INI1 and INI2

P.S. apologies for being slow and insistent, your help is GREATLY appreciated.

and not C(400/9) = 40/9 and Q(400/9) = 1/80, as you write

1/80 = 0.0125

1/40 = 0.025  --> my boundary condition specified in INI1 and INI2

P.S. apologies for being slow and insistent, your help is GREATLY appreciated.

please excuse my ignorance

very nice pictures Robert!

please excuse my ignorance

very nice pictures Robert!

You may be able to get more precision by setting Digits to a large number, say

Digits:=100:

I'm not sure it'll change anything, but it's worth a try.

You can simultaneously maintain a small number of digits on display,

interface(displayprecision=4):

And you can get maple to display some of its steps by setting infolevel,

Throughout the Maple library userinfo statements have been used with the following conventions: 
Level 1: reserved for information that the user must be told.
Level 2,3: general information, including technique or algorithm being used.
Level 4,5: more detailed information about how the problem is being solved

Apparently matlab has a default of 32 digits. You may be able to play around with that too.

You may be able to get more precision by setting Digits to a large number, say

Digits:=100:

I'm not sure it'll change anything, but it's worth a try.

You can simultaneously maintain a small number of digits on display,

interface(displayprecision=4):

And you can get maple to display some of its steps by setting infolevel,

Throughout the Maple library userinfo statements have been used with the following conventions: 
Level 1: reserved for information that the user must be told.
Level 2,3: general information, including technique or algorithm being used.
Level 4,5: more detailed information about how the problem is being solved

Apparently matlab has a default of 32 digits. You may be able to play around with that too.

thanks for your help Paulina,

and a big thank you to Alejandro, as always!

Patrick.

thanks for your help Paulina,

and a big thank you to Alejandro, as always!

Patrick.

I see what you mean, I too get that blurred effect for even values on-screen (Maple13/standard), but when I exported as ps, I couldn't see the blur anymore:

p4 := plot(cos(x), x=-2*Pi..2*Pi, 
axis=[gridlines=[[0], thickness=4, color=black], tickmarks=8], axes=normal):
plotsetup(ps,plotoutput=`p4.ps`,
plotoptions=`color,portrait,noborder,axiswidth=500pt,axisheight=500pt`):  
plots[display]({p4},labels=[``,``]);

I see what you mean, I too get that blurred effect for even values on-screen (Maple13/standard), but when I exported as ps, I couldn't see the blur anymore:

p4 := plot(cos(x), x=-2*Pi..2*Pi, 
axis=[gridlines=[[0], thickness=4, color=black], tickmarks=8], axes=normal):
plotsetup(ps,plotoutput=`p4.ps`,
plotoptions=`color,portrait,noborder,axiswidth=500pt,axisheight=500pt`):  
plots[display]({p4},labels=[``,``]);

Thanks Paulina, this is a useful thing to know.

The option/gridlines workaround you suggest works for Maple/Standard but not for Maple/Classic. I should have made it clearer that I am interested in using this in Maple/Classic because the axis lines are thinner in classic than in standard, and especially because the 3D plots produced in Maple/Classic actually look a great deal better than the 3D plots produced in Maple/Standard -- something I am hoping Maple 14 will address :-)

Paulina, if you're reading, do you know whether the tickmarks/thickness option available in Maple 11 (still documented in the help, but lost in Maple 13) is unavailable by design or because of a bug? If it's a bug, let's report it as such.

jakubi, do you mean the effect caused by the fact that the gridlines are grey by default while the axis lines are black? The call below sets the gridlines to black and looks alright on my Maple13/Standard:

p := plot(cos(x), x=-2*Pi..2*Pi, 
axis=[gridlines=[[0], thickness=3, color=black], tickmarks=8], axes=normal): 
plots[display](p);

Thanks Paulina, this is a useful thing to know.

The option/gridlines workaround you suggest works for Maple/Standard but not for Maple/Classic. I should have made it clearer that I am interested in using this in Maple/Classic because the axis lines are thinner in classic than in standard, and especially because the 3D plots produced in Maple/Classic actually look a great deal better than the 3D plots produced in Maple/Standard -- something I am hoping Maple 14 will address :-)

Paulina, if you're reading, do you know whether the tickmarks/thickness option available in Maple 11 (still documented in the help, but lost in Maple 13) is unavailable by design or because of a bug? If it's a bug, let's report it as such.

jakubi, do you mean the effect caused by the fact that the gridlines are grey by default while the axis lines are black? The call below sets the gridlines to black and looks alright on my Maple13/Standard:

p := plot(cos(x), x=-2*Pi..2*Pi, 
axis=[gridlines=[[0], thickness=3, color=black], tickmarks=8], axes=normal): 
plots[display](p);

thanks so much jakubi for your patient explanations!

thanks so much jakubi for your patient explanations!