@Al86 Okay, I've taken your function to be (x-2)^2*(3-x). Then one possible command is

ImageTools:-Embed(IterativeMaps:-Bifurcation([x], [r*(x-2)^2*(3-x)], [0.2], 0, 0.3));

Note that the parameter r must be used. As far as I can tell, it must be literally r, which seems very unMapleish to me. There are a vast number of options mentioned on the help page to use color to bring out various features of the above plot.

@mehdi jafari 

Are you using matrix (lowercase m)? That's deprecated, and there's no good reason to ever use it. Use Matrix instead.

What's wrong with simply sin(erf(t))? Do you expect there to be some other simple analytic form?

@JD423 

Regarding version dependency of the restart issue: This is just my guess, but I think that it has more to do with operating-system issues than with the version of Maple. I think that it has something to do with synchronization between the "kernel" and the GUI, which run as separate (and rather independent) processes in all versions of Maple. 

The need to put restart in its own execution group is documented on its help page. It's not a "bug" in the strict sense of that word. People who have a whole vocabulary for making fine distinctions among software behaviors might call it a "wart".

Regarding loading packages with with: You may have gotten the wrong impression that I disdain the use of packages. That's not at all true. What I disdain is the loading of packages with with. Instead of that, I just put the package name together with the procedure name at the point where the procedure is used. In other words, instead of Distance I'd use Student:-Precalculus:-Distance. If the prefixes are annoyingly long, I do something like

StP:= Student:-Precalculus;
...
... StP:-Distance(...) ...

In either case, when reading the code, it's clear that Distance comes from a module or package.

I think that it's worth pointing out that what you call b is formally called the skewness of x. This information may or may not be of help to you or to someone else who tries to answer your Question.

There seem to numerous bugs reported here related to the newer extended typesetting, which is now the default. Try doing this before running the above commands:

interface(typesetting= standard);

And what do you mean by ""sigma? That's not valid syntax. Usually I can figure out a user's intention despite their invalid syntax, but that one has me completely baffled.

This is essentially a duplicate of your previous Question. You've only changed the equations slightly. You seem to have completely ignored all the advice that both Tom Leslie and I gave you.

@cencen_cj wrote:

• I have no clue what went wrong. Please kindly give me a hint.

But Tom did give you a substantial hint! I am certain that your usage of square brackets in the way that he pointed out is wrong. I am not certain that it is the cause of your error, but, nonetheless, it is wrong and must be corrected before you can proceed.

It's offensive to check all the boxes Maple, MapleNet, MapleSim, etc. Your Question is about Maple alone. Better yet, you should select your Maple version.

Please upload (at the very least) the code, the call that produces the error, and the exact error message. You can either upload a worksheet as an attached file, or just upload plaintext. It doesn't matter if it's in some other language; we can still figure it out.

@tarik_mohamadi 

Is the case R=0 meaningful to you? It certainly wouldn't be meaningful to me. This case is trivial and degenerate, and it needs special handling if you want to include it. Otherwise, just remove this case from the loop.

@tarik_mohamadi I need to see your complete code to provide further help. At the least, I need to see the value of eqns.

Generally, if it's possible to do something with Threads, then doing so is significantly faster and uses significantly less memory than using Grid. So, if some easy modification can make the code threadsafe, it may be worth pursuing that.

It's possible for code to be threadsafe even though it uses procedures not listed at ?index,threadsafe. That page lists procedures that are guaranteed to be threadsafe. The issue is whether the parallelized part of the code can make contradictory assignments to variables at a higher lexical level (including enviroment variables such as Digits). A common case is code running under evalhf. I believe that such is always threadsafe (and, if not, it certainly is threadsafe in the vast majority of cases). So, if that evalhf code uses sin, for example, it's still threadsafe even though sin, in general, is not.

@Joe Riel According to the relevant help page, combinat:-rankperm and combinat:-unrankperm were introduced in Maple 16; so, too late for this OP. And, I'm content with the code that I've written, but if you see the possibility of improvement, please let me know. I'm aware that with Maple 2019 syntax, the line

C[i..]:= C[i..] + rtable(i..n, j-> `if`(C[j] < c, 0, 1))

can be improved to 

C[i..]+= rtable(i..n, j-> `if`(C[j] < c, 0, 1))

@testht06 

My composition operator is the procedure &x that I already gave above:

[3,5,7,0,2,1,4,6] &x [2,4,0,5,3,1,6,7];
      [5, 1, 7, 2, 0, 4, 3, 6]

Maple's sophisticated list indexing makes the code of this procedure so short that you may have missed it above:

`&x`:= (P,Q)-> Q[P+~1]: