For whatever reason, I have the hardest time finding that keyword.  I know it is in kernelopts, but it never jumps out when scanning the list in the help page. Probably I'm looking for something with gc in it.  Some day I'll create a help page with two listings, one alphabetical and one functional, however, given the variety of stuff in there there may be no nice organization.

@Alejandro Jakubi It's been out for a while, I mentioned it here. It requires Emacs and only works with OpenMaple (which is part of any recent Maple distribution); however, I don't know that anyone has successfully installed it on a non Linux system. The OpenMaple requirement limits its use to, essentially, tty Maple. That is, it doesn't work with the Standard Maple GUI.

The good news is that I've since developed a replacement that eliminates the need for OpenMaple, works with all Maple user interfaces, and is easily installed on Linux, Windows, and presumably the Mac, though I haven't tested it there.  It's in alpha test now.  It uses a new architecture that provides a lot of capability, such as the ability to debug parallel Maple sessions. Not sure when the general release will be.  Send me an email if you are interested in beta testing it.  Still requires Emacs, but I consider that a feature 8-). Currently am adding stuff so less experienced Emacs users can deal with it.

@Alejandro Jakubi It's been out for a while, I mentioned it here. It requires Emacs and only works with OpenMaple (which is part of any recent Maple distribution); however, I don't know that anyone has successfully installed it on a non Linux system. The OpenMaple requirement limits its use to, essentially, tty Maple. That is, it doesn't work with the Standard Maple GUI.

The good news is that I've since developed a replacement that eliminates the need for OpenMaple, works with all Maple user interfaces, and is easily installed on Linux, Windows, and presumably the Mac, though I haven't tested it there.  It's in alpha test now.  It uses a new architecture that provides a lot of capability, such as the ability to debug parallel Maple sessions. Not sure when the general release will be.  Send me an email if you are interested in beta testing it.  Still requires Emacs, but I consider that a feature 8-). Currently am adding stuff so less experienced Emacs users can deal with it.

@Gary Palmer By command-line I mean an operating system shell.  Don't know what you call it on the Mac, but Terminal has the right flavor.

If and when the script is working, the memory usage can be turned off by running it with

maple -q -F your_script.mpl

However, being able to see what it is doing is useful during debugging. One way to turn off just the reporting of memory usage is

maple -F -c 'kernelopts(printbytes=false)'  your_script.mpl

Try plotsetup(maplet) with a sample script that plots something and whichi you know works. It's quite possible that in the course of exporting and manually fixing a bug has crept in. What I generally do is wrap the entire script into a procedure, declare all the variables [as locals or globals], then run mint on it (the Maple syntax checker).  Executing the procedure allows me to use the debugger and step through the code (full disclosure, I've written an extension to the Maple debugger that makes this a bit more convenient).

@Gary Palmer By command-line I mean an operating system shell.  Don't know what you call it on the Mac, but Terminal has the right flavor.

If and when the script is working, the memory usage can be turned off by running it with

maple -q -F your_script.mpl

However, being able to see what it is doing is useful during debugging. One way to turn off just the reporting of memory usage is

maple -F -c 'kernelopts(printbytes=false)'  your_script.mpl

Try plotsetup(maplet) with a sample script that plots something and whichi you know works. It's quite possible that in the course of exporting and manually fixing a bug has crept in. What I generally do is wrap the entire script into a procedure, declare all the variables [as locals or globals], then run mint on it (the Maple syntax checker).  Executing the procedure allows me to use the debugger and step through the code (full disclosure, I've written an extension to the Maple debugger that makes this a bit more convenient).

@Gary Palmer Ideally you could just export to a .mpl file, then, from the command line do

maple -F your_export.mpl

The -F is to prevent Maple from exiting after it process the script.  You will probably have to make some changes to the script.  For example, some of the 2D math, if that is what you used, might need to be tweaked a bit, but possibly not. You will have to assign a plot driver.  By default the command line uses a text based plot driver.  Not sure what is appropriate for the Mac, but probably plotsetup(maplet) is what you want.  Add that before doing any plotting. Best thing to do is try it and see what happens.

@Gary Palmer Ideally you could just export to a .mpl file, then, from the command line do

maple -F your_export.mpl

The -F is to prevent Maple from exiting after it process the script.  You will probably have to make some changes to the script.  For example, some of the 2D math, if that is what you used, might need to be tweaked a bit, but possibly not. You will have to assign a plot driver.  By default the command line uses a text based plot driver.  Not sure what is appropriate for the Mac, but probably plotsetup(maplet) is what you want.  Add that before doing any plotting. Best thing to do is try it and see what happens.

@Markiyan Hirnyk Hmm.  Maybe not. Assuming E(sqrt(x)) = sqrt(E(x)) probably wasn't my cleverest move.

@Markiyan Hirnyk Hmm.  Maybe not. Assuming E(sqrt(x)) = sqrt(E(x)) probably wasn't my cleverest move.

@Christopher2222 It should be close enough.  There is some heat transfer to the air from the ends, so that could be modeled, however, unless the beam was rather short and fat, that is probably negligible.

@Christopher2222 It should be close enough.  There is some heat transfer to the air from the ends, so that could be modeled, however, unless the beam was rather short and fat, that is probably negligible.

@Christopher2222 That's slightly tricky because it changes the form of the boundary condition, from Dirichlet, T(0,t) = T0, to Neumann, D[1](T)(0,t) = 0.  What you'd really want to do is to call pdsolve a second time, with the new boundary conditions and with the initial conditions imposed by the state at the transition.  Not sure how easy that is to set up.  Alternatively, you could modify the boundary condition so that it models a conductance from the end to a constant temperature source, and then drive the conductance to zero. The latter is how I'd model this with MapleSim.

@Christopher2222 That's slightly tricky because it changes the form of the boundary condition, from Dirichlet, T(0,t) = T0, to Neumann, D[1](T)(0,t) = 0.  What you'd really want to do is to call pdsolve a second time, with the new boundary conditions and with the initial conditions imposed by the state at the transition.  Not sure how easy that is to set up.  Alternatively, you could modify the boundary condition so that it models a conductance from the end to a constant temperature source, and then drive the conductance to zero. The latter is how I'd model this with MapleSim.

@Christopher2222 D[1](T)(2,t)=0 means the temperature distribution is not changing with distance at x=2.  That implies that there is no heat flow through the end.

To get particular values you can do

Tnum := sol:-value(T):
Tnum(2, 3*60^2);
                 [x = 2., t = 10800., T = 288.149999999999977]

@Christopher2222 D[1](T)(2,t)=0 means the temperature distribution is not changing with distance at x=2.  That implies that there is no heat flow through the end.

To get particular values you can do

Tnum := sol:-value(T):
Tnum(2, 3*60^2);
                 [x = 2., t = 10800., T = 288.149999999999977]