Joseph Cusumano

That's wonderful. Thanks, Ethan!

Thanks for figuring that out, Ethan. Maxima (and therefore wxMaxima) appear to depend on the previous drawing order. Will this be changed back to the behavior in gnuplot 5.47? I'm not a developer, so I don't know how such interaction issues are addressed. To which project does the bug get assigned?

By examining the .gnuplot file, I can I confirmed that the contour both directive works in gnuplot 5.47 but fails in gnuplot 6.0. However, I also found that commenting out this line set pm3d at s depthorder implicit results in the contours being plotted on both surfaces in gnuplot 6.0, as desired. I can also get a good result by replacing the above with either set pm3d at s scansautomatic or set pm3d at s scansbackward Maybe I'm missing something, but I don't see the difference in results between...

There is no bug. There's nothing wrong with those answers, either. They just don't look the way you want them too. You're getting complex numbers because the log of negative numbers is complex, and Maxima doesn't know the sign of (2x-A). But just because it throws a %i in the answer doesn't make it wrong! Try this, to clear the exponentiated the log terms. ode:'diff(y,x)+(3/(A-2*x))*y=0; ode2(ode,y,x)$ factor(radcan(%)); /* this does the clean up */ ic1(%,x=xB,y=yB); This probably gives you what...

I've figured it out with the help of this page, which has a nice description of how to do it.

There are two steps: Using the signature file you can verify that the content of the tar.gz has not been changed after the signature has been created. Using the public key you can verify that the signature has been created by the person that has access to the corresponding private key. Well, yeah... but do you know the Linux (Ubuntu/Mint) command line syntax to do those things? I'm been trying to use gpg, so far with no luck.

I want to verify the tar.gz file for the latest release using the associated .asc file. I've never done that before. I think I need a public key. Where do I get that? What keyserver do I use? I've been playing around with gpg (I'm using Linux Mint 19.1), but so far haven't had any luck.

Well, again, that's the nature of floating point, which can be implemented slightly differently on different machines and/or in different numerical environments. The number 0.2 is not distinguishable from 0.1999...999. That's not a limitation of Maxima. It's a reality of floating point arithmetic. That's one of the virtues of symbolic manipulation: the arithmetic is exact. Once you've converted to floating point, it's not. Cheers.