Is it possible, and how, to disable the automatic completion in the "Advanced Search / keyword" field ?

Underlying this question is my looking for informations about cmaple (beyond what the help page displays : if I can't find any I will ask some specific ones later). But every time I type "cmaple" in the keyword textfield, it is replaced by "campée" (which is a french word ... I guess english people will obtain something different)

It is very common, in Modeling and Simulation activities, to account for Uncertainties.

In order to set these ideas down, consider a computational code F (typically a code that solves a set of PDEs in space (M) and time (t) ) and its response Y = F(M,t) (here Y is a short for Y(M,t)).

This response Y usually depends also on some set P of parameters (each of them considered as a scalar quantity) .A more convenient way to note Y is Y(M, t | P) where the "|" character is used here to express that Y is considered as a function of M and t for each given value of P.Generally one does not consider Y as a whole but more often one focuses on some quantity of interest (Q) derived from Y through applying it some operator G (for example the operator max(Y) over some space and time domain).

Applying G generally makes Q to appear as a function of P alone.In Uncertainty Quantification activities, a major concern is to understand how uncertainties about P modify the values of Q ?The classical framework is to consider P as a (multi-dimensionnal) random variable. One of the most common problems is then to assess some basic characteristics of Q, where Q is considered as a function of P (a quick and notional notation is Q = H(P) = (G°F)(X, t | P)).

The simpler and faster method to do this is based on a Taylor expansion of H (provided some conditions hold) arround some particular point p* (p* could be the mean of the multi-dimensional distribution of P)One writes, for every value p of P :

Q = H(p) = H(p*) + (H')t (p-p*) + 1/2 (p-p*)t H" (p-p*) ...

where H' is the gradient vector of H according to P at point P = p* H" is the hessian matrix of H according to P at point P = p* (p-p*) is the vector of differences, assumed to be "small"

I would like to define the operator E so that I could derive automatically approximations of the first 4 moments of Q, up to any desired order.In particular, order 2 is often necessary as soon as (G°F) is highly non linear regarding P ; and estimations of the 3rd and 4th moments is of great help to determine how much symetric or flat is the distribution of Q.

The idea is to define an operator E with suitable properties and to apply it to a multivariate taylor expansion of Q^n where n is any positive integer

I tried to do this by my own (look to the supplied .mw file) but I do not have sufficient skill in Maple to complete the job.

Could someone help me ?

Even if I am not qualified in saying this, I believe that this type of approximation of the different moments of Q could be included in a future release of Maple ?

# CAN WE TRUST MAPLE ?## I want to solve numerically systems of ordinary differential equations (ODE)## File "MC.m" below contains an example of one of them (a second degree ODE # reduced to a couple of 2 first order ODEs ; details about these equations # are of no importane here).## I am going to show you a very disturbing behaviour of MAPLE ...#restart:with(plots):read "/Users/marcsancandi/Desktop/MAPLE++SCILAB/BUG-LSODE/MC.m":# A very quick look to the ODE system ## (0.2345... is the mass of the "moving mass" ; some of you will # probably recognize the structure of a mass-spring-damper system)## Here again, the detailed expression of the 2 RHSs does not matter#map(u -> if is(rhs(u), numeric) then u else lhs(u)=RHS end if, convert(MC, list));

# In fact the value of sol(8.1) depends on the value T had during # the previous evaluation sol(T).# Which suggests that, maybe, some global variable has not been # properly erased when sol(..) is evaluated (?)

# Observe these results are very similar to those obtained with lsode## But what are the results I obtaine by pointwise evaluations of# sol(t) for t in 7.8..8.2 ???## 4/ Now evaluate "pointwise" sol(t) for the times retained print();printf("\n What sol(t) gives for the same values of t\n");printf("------------------------------------------------\n");printf(" t V(t) X(t)\n");printf("------------------------------------------------\n");for MyTime in ListOfPoints[GoodRows, 1] do MySol := map(u -> rhs(u), sol(MyTime)): printf("%-15.12f %-15.12f %-15.12f\n", seq(MySol[n], n=1..3)) end do:print():

What sol(t) gives for the same values of t------------------------------------------------ t V(t) X(t)------------------------------------------------

# Wow, these two tables give very close results (at least if you don't look# farther than the tenth decimal position ... which could probably change# by fixing Digits to 15 or 20 (?) ... even if this hypothesis is not # fully satisfactory ?)## Here pointwise evaluations of sol(t) always give the correct answer (up to# the decimal representation induced by the default value of Digits).###------------------------------------------------------------------------## Question : why the "magics" no longer operate with rkf45 ?# (of course it is humor at the second degree !)##------------------------------------------------------------------------### It could be funny to play with "Magic MAPLE".## But I have to solve serious problems, and among them, what interests me# in the solution of the "MC" system, is "events capturing".# Example of such an event "event" E_n is "the moving mass has reached the # position X = S_n where S_n is a given stroke (for exemple S_N = 0.006).# And "capturing E_n" then means "find the time T_n such that X(T_n) = S_n".## I thus wrote a fixed-point method to do this, that is a procédure that# repeatedly asks for evaluations of procedure "sol".# But, for the behaviour depicted above, it doesn't work correctly with lsode.# So, despite the funny magical behaviour of MAPLE, I have a serious problem !## A problem I can sum up while saying ## "I CANNOT TRUST MAPLE WHEN IT SAYS ME sol(t) = xxx"### Has anyone already been faced with these kind of behaviour ?## Maplesoft support seems to beat around the bush with me, asking for the # ODEs equations, or criticizing the expressions of their RHSs ..., wanting# to see where these equations come from (they come from a more than 10.000 # lines application I have developped, but it's not the point here given # rkf45 proceeds correctly).## If anyone is interested to investigate this problem, I can provide # her the "MC.m" file that contains the ODE system used here## Thanks a lot for the time you spent to reading me# #