Joe Riel

8313 Reputation

22 Badges

15 years, 288 days

MaplePrimes Activity


These are replies submitted by Joe Riel

In your worksheet, using your times, Scale is the fastest (by a small margin). 

A few minor comments.  Probably you don't want to use the extension mpl for the mint output file.  You can, but that is kind of strange in that the output is not Maple code. Without the -o option, mint writes to the screen (in linux that means writes to stdout, I don't know the terminology for Windows but am pretty sure it is equivalent); with the -o option it writes to the file specified by that option.

@Bendesarts You are correct in that if there are syntax errors you won't be able to create an mla file.  However, that will always be an issue.  The ideal solution is to run the file through the Maple mint utility, which detects such errors.  So far as the time taken to create an mla, that is likely not an issue.  I work with a package that loads hundreds of Maple files; it only takes a few seconds to rebuild the mla. Because I work with an editor that is readily customizable, I have it set up so that a function key does the rebuild.  Another key runs the particular file I'm working on through Maple mint.  A cautionary note:  on Windows things are likely more a pain.  I suspect that rebuilding an mla might be problematic if it is being used, say by an open Maple worksheet.  That isn't an issue on Linux. My usual workflow is to edit the Maple source, rebuild the mla, then click the Restart icon in whatever Maple worksheet I'm using to test the code.

I don't understand what you want.  How about a couple of examples of input and expected output.

@Carl Love I don't believe compiled procedures can be stored in an mla (not sure about that).  An alternative would be to rewrite the internal procedures in C and provide binaries with the Maple distribution (that's done for other stuff), but it's more work for little benefit.  When creating and debugging iterators it is convenient to be able to use compile=false and then step through the iterator in the Maple debugger; that wouldn't be feasible if the internal procedures were in C.  On the other hand, am currently (itermittently) working on a new iterator which could be significantly faster if written directly in C.

@Carl Love Please email me the info; I can add it to the internal bug report (which I haven't yet seen).  There were some changes to add (and seq) for 2021; I don't work on them.

@Ronan As Carl mentioned, using compile=false is a reasonable way to avoid the one-time delay for a small iterator. In Maple 2020 the delayed compilation method used by the Iterator package was modified so that the compilation occurs when an iterator is first generated; previously it occurred the first time an iterator was used (expanded).  So for a particular iterator type (the numerical arguments don't matter) you could assign a throw away version in the startup code. For example
 

Iterator:-CartesianProduct([1,1]):

Now any subsequent usages of a CartesianProduct iterator will not have to recompile.  That works even if they are used in separate threads

@Anthrazit To replace an existing Maple Cloud document, you need to ensure that the Document Properties used by Maple Cloud match those of the original; without that there won't be a "Publish Update" button in the dialog that appears after sending the book to the cloud. Open the Maple book and inspect the Document Properties (File > Document Properties).  The important ones are those that start with "X-Cloud" and "application_type", "authors", "description", "language", and "title", however, you should be able to ignore the X-CloudVersion, since that is incremented by the cloud site.  The others must match the original (possibly some could be changed, but its probably safer to change them at the site).

I generate Maple books from a Makefile so don't actually have experience in manually changing these properties, but it should work.

Followup When you first upload a Maple worksheet/book to the cloud, be sure to save the file after doing so.  The process of uploading it adds the fore-mentioned Document Properties.  If you didn't save it, they won't exist when you go to update.  In that case, you should start by downloading the file. 

I haven't noticed that. I've had issues updating packages, but that's a separate issue and caused by me making changes that prevent Maple from identifying the book as an update. What do you observe after you click the "Upload to Cloud" selection?

@AmusingYeti Note that kernelopts(platform) returns "unix" for both linux and Mac OS X.  If you need to distinguish them, consider kernelopts(system).

I uploaded a Maple package, UTF8, that uses native methods for similar functionality, onto the Maple Cloud a few years ago.  

@Jaqr It seems unlikely, then, that limited disk space is the issue. 

That is possible. On linux, Maple normally uses the /tmp directory.  How much do disk space do you have there?  Use, say,

df -h /tmp

 

@acer The example in the LibraryTools:-Save help page is frightening; if executed it would save directly into the main maple mla.

What's the application?  That is, given a Maple worksheet, do you want determine what comboboxes are in it?

I have a command-line tool, written in Maple using the Bark package available on the Maple cloud, that I use from the linux command line to inspect and modify worksheets.  For example, here I use it to determine what comboboxes exist in a given worksheet:
 

$ ect Linearization.mw --type=ComboBox
cmbInputVarRoot
cmbOutputVarRoot
cmbInputVar
cmbInputSignal
cmbOutputVar

If interested I could push it to the cloud (might take a while to get it ready).

1 2 3 4 5 6 7 Last Page 1 of 186