Here's the procedure npar:

npar:= proc(p::procedure, $)
local L:= [op(1, eval(p))];
   nops(L) - `if`(` $` in L, 1, 0)
end proc;

This counts the parameters, not the arguments. What's the distinction? Parameters are an inherent property of a procedure; they're part of how it's written. Arguments are what's used when the procedure is called. The number of arguments to a given procedure may vary. If I declare

f:= x-> x^2;

then f has one parameter, x. If I call it using f(1,2), then it has two arguments for this call. This will not generate an error; by default it's allowed to pass extra unused arguments to a procedure. If you want to insist that f be called with exactly one argument, then you need to write it like this:

f:= proc(x,$) x^2 end proc:

Now that $ will appear as ` $` in op(1, eval(f)), which is why my procedure npar checks for it and subtracts 1 if it's found.

Inside procedure lich, you use f as if it were itself a procedure. That's fine, but then you need to pass a procedure to f, not an expression. So, you just need to change the call to lich to

lich(x-> sin(x^2), 0, Pi, 10);

We usually don't take kindly to screenshots. In the future, please upload a worksheet using the green uparrow on the toolbar of the MaplePrimes editor.

To get longitude and latitude lines on a sphere, use plot3d with coords= spherical:

plot3d(
   [1, phi, theta], theta= 0..2*Pi, phi= -Pi/2..Pi/2,
   coords= spherical, scaling= constrained
);

You can control the number of lines (to some extent) with the grid= [m, n] option.

Here's a worksheet that summarizes all that I've said so far, and also works out some of the finer details and nuisances of implementation.

Download Complex_norm_minimization.mw

If you want the number to display with the number of decimal places with which it was entered, but you don't want to explicitly specify that number of places, then use

FloatString:= (x::float)-> sprintf("%.*f", -op(2,x), x);
FloatString(0.0141);

To either convert command, append the clause assuming t1 > 0.

If your expression for drag force is df, then all that you need is

Cd:= V-> df *~ V;

If you have more trouble, please post a Maple worksheet (not a .docx).

Whether you use a colon or a semicolon to terminate a statement in a loop makes no difference. The only one that matters is the one after the final end do.

The loop depth for which output is displayed is controlled by the environment variable printlevel. By default, this is set to 1, so only the output of unnested loops is displayed. If you increase it:

printlevel:= 2;

then the output of every command in your doubly nested loops will be shown. I strongly advise that you only use this technique for debugging because, in general, the volume of output will be overwhelming.

The proper way to display the output of commands within loops or other control structures is to use print. That is, for any X that you want displayed, use print(X).

To return the entry of minimal modulus in a single line of code, use

rts[min[index](abs~(rts))];

It is also possible (in a very short single line of code) to sort the entries by modulus. This is especially useful for lists of eigenvalues.

This can also be done with simplify with side relations:

sol:= dsolve({diff(y(t),t$2) + w^2*y(t) = p/m*exp(-a*t), y(0) = 0, D(y)(0) = 0}):
simplify(sol, {a= n*w, p= m*w^2*u});

Suppose that p is a univariate polynomial, and that you want to plot the complex roots of p of modulus less than 1. Then do

plot(
   [Re,Im]~(select(x-> abs(x) < 1, [fsolve(p, complex)])),
   style= point, symbol= solidcircle, symbolsize= 18, scaling= constrained
);

If p is something other than a univariate polynomial, then more-sophisticated steps are required for the solving, but the selecting and plotting are the same.

I don't know why you're having trouble implementing Kitonum's Answer. Here's a different way using eval instead of subs. Create a list (not a vector) of the symbolic variables in the matrix:

X:= [x1, x2];

That part only needs to be done once. Then for each evaluation that you want using the values from vector x, do

eval(hf, X =~ seq(a, a= x));

Thank for providing the extra infomation that the error does not occur when you initialize N[i] to []. Now I am sure that you're dealing with a bug in Maple's 2D Input. The bug is that when certain expressions such as N[i] evaluate to NULL in 2D Input, it's as if they weren't there at all. So your statement

N[i]:= N[i], Data[i,j][4];

is passed to the parser as

N[i]:= , Data[i,j][4];

which, of course, has an unexpected comma.

The best thing that you can do is simply not use 2D input. Maple's 2D input is a completely unredeemable piece of garbage that's riddled with bugs like this.

But you can also change it to this, which is a much more efficient way to write it anyway:

for i to 2 do 
   N[i]:= seq(Data[i,j][4], j= 1..8) 
end do:

Now you don't need to initialize N[i].

The other Answers are great, but to Answer your Question directly:

You need to use = rather than := to set up equations. Like this

Eq1:=  x = y/p:
Eq1:=  z = x*a+y*(1-b):
Eq1:=  x = 100*z/(p*r+r);

There is never a situation where one would put a free symbolic variable (such as a variable which is to be "solved for") on both the left side and right sides of assignment operators (:=). Doing so causes "recursive assignment".

The following method is similar to Kitonum's, but it'll work in 1D input, so that you can easily edit the results. Like Kitonum's method, you must be prepared to follow Maple's own indentation and spacing style. Here's my procedure:

Indent:= (P::procedure)-> 
   map2(
      printf,
      "%s\n",
      map(
         s-> `if`(s[1]= " ", s[5..], s),
         StringTools:-Split(debugopts(procdump= P), `\n`)[..-2]
      )
   )[]
:

Now apply that to your procedure; for example, using Kitonum's example procedure,

Indent(PrimeTwins);

PrimeTwins := proc(N)
local n, a, b, L;
   n := 0;
   a := 2;
   do
     b := nextprime(a);
     if b-a <= 2 then
       n := 1+n;
       L[n] := [a, b];
       a := b
     else
       a := b
     end if;
     if n = N then
       break
     end if
   end do;
   convert(L,list)
end proc

Now copy-and-paste the output to a 1D Input (aka Maple Input) region, a Code Edit Region, or an external text editor.

All that being said, I strongly prefer to simply indent my code with the space bar as I am entering it.