@enderw88 Yes, you could transform a subexpression by referencing its position" (which operand it is), or by its type, by its structural identity, by its mathematical nature, or possibly by a few other means (according to the example...).

Which approach would be more robust and appropriate would depend on the particular example as well as what future examples you'd like to mirror with the same approach.

For your given expression, which term did you want to transform, what aspect makes it the term to transform, and how should it be transformed?

I have deleted a duplicate Question thread, for essentially this same set of ODEs (with parameters slightly differently written).

The followup worksheet was this: Error_(1).mw

Please put your followups here, instead of spawning wholly separate new Question threads for this.

You've already split this off from your original Question thread on this topic ("C1" here).

Please don't spawn yet another wholly separate Question thread just to try and figure out a shorter syntax for this manipulation.

Duplicate Question threads get flagged as such, and may be deleted by some moderator.

@Mikey_W I'll try to write out some clear examples. But it might not be this week.

You have not attached your worksheet.

If you intend on using the name `gamma` like any usual, unassigned name then you might want to declare it local at the top-level.

@NIMA112 You could do something like this in Maple 2020.

Adjust your color choices as you wish.

h1_h2_ok_ac_2020_4_ac.mw

For example (and you could remove the 0.0 value from Clist if its contour bothered you).

Using Maple 2023.2 I can reproduce that crash in the GUI with just this.

restart;
G16 := GF(2, 4, alpha^4 + alpha + 1):
print(GF);

If I set  interface(typesetting=standard)  in an execution group right after the restart then I don't get the crash.

@NIMA112 You seem to have access to Maple 2023 sometimes. How about using the colorbar that plots:-contourplot produces in that version?

The second of your plots:-inequal examples (sqrt(3)) works in my updated Maple 2023.2.

The first of your plots:-inequal examples (Pi) works without needed evalf in a beta version of Maple 2024.

Have you submitted a bug report against the solve examples? If not then I'd be happy to do so.

Is this the system that you want solved?

Download trig_sys_real_ex0.mw

@Carl Love Is a bug report submitted? If not, I could do so.

@KIRAN SAJJAN As you can see in the following attachment, this worked for me when I ran it in Maple 2018.2. That file has the system with f1(eta), but no f(eta).

sachi_stream_error_3d_ac_1b.mw

So that handles your first file, as far as I can see. It makes a sequence of 3D contour plots, since that's what you earlier attempt clearly attempted to do. If you want some other style of 3D plot then adjust the style option, or state clearly what else you're after.

Your second file, 3d_sachin_p1.mw, makes use of a procedure written I believe by Carl Love. It's going wrong when its ParamPlot3d procedure computes its L and U values as Float(undefined).

[edit] I have adjusted for that by changing the relevant min,max calls to min[defined] & max[defined].

3d_sachin_p1_acc.mw

@Carl Love I wonder if a rationale is that RootOf always turns its bound name into _Z.

RootOf(x - exp(x));

        RootOf(_Z - exp(_Z))

RootOf(_Z2 - exp(_Z2));

         RootOf(_Z - exp(_Z))

Hence querying indets(...,RootOf) provides any information and programmatic control that one would otherwise get if indets(...,name) were to return the _Z in use in some RootOf.

But for those other constructs, arbitrary names can be used. And so there's justification in saying that indets(...,name) should be able to query for them programmatically.

Where exactly is the piece of paper in your scenario?