%0 in the message string in userinfo would give the comma

Download userinfo.mw

@Blanc Is this what you want?

Download CyclicGp.mw

@nm Since you were originally interested in the integral, why not just

seq(evalf(Int(sqrt(1+sin(x)^2),x=0..phi)),phi=-3..3,0.5);

which gives the same as MMA. But if you really want to go from the EllipticE, then

Download EllipticE.mw

@Blanc What calculations do you want to do with them? You can set up these as a custom Group, but if you just want to calculate with them then just using the mod operator is simpler and already built in, e.g. 41 + 27 mod 53. Are you only interested in mod a prime?

@nm You are right - there are different definitions. 

Download EllipticE.mw

@nm I suppose there could be different definitions.

Please define what you mean by primitive element.

@Suryakanth The approximate solution for theta_p you provide could be a straight line going down to zero at Y=10, rather than an exponential decay if you prefer; it only has to look approximately right. I think you are trying to reproduce Fig 2. But there is no f(Y) or F(Y) given so there is not enough information for me to know what they look like and to know what an approximate solution would look like.

As I said, there may be no mistake. (But I didn't check your equations.)

@Suryakanth This does not mean there is an error in the equations (though there might be). Maple needs some help to start with. The solution to this is to give a list of approximate solutions using the 'approxsoln' option. For example, theta(Y) could be given as an exponential decay function, since that is what it looks like; similarly for Theta_p. Only you know what F and f look like.

This error can also arise from an incorrect formulation of the equations. For example a decaying function with BC D(f)(0) = -1 is accidentally given BC D(f)(0) = 1, so then Maple is expecting an increasing function.

@acer I am using Maple 2025.2, so looks like a regression. Looks like the code in `simplify/table` has been updated to use Cache. 

@nm The forget commands at the top of your worksheet just do the forgetting then. I don't know how to change things permanently. If you knew the exact subprocedure which was giving the problem and had option remember, you could perhaps hack it to remove the option but I wouldn't recommend that.

[Edit: the remembered values are in a cache - see op(4,eval(`simplify/table`)), and there is some updating of the table, but it is not as simple as removing option remember.  forget.mw  ]

Yes I see this with the error messages but not when uploading to Mapleprimes. Presumably a Mapleprimes site issue.

@sand15 Thanks for the comments. As a side point I think I found the effect of the ill-conditioning - if I look at the roots of the denominator and numerator polynomials for the [7,9] case, two of the numerator roots are very close to two of the denominator roots, so it is almost equivalent to a [5,7] case.

Also the Statistics package - see the help page ?Statistics,Regression

There is also the Optimization package, but those are in hardware floating point.

Not entirely clear what your specific requirements are.

@salim-barzani I think you are saying you want to keep the ode in G(xi) and not use a specific solution. In many cases the solution to the ode may not be known, but in this case it is just the harmonic oscillator equation, so it seems to be that using the general solution c[1]*exp(h*xi)+c[2]*exp(-h*xi) (or its equivalent sin/cos form) is entirely equivalent to using the ode.

Then from the solved eqs one can select c[1] and c[2] to cover the specific cases you want, sinh, cosh, exp or (with imaginary h) sin, cos, or why not the general solution? In this case the solutions don't depend on c[1], c[2] or h, so any of the solutions works. 

dsolve.mw