• I cannot reproduce the error (see the attachment) with Maple 2022.2. What do you use?
• You assume the upper bound of the integral smaller than the lower bound. Is that what you want?
• evalf introduces numerical inaccuracies which can prevent simplification of expressions. It should be used after simplification but not before
• Maple assumes that the other indeterminants zeta, kappa, m, mu, p are complex if not otherwise assumed. I have doubts that there is a solution. Maybe in the real domain.

ex-2_reply.mw

@acer

Very helpfull for fine tuning. Thank you!

After forcing (via the Nvidia control panel) an exclusive use of the internal intel graphic processor for Maple and MapleSim the error was gone.

When the startup problem appeared again (startup termination looked a bit different) a “reset” of 3d-settings of the graphic card to “OS manages the graphic processors” solved the problem.

(To the best of my knowledge the graphic card settings where never modified by a user action.)

@ Moderators: Can you make this anwser a reply and anwser this question as beeing answered to remove it from the list of unanswered questions?

@dharr 

An example in the help page with arguments would have been helpfull. Your statement is also simpler than:

subsindets(expr, with_unit, z->convert(z,unit_free) );

Thanks!

@mmcdara 

With Maple 2022 latest improvements its very unlikely that units are wrong in plots unless labels with units are manually entered or useunits is used. Your alternative is like driving a car without safey belts. Once you get used to it you start feeling unsafe. In this particular case useunits works only partially

Unit(('W')/'m'^2)*max(t/Unit('s'), 0);
plot(%, t = -Unit('s') .. 2*Unit('s'), useunits = [ms, mW/mm^2]);

which is a new type of use error not possible before.

PS.: I should have expanded a bit more why I am interest in using max/min. It's a simple way of clipping the amplitude. Piecewise can become complicated. It looks to me that plot does not recognize that the max statement in my original expression is unitfree dimensionless and strips of all units when it encouters functions like max

Unit(('W')/'m'^2)*max(t, 0);
plot(%, t = -Unit('s') .. 2*Unit('s'));

that would otherwise return unevaluated as

max(W/m^2, 0)

There are probably more cases with a similar behavior. I was hoping for a kind of uneval trick that would make plot  throw an error (prevent stripping of all units) if statements are used that do not evaluate numerically.

@nm 
Thanks!

PS.: Before asking I tried this one

plot(ifelse(0 < t/Unit('s'), t, 0), t = -Unit('s') .. 2*Unit('s'))

@Carl Love 

That makes sense.

@Preben Alsholm

👍 for answering my question.

IMO: It should be a) with anwser in the title.

@Preben Alsholm 

That should not be possible. Try frist to remove your answer to see if this removes the 7 pts already and to check whether the question is again listed under unanwserd question.

@all

If I interprete the output of

dismantle(expr)

correctly there is indeed an outer product of -1 and the rest

SUM(3)
   PROD(7)
      SUM(5)
         NAME(4): r0
         INTPOS(2): 1
         NAME(4): Delta_r
         INTPOS(2): 1
      INTPOS(2): 2
      SUM(5)
         NAME(4): r0
         INTPOS(2): 46
         NAME(4): Delta_r
         INTNEG(2): -41
      INTPOS(2): 1
      NAME(4): r0
      INTPOS(2): 5
   INTNEG(2): -1

From the programming guide:

The simple product handling is not well implemented in subsop which to my oppionion should work as described. It should substitute as op() list operands.

restart;
expr := -(r0 + Delta_r)^2*(46*r0 - 41*Delta_r)*r0^5;
subsop(1 = a, 2 = b, expr);
                            #  a b

@Thomas Richard 

It's a workaround for formating a single output and afterwards resetting to default by

interface(displayprecision = -1)

Thanks. 

@dharr 

Yes, I know.

The consequence is that such settings apply for a whole session and not for the worksheet. Since I have almost always more than worksheet open I do not want these settings to propagate to the other worksheets.

For others that might be a workaround.

@acer 

My eyes need a rest...

@acer 

Nice! I stop proposing better code because I could not call MakeInert this way inside a procedure:

InertFrom:-MakeInert(a);

restart;
a := 2*Unit('m');
InertFrom:-MakeInert(a);
with(InertForm):
MakeInert(a);

Why is that? Must I use uses?

@Carl Love 

Thank you. It is always worth taking a closer look when nm observes something during his/her extensive investigations.

I was about to ask a separate question whether and how the boundary to the complex domain can be determined or drawn, but decided against it because it is purely of interest and the question channel is quite busy.