@Markiyan Hirnyk That restriction holds for the numerical solvers only.

@Axel Vogt PS: I can not see, wether Int or int was used in the original question (but that's probably minor)

You can deduce from the blue integral sign in the output that the input was int. The inert form Int would have produced a grey sign.
Actually, it was entered via the Expression palette (or Calculus palette in Maple 18), which inserts the 2D Math Input equivalent of int. You can see its syntax when hovering the mouse over the palette item.

This is because the Grammians command has to call either LyapunovSolve or SylvesterSolve from LinearAlgebra. There are no symbolic solvers for these matrix equations. The help pages for these commands explicitly point out:

This routine operates in the floating-point domain. Hence, the entries in the Matrix arguments must necessarily be of type complex(numeric).

A similar hint should be added to the Grammians help page, I think.

@Alejandro Jakubi Yes, the hotwin etc. pages are the correct place for this. But AFAIK, dot releases generally do not update help pages, mainly because that would increase download sizes considerably. Most relevant changes are listed on the download page itself. I think that's a good compromise.
However, I'll submit an SCR making sure the new shortcut is covered in the next major version docs.

For several reasons, I don't agree with you about its location in the menu structure. The Edit menu already has other Execute entries. And it has other items that affect the whole worksheet - this is not unique to the File menu. Finally, executing is not a file operation. It usually generates output, changing the appearance of the content. So this can be seen as editing.
By contrast, having a top-level Execute menu sounds reasonable to me.

In 1D input mode aka "Maple notation", I'm getting a more specific error message:

Error, unexpected `local` declaration in procedure body

In 2D Math input, Maple helps you by highlighting the local keyword. That's very close to the actual input error location. If you remove the colon between proc(f,g,var) and local, Maple will accept your procedure definition. See ?proc for the syntax details if needed.

For programming tasks like this, I recommend the combination of Worksheet Mode and Maple notation.

@acer Note that there is a special situation with memory usage by external libraries on Mac OS X, mentioned on the ?platform help page. Mac Dude might set kernelopts(freebundle=true) to overcome that.

@Kitonum You can avoid introducing floats and converting them to rationals:

convert(1/(x^2+2*x+2), fullparfrac, x);
allvalues(%);

@Preben Alsholm Very nice. An optional check confirms that result: pdetest(res2,[pde,bcs]);

@jwhyte As you wrote about version 16.00, you should install updates 16.02 and 16.02a from here, and check if the problem persists. The FAQ you listed is referring to 16.01, which is included in 16.02.

@Alejandro Jakubi It's actually mentioned in the 18.01 update docs. But I must admit I had overlooked it.

Its location in the Edit menu is correct, I think. Where else would you place it?

I'm not sure why that happens, because I cannot reproduce the problem. But another customer recently confirmed that updating to Maple 18.01 and/or adding option linestyle=solid to the spacecurve call helped.

@federave Thanks for your detailed instructions. I was now able to reproduce the error message. Unfortunately I have no idea about its origin, but I will discuss this with my colleagues soon. If we have any hints, we'll let you know.

As far as I know, the model is from 2008 (when MapleSim 1 appeared, based on Maple 12), and might need some adjustment to properly run with the latest versions of MapleSim and Maple.

The only suggestion I have for now is to avoid storing a new parameter set here, and make the required changes directly in the Maple worksheet, still using the "Symbolic.params" file. Does that work for you?

@federave I tried to run both of your msim files. The one titled modified_DoubleWishbone.msim sort of "runs" but gives nonsense output, both in some 2D plots (from scopes) and for the 3D animation, besides some warnings and non-fatal errors. I see the error message from the screenshot in the DefiningHardPoints.mw attachment, but I have no idea about its origin. Probably a side effect of your modifications.

The other one called DoubleWishbone1.msim doesn't even simulate; the error message is "unable to find `TSDAKs` in model `Main.DWS` while expanding `Main.DWS.TSDAKs`". You still need to instruct MapleSim to use that Parameter Set called "new" (either in the Parameter Sets pane on the left, through context menu > Use, or in the Inspector on the right, by clicking the green check mark). But that doesn't solve the problem. When using the original parameter set again, MapleSim notifies you about some inconsistency.

So it seems you somehow messed up both files. At this point I'm unable to help, sorry. Please download the original file again and try to describe each step you took. As I said, it runs well here, even when I store the current parameters under a new name. There must be still some info missing from your end.

@federave Thanks, your posting is much better readable now.

I don't need any further screenshots, but your edited worksheet. From the first screenshot, we see that you changed index 39 to 62, and there must be some more changes, because it's still running fine on my system even when I store the parameter set in MapleSim.

Alternatively, give a precise list of your actions (after downloading the msim file) so that one can reproduce the error.

I suppose you have updated to MapleSim 6.4.01 and Maple 18.01; if not, look here.

Please insert clickable links in your posting. This can be done by highlighting a word in the editor and then selecting "Insert/Edit Link" from the context menu (right mouse button). Copying&pasting URLs is cumbersome for readers.

Next, upload your edited worksheet, using the green arrow-up button in the editor. Your screenshots are insufficient for diagnosing the problem. The original worksheet runs correctly on my system.

By the way, since you tagged your posting with "Maple 18", I guess you are using current MapleSim 6.4. Version 6 was for Maple 16. However, the model and its worksheet will run in both versions.