I wanted to try this simplification in Maple 2025, only to find timelimit hangs.

Waited 3 hrs when timelimit was 30 second. It seems simplify got locked up and timelimit does not work.

Not only that, Maple itself hangs and clicking on retsrat kernel or red small bottom at lower level corner in Maple 2025 has no effect at all.  

Only way is to kill all of Maple from command line.

Make sure to save all your work before trying.

There are two bugs here: First is that timelimit still hangs (even though Maplesoft claimed it is fixed almost 5 years ago)

https://www.mapleprimes.com/maplesoftblog/213986-Introducing-Maple-Learn-officially

You will also be pleased to know that Maple 2021 addresses the timelimit() issue that you mentioned.

The second issue is that one can not close the kernel from frontend. (well, this is because kernel hanged)

Note that closing Maple works using File->EXIT but this leaves the Maple kernel/mserver  running  in background!

So had to go kill that process from command line manually also.

So make sure to do this, else you will end up with many mserver processes running in background after maple is closed if you try this more than one time.

Any one knows why this happens for this example? Should not timelimit have finally been fixed in Maple 2025?

I have been complaining about timelimit not always working for ages. Have no idea why Maplesoft can't figure solution to this problem for good. 

timelimit is the most important command for me, as without it, my program will never work and will just keep hanging.

I spend 50% of my time finding worarounds around Maple bugs instead of what I should be doing which is write more code.

Download timelimit_hang_in_maple_2025.mw

is it possible to ask Maple to verify ode solution obtained from book, which is given in parametric form to check if it is correct?

I know odetest supports both explicit and implicit solutions. But parametric solution is neither of these.

The solution in parametric form makes it look simple to look at and understand, but at same time, not practical in terms of obtaining an explicit solution to verify it and to use it.

The book "handbook of exact solution for ordinary differential equations" by Polyanin and Zaitsev have many such solutions.

Here is one such example of many

I can not just give odetest the y(x) solution above, because the right side depends on tau, which is parameter. If I try to solve for tau in terms of x from the first equation it will become so complicated and odetest hangs. So a whole new different approach is needed as brute force method is not practical in most cases.

Download how_to_verify_parametric_solution_to_ode.mw

Some more examples from the book where solutions are given only in parametrric form

update

inspired by solution below by @acer, I found if I just use Solve on the x equation, in order to find t as function of x, and use that in the y equation, it will automatically return solution using RootOf.

Hence no need to explicitly evaluate the integral or explicity set up the RootOf manually.

Now odetest work. 

Download how_to_verify_parametric_solution_to_ode_V2.mw

Is there a trick to make Maple simplify 

to

I can't use the exp() trick given in earlier questions, since there is no exp here. Below are my attempts. Can someone find another smart trick to do this simplification? Should simplify() have simplified it as is with no assumptions or using tricks? This is all done in code, so solutions can not depend on "looking on screen" and deciding what to do for each step.

Download simplification_may_8_2025.mw

For reference, using another software

I asked similar question 5 years ago about Physics update but it was not possible to find this information

How-To-Find-What-Changed-In-Physics

I'd like to ask now again same about  SupportTools. Can one find out what update is actually included in new version?

Even if it is just 2-3 lines. It will be good if users had an idea what was fixed or improved in the new version.

Any update to software should inlcude such information. Not asking for details, just general information will be nice. Right now one does an update and have no idea at all what the new update fixed or improved which is not good.

May be such information can be displayed on screen after a user updates?

according to what is new in Maple 2025, it says

• Maple 2025 introduces several important improvements to simplify regarding expressions containing exponential, trigonometric, hyperbolic, and/or inverse trigonometric functions, resulting in more compact results. Other commands in the math library also provide simpler results due to these improvements.

But I still see weakness in simplify. (see also recent question).

Here is an example, A and B below are equivalent mathematically. But A is almost twice as big. So one would expect simplify(A) to return B. right? But it does not. Also using size option has no effect.  

Does one need more tricks in Maple to make it simplify this? Is this not something that a powerful CAS software like Maple should have been able to do?

Download why_can_not_simplify_may_4_2025.mw

Using another software, all what is needed is call to Simpify to do it:

I also tried my most power full_simplify() function in Maple, and it had no effect

full_simplify:=proc(e::anything)
   local result::list;
   local f:=proc(a,b)
      RETURN(MmaTranslator:-Mma:-LeafCount(a)<MmaTranslator:-Mma:-LeafCount(b))
   end proc;

   #add more methods as needed

   result:=[simplify(e),
            simplify(e,size),
            simplify(combine(e)),
            simplify(combine(e),size),
            radnormal(evala( combine(e) )),
            simplify(evala( combine(e) )),
            evala(radnormal( combine(e) )),
            simplify(radnormal( combine(e) )),
            evala(factor(e)),
            simplify(e,ln),
            simplify(e,power),
            simplify(e,RootOf),
            simplify(e,sqrt),
            simplify(e,trig),
            simplify(convert(e,trig)),
            simplify(convert(e,exp)),
            combine(e)
   ];   
   RETURN( sort(result,f)[1]);   

end proc:

Calling full_simplify(A) did not simplify it.