@Preben Alsholm What I was trying to convey, in my Answer above, is that I get the following performance using the Zf(t,f) I had.

plot3d(Zf(t,f), f=1..10, t=0..3, grid=[29,49]);     # 9.0 sec

plot3d(Zf(t,f), t=0..3, f=1..10, grid=[49,29]);     # 3.6 minutes

Using the implementation for Q(f,t) which you've given, I see the following, similar, performance distinction (albeit a smaller absolute difference, but a somewhat comparable relative difference).

CodeTools:-Usage( plot3d(Q(f,t), f=1..10, t=0..3, grid=[29,49]) ):
memory used=11.90MiB, alloc change=0 bytes, cpu time=330.00ms, real time=331.00ms, gc time=30.19ms
CodeTools:-Usage( plot3d(Q(f,t), t=0..3, f=1..10, grid=[49,29]) ):
memory used=49.77MiB, alloc change=0 bytes, cpu time=4.82s, real time=4.82s, gc time=29.40ms

The key aspects are that it seems important to:
1) Have the dsolve parameter be the first/inner plotting variable, so that it changes value less often.
2) Don't set that parameter (using a procedure returned by dsolve) if its value is not different/changed.

Yes, I realize that the axis roles can be interchanged by using the parametric plotd3 calling sequence, while retaining the dsolve-parameter as the inner/first plotting variable for efficiency. But I was trying to keep it simple since the OP has trouble following instructions.
 

@adel-00 No, do it as,

   plot3d(Zf(t,f), f=-1..1, t=0..3, grid=[29,49]);

The procedure Zf sets the value for parameter f, and then calls zfun at the value of t.

The CodeTools:-Usage is just there to show the timing.

Download Summation.mw

@minhhieuh2003 Column span relates to how many columns a cell will span over. It doesn't specify a width.

You might be able to force some kind of increase to width, by padding with a long empty string. But it would be poor, in the sense that it would hardly offer the functionality to get a target pixel size.

I'll repeat an earlier suggestion: Consider using the documented commands in DocumentTools:-Layout instead of all these undocumented commands in Typesetting. It also gives the control you've requested for horizontal alignment as well as width. For example,

goi_maple_ac_EC.mw

@FrancescoLR What I'm expecting is a worksheet or text file, that contains all code, including procedures and data and the function calls that will reproduce your error messages when re-executed.

Use the green up-arrow in the Mapleprimes editor to upload.

@torabi As I wrote before, "Look at the entries in PDE5 and PDE[5], instead of suppressing everything with full colons. The equations you're passing to fsolve contain scalar expressions added to rtables."

You wrote the code which constructs PDE[i], and you haven't explained it. So, you ought to fix it.

@torabi Examine the arguments you are passing to fsolve. They contain some non-scalar nonsense.

@Carl Love He is also attempting to do Fortran code-generation, if I am understanding rightly. But we've been told very little about the data. It might be possible to get some improvement for at least the CG part, perhaps by using Grid on a few chunks.

Look at the entries in PDE5 and PDE[5], instead of suppressing everything with full colons. The equations you're passing to fsolve contain scalar expressions added to rtables.

@FrancescoLR Could you upload a full example, including the missing data (T_O_I, D_vol, N, p_gamma, and other...)? It's pretty difficult to deal with the procedures without it, and it's not reasonable to expect people to cook up their own.

It could be a smaller subset of your full data, but it'd help if it were large enough that successful parallelism could show at least some measurable timing improvement.

Even better would be a variant that did the code-generation and export sequentially, successfully.

@minhhieuh2003 Why don't you get the free upgrade from Maple 2016.0 to Maple 2016.2?

Please use 1D plaintext input in a Worksheet for code you'd like me to edit/adjust in future.

Download goi_maple_ac.mw

@minhhieuh2003 I have a hard time understanding you, since you don't state your question with full sentences. So I have to guess.

I am guessing that you are asking how to generate a representation, from a given expression, which displays in typeset 2D Output form.  So look at how foo1, foo2, foo3, and foo4 are displayed below.

I only used a forced mtext above, because you were asking about numbers and simple text. You can get representations for other expressions using Typesetting commands (as you did originally in your own code) or InertForm commands.

Download TS_fun.mw

You seem to be interested in laying out text and expressions in a particular format. Have you considered using the DocumentTools:-Tabulate command? Or, if that is not flexible enough for you, the commands from the DocumentTools:-Layout package? Unlike these Typesetting commands, those have Help pages. It's just an idea...

@shimaa sadk This one works for me.

Download ask_new.mw

Another way is to force method=_d01amc the NAG function for semi-infinite domain, while preventing evalhf mode (so as to avoid overflow) as well as specifying a higher working precision both for integrand evaluations as well as internal handling of same. This is fast.

Download ask_new_faster.mw

@Ramakrishnan Please pay closer attention. The line that you claim is missing a statement terminator is not input. It is just the echoed output of the previous input line.

And the messages about long output are not an indication of a problem with the code.

Here is the Original Poster's code, with that output line removed, and some colons to suppress the printing of long itermediate structures. It works fine, in Maple 2018.

restart; with(VectorCalculus): with(Student[LinearAlgebra]): with(plots):
v[i] := 145000; thetabn := (1/8)*Pi; thetavn := (1/6)*Pi; k := 10; omegac := .5;
lrange := 6*Pi;
v[b] := cos(2*thetabn)/cos(thetabn); v[g] := sin(2*thetabn)/cos(thetabn);
n := `<,>`(k*cos(thetabn), k*sin(thetabn), 0);
vr:=
[v[b]*t, v[g]*sin(omegac*t)/omegac, v[g]*cos(omegac*t)/omegac];

lambda := v[i]*cos(thetavn)/cos(thetabn);
shockplot := PlanePlot(n, caption = "", planeoptions = [colour = blue, transparency = .5], normaloptions = [shape = cylindrical_arrow, colour = red]):

t1 := textplot3d([k*cos(thetabn), k*sin(thetabn), 0, 'n'], align = above):
B := animate(spacecurve, [[t, 0, v[g]/omegac], t = lrange .. A], A = lrange .. 0, axes = normal, thickness = 3):
C := animate(plot3d, [[v[b]*t, v[g]*sin(omegac*t)/omegac, v[g]*cos(omegac*t)/omegac], t = 0 .. x], x = 0 .. lrange, axes = normal, colour = red, labels = [" ", zeta, xi], thickness = 2, paraminfo = false):
reflection := display([B, display(op([1, -1, 1], B), C)], insequence, scaling = constrained, axes = normal, tickmarks = [0, 0, 0]):
display(shockplot, t1, reflection, axes = none);

If you have similar variations on this question then please add them here in a Comment/Reply to the original Question, instead of making a new and separate Question thread.