@acer Thanks! 

I tried Typesetting instead of typeset.  I probably would have eventually come across an example somewhere but I was going crazy looking at so many examples that didn't have it. 

Thanks again

@Ronan ok no problem.  I came across the same error yesterday but couldn't figure a way around so in my case I had to remove the limitations in the precision.

@acer ok thanks.  So luckily the error, so none of the library routines were changed. 

Sorry I haven't posted an example yet, still playing around with it. 

Acer, I just came across another related post of yours 3D Plot size option , it appears it was written for Maple 2019, I ran the code on Maple 2022 but Maple is throwing the error

So currently trying to figure out how that command was changed from 2019 to 2022.  Probably a compatability issue at some point. 

@acer thanks acer that's very helpful.  I'll have a look at the links you gave. 

I believe simplify tries to move things into ONE term, and it simplifies it as best it can get with it all in 1 term.  

Making it simplify to 2 terms is another ballgame.

Perhaps then if you want simplify to perform as you think it should then possibly it would be better if if had a term argument?  Specifying you want it simplified to 2 terms or 3 even where the default is 1?  Just a thought.  But then it's starting to take on the role of expand, that is moving a solution from 1 term and "expansing" it to 2 terms.

There should be a repository somewhere.  However I doubt these tiny fixes will be mentioned. 

On that note does this mean the minor updates like 2025.1, 1025.2 etc will no longer exist?  Those fixes show what was updated but if that avenue is no longer then I would hope SupportTools update would have some kind of fix log.

A bug, probably internal code that tells maple where to link within the help pages was renamed/moved or deleted.

@Scot Gould Interesting.  version 15 must have been uploaded just after I looked at the maple.cloud webpage - as it was labelled v 13 when I last saw it. 

So if you had version 13 specified and it loaded v15, then that would indeed make the version# irrelevant.  Of course that begs the question - if the version specifier is irrelevant and the most recent is updated and it breaks maple, how then would one revert to an older update?  I'm sure it would get fixed relatively quickly, in which case then the question is moot.

Basically what I'm saying is, is it better to put these commands in an initialization file or a library archive?

I understand that an initialization file is immediate and an archive only occurs when the command is invoked, however lets say I'm updating some scientific constants (for example the mass of the sun or earth to more decimal places)

with(ScientificConstants):

Modify(M[Sun],value=xxxx, undertainty=xxxx)

or the mass of a proton or neutron to better precision. 

What I mean to say is to update Maple to more exact values, it's an update so I guess that would mean to apply it as an initialization file.  How does the Maple update file work - it doesn't just keep adding to an initialization file, it's a package - or some kind of a module correct?

@Scot Gould Great! 

You would only know the latest version number by going on the maple.cloud website. 

Or I think it may be similar to the way the Physics package worked.  Probably similar to Physics:-Version(latest) ... oh I think SupportTools:-Version(latest) might work I don't have Maple 2025 so I can't check if that works. 

Under ModifyConstant the help page states

To update a constant for all future Maple sessions, add the ModifyConstant command to your Maple initialization file.

So if I was updating a whole slew of constants (be it more decimal places, more identifiers, more constants) am I to believe we are to use the initialization file as the transport element for these changes?  I mean is it ideal to have a very large initialization file or would the library archive make more sense?

@Scot Gould maybe download the package manually to your machine and install the package that way.  It is unlucky version 13 now - maybe that's a factor?

To download manually, enter this in your browser
https://maple.cloud/downloadDocument?id=4797495082876928&version13

then run PackageTools:-Install("Maple+Customer+Support+Updates.maple") on the downloaded file,
of course inside the quotes will be the location of the file.

**edit added ** I think also you need to include the overwrite command.

Symbolic computation is one area Maple can not be beat. 

Factorization, Polynomials.  When it comes to numerical solutions Mathematica is good, when it comes to finding exact solutions Mathematica is very slow.  When it comes to sybolic solutions Maple smokes Mathematica, so it's not as dire a statement Wolfram makes it out to be in their comparison. 

As noted here over at stackexchange https://mathematica.stackexchange.com/questions/311157/does-mathematica-have-weaker-symbolic-computation-especially-symbolic-polynomia

@sursumCorda Just had a look at that.  Looks like Wolfram is really raining down on Maplesoft with some of their bold statements.  Like this last one "For those capabilities that Maple has implemented in the last 10 years, the median time lag between features being introduced in Mathematica and basic implementation in Maple has been around 10 years.  If you want access to deep implementations of the very latest in computation, you should be using Mathematica."

What features are they talking about?  It's open to so much interpretation.  Also that last statement of theirs "deep implementations of the very latest in computation, you should be using Mathematica."  ... Really??!!  Is it really that justified that they can state that?  We need to either step up, but I think rather stomp out those war of words is the course of action here.