MaplePrimes - answers and comments on Question, A problem with using "subs" command

substitute for what?

Axel Vogt — Sun, 14 Oct 2012 23:12:14 Z

You need to provide the rule for "old to new", what has to be done

The syntax is subs( currentExpression = newExpression, termToWorkOn), algsubs is similar.

Likewise you can try eval(termToWorkOn, currentExpression = newExpression)

And it is simply not clear, what you want to do.

Note that D_0 etc does not make sense, except you mean constants and that your expressions
do not depend on your variable t.

2-D input trap

Alejandro Jakubi — Mon, 15 Oct 2012 00:54:13 Z

The problem here is a 2-D input trap. The third line of your 1-D input shows the name `#mo("⋅",fontstyle = "italic")` which typesets as a dot. If it slipped into your input by use of a menu, my advice is avoid them. Or better yet, avoid the usage of 2-D input altogether. It is full of traps!

In reply to Axel:

kobi — Mon, 15 Oct 2012 11:05:51 Z

The term "thetaScaleDefinition" includes the "old to new" rule.

I am trying to implement a "multiple time scale" solution to a problem, whereby these kind of expressions are required to be developed. The complete model is too complex to include here, and actually not connected to this problem.

I've tried the same expression without using subscripts (i.e using D1,D2 instead of D₁,D₂ ) but the problem persists.

Using 2D input

kobi — Mon, 15 Oct 2012 11:14:44 Z

Thanks a lot Alejandro. I did not use a menu for creation of the input lines. I simply typed "*" for multiplication, as I prefer to have a multiplication sign rather than a space between the two multiplied arguments.

bug?

Alejandro Jakubi — Mon, 15 Oct 2012 12:53:18 Z

@kobi

One of the problems with 2-D input is that what you get may depend on non-recorded GUI interactions (mouse clicks and the like), resulting in a process hard to reproduce. If you have got somehow that "sdot" TypeMK name just by typing "*", it sounds to me as a bug.

have you tried the classical interface ?

Axel Vogt — Mon, 15 Oct 2012 16:31:20 Z

Have you tried to use the classical interface ?

I think it is better for controlling the input ...

PS for my answer below: sorry, obviously I did not
recognize the rule ... seems, it was too late ...