Thomas Richard

Mr. Thomas Richard

3255 Reputation

13 Badges

15 years, 61 days
Maplesoft Europe GmbH
Technical professional in industry or government
Aachen, North Rhine-Westphalia, Germany

MaplePrimes Activity


These are answers submitted by Thomas Richard

Recently (weeks ago) I had the same problem on one of my machines, and it turned out to be a side effect of a certain Physics update that had meanwhile been fixed. So if you are using the Physics package, make sure to keep it updated.

If the problem persists, please tell us the output of Physics:-Version();

You got it almost right; the command is SetProperty rather than setProperty.

Furthermore, I would check "Continuous update on drag" (or "Update continuously while dragging"  in older versions) in the Component Properties dialog for the slider.

If so, then I guess the answer is obvious. ;-)

But if you have specific feature suggestions, feel free to send them to support@maplesoft.com and/or discuss them here.

You didn't provide any executable example (code snippet or worksheet), but this is how it is done in principle. Suppose sol is your procedure returned by dsolve/numeric. Then, after the halt has been triggered:

sol(eventfired=[1]);

For the details, please see section "Interactive features" under ?dsolve,numeric,Events.

About question 2: insert

interface(warnlevel=0):

before calling sol.

But I would not suppress warnings globally. In general, they are useful. I've set warnlevel to 4 in my initialization file. Default value is 3.

Your original get_plot procedure issues no warning because it is technically correct.

If you want to see additional diagnostics, then do

maplemint(get_plot);

Note that maplemint has been updated in Maple 2018; please see Help > What's New > Language & Programming.

newsys := eval([e||($1..10)],mu=5);

Have you tried the TripleScalarProduct command of the Student:-MultivariateCalculus package?

To see the policy, just follow the About link at the top right of MaplePrimes, and see bullet item 1:

... as well as general interest topics in math and computing.

Which doesn't mean that we're all eagerly waiting for homework questions, though. ;-)

To display symbols properly, you will need to wrap the legend strings into typeset calls, like this:

legend=[typeset("Flat Prior ", 'Beta(1,1)'), ...]

Note the single quotes around Beta(1,1) which would be evaluated as 1 otherwise, because Maple knows the Beta function.

For more info, please enter ?plot,typesetting to open the help page.

Your expression is an algebraic function (see ?type,radalgfun for the definition), and the recommended command for evaluating these is evala. [There is actually a whole machinery (mathematical theory and Maple packages) behind it, but let's keep things simple at this point.]

In many such cases, radnormal will also do the job, but why would I type 9 letters if 5 suffice? ;-)

There's a number of possible reasons for blocking the launch of the GUI. Please see our FAQ page on that.

Have you tried increasing the interface variable screenwidth? It defaults to 79 in command line Maple.

Please consult our FAQs: https://desktopfaq.maplesoft.com/customer/en/portal/articles/2840902-maple-does-not-start

They have not only been restructured, but also extended, so that more situations (problems and solutions) are covered now.

Futhermore, for Windows 10 users who had installed the so-called Creators Update: that makes trouble with several applications including Maple. They can crash upon starting or saving files, at least on some systems. In that case, unrolling that update helps, or – if that is not an option – deleting the so-called God-Mode by removing the

    C:\Users\%USERNAME%\Desktop\GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}

folder.

The PDEtools package has the proper command for this task: DeterminingPDE. However, your jet-like notation will need to be adjusted a bit to be processed by diff_table.

I'm not an export on that topic, but this should get you started to do further symmetry investigations:

with(PDEtools):
declare(Q(x,t),R(x,t)): # optional
q := diff_table(Q(x,t)):
r := diff_table(R(x,t)):
pde1 := q[t] = alpha[3](t)*(q[x,x,x]-6*q[]*r[]*q[x])+alpha[2](t)*(2*q[]^2*r[]-q[x,x])+alpha[1](t)*q[x]-alpha[0](t)*q[];
pde2 := r[t] = alpha[3](t)*(r[x,x,x]-6*q[]*r[]*r[x])+alpha[2](t)*(-2*q[]*r[]^2+r[x,x])+alpha[1](t)*r[x]-alpha[0](t)*r[];
sys := [pde1,pde2]:
detsys := DeterminingPDE(sys);

As you can see, I renamed your original functions to uppercase Q and R...

Your first input line is most probably a result of some copy&paste error. Simply replace it by

with(simplex):

 

First 13 14 15 16 17 18 19 Last Page 15 of 43