The problem is that the Maple 2016 2D Input parser is unable to interpret that use statement until after the module is created and assigned to m.

If you are using 1D Maple notation then there is no parsing problem.

If you are using 2D Input then the module creation and assignment to m has to be executed before the 2D parser starts dealing with the execution group containing the problematic use statement.

As you've discovered one workaround is to put the use statement in a seperate execution group, after the execution group that assigns the module to m. I would prefer the alternative of not using 2D Input altogether for such programming.

It looks like your version MapleV R4 directly returns the exact radical value of sin(Pi/12).

In Maple 2017.3 an (equivalent) exact radical form can be obtained using the convert command.

sin(Pi/12);

                              /1    \
                           sin|-- Pi|
                              \12   /
r:=convert(%,radical);

                        1  (1/2) / (1/2)    \
                   r := - 2      \3      - 1/
                        4                    

ee:=1/4*sqrt(6)*(1-1/3*sqrt(3));

                       1  (1/2) /    1  (1/2)\
                 ee := - 6      |1 - - 3     |
                       4        \    3       /

radnormal(r-ee);

                               0

kernelopts(version);

   Maple 2017.3, X86 64 LINUX, Sep 27 2017, Build ID 1265877

I get the exact radical result directly from MapleV R5 but not from Maple 6.

@PhilipKroon You probably would not have had that problem with write-privilege if you had instead chosen a better location for the .mla file.

The advice in another Answer here would create the new .mla (Maple Library Archive) in the first folder in `libname`. By default that is the `lib` subfolder of your full maple installation.

It is poor advice to start fooling around in that folder, IMNSHO. It's probably even worse to fool around with i/o commands in Maple while running with admin privileges.

Alternatives are to create the new .mla file in a "toolbox" folder in the right place under your home folder. That too would not require you to alter libname in subsequent sessions in order to use it.

Yet another way is to build the new .mla file in some altogether different folder that is owned by you. In order to use it subsequently you could append `libname` in Maple sessions or (just once) append to `libname` in a personal maple initialzation file.

Please let me know if you'd like details on these suggestions (I'm away from a working copy of Maple today...)

The last opened Dcocument-Block seemed to have a corrupted Input item. If I delete that problematic Input, close off the outstanding open Group, Document-Block, two Sections, and Worksheet items in the XML file then I get the following:

1._Opgaver_1.mw

You could force the tickmarks on the second axis, eg,

plots:-display(plots:-logplot(x^2-3, x = 0 .. 100),
                  axis[2]=[tickmarks=[seq(10^i=typeset(10^convert(i,name)),i=-2..5)]],
                  legendstyle = [font = [bold, "TimesNewRoman", 30], location = right],
                  thickness = 4, font = [bold, "TimesNewRoman", 30])

restart;

ans:=sum((a+k*d)^r,k=1..infinity,formal)
     -sum((a+(k+n)*d)^r,k=1..infinity,formal);

             r             a + d     r             d n + a + d
     ans := d  Zeta(0, -r, -----) - d  Zeta(0, -r, -----------)
                             d                          d

f:=r->sum((a+k*d)^r,k=1..n):
simplify(f(7)-eval(ans,r=7));

                               0

I'm not sure what aspect of your original you found wanting.

restart;
with(Statistics):
randomize():
N := RandomVariable(Normal(300, 10)):
S := map(round,Sample(N, 100000)):
Histogram(S, frequencyscale = absolute,
          bincount = 75, binwidth = 1, tickmarks = [default, default]);

Pass it recursively as ':-num'=num .

The colon minus makes the lhs of that be a reference to the global name. The single right quotes protect against the case where you also might have assigned a value to the global name (ie. at the top level).

Use the plotsetup command to set the target device (ie. plot export driver).

And then use plots:-display or usual methods of "printing" the plot to output (which will direct it toward the set device).

Here are a few ways of shading the contours or its filled regions, on the 2D projection.

restart;

f := proc(x, y) options operator, arrow; sin(x)*cos(y) end proc:

Psurf:=plot3d(f, -Pi..Pi, -Pi..Pi, style=surface,
              colorscheme=["zgradient", ["Orange","Blue"]]):

Pcont2D_1:=plots:-contourplot(f, -Pi..Pi, -Pi..Pi,
                              coloring=["Orange","Blue"]):

Proj:=plottools:-transform((a,b)->[a,b,-1]):

plots:-display(
  Psurf,
  Proj(Pcont2D_1)
);

Pcont2D_2:=plots:-contourplot(f, -Pi..Pi, -Pi..Pi,
                              filledregions, coloring=["Orange","Blue"]):

plots:-display(
  Psurf,
  Proj(subsindets(Pcont2D_2,
                  specfunc(CURVES),
                  u->NULL))
);

plots:-display(
  Psurf,
  Proj(Pcont2D_1),
  Proj(subsindets(Pcont2D_2,
       specfunc(CURVES),
       u->NULL))
);

plots:-display(
  Psurf,
  Proj(subsindets(Pcont2D_2,
                 specfunc(CURVES),
                 u->CURVES(op(u),COLOUR(RGB,0.,0.,0.))))
);

surf_proj_contours.mw

You can resize the GUI Table inserted by the plots:-display command by manually dragging its borders.

Or you can change its Properties by right-clicking within it (in the white space, not the plot).

Note that if you re-execute the plots:-display command then the changed Table will be replaced with a new one (with default size).

If you want to be able to programmatically embed a GUI Table containing a plot, with a specific size, then you can use the DocumentTools:-Tabulate command in modern Maple (eg. version 2017). That command did not exist in your Maple 18, but the attached worksheet shows how you can programmatically get a similar effect for a plot. Note that the commands in use there are not documented in Maple 18, and are a bit fragile due to some lack or argument validation.

M18_DT_plot.mw

If your actual goal was to programmatically produce a 3D plot that displays automatically with a specific size (in Maple 18) then the following attachment illustrates another way to get that effect. This approach is not documented, and "your mileage may vary".

M18_sized_3dplot.mw

If your data is purely real numeric then you might try the LinearAlgebra:-CARE command.

For example,

Download CARE.mw

Download mult.mw

Download conv_arctrigh.mw

The fsolve command can have difficulty with the original because of the ill-behaviour numerically, alongside the fact that the expression is non-real-valued when K[1]<-1 or K[1]>1. This can be mitigated in several ways.

[edited] I am deliberately proceeding with ranges for K[1] that are wider than -1..1 on at least the positive side, simply because restricting the domain to within -1..1 is one way to mitigate the issue. It is of interest to see what happens when the user is not required to do such preliminary analysis to arrive at that approach.

restart;

ee:=-2*sqrt(-K[1]^2+1)*K[1]+4*K[1]^2-Pi-2*arctan(sqrt(-K[1]^2+1)/K[1]):

fsolve(ee,K[1]=0.5..2);
                          0.9832314847

fsolve(abs(ee),K[1]=0.5..20);
                          0.9832314847

# The next can return unevaluated (it varies with the range supplied).
fsolve(ee,K[1]=-2..2); 
fsolve(ee,K[1]=-2..20); 

These plots illustrate what's going on.

plot([Re,Im](ee),K[1]=-3..3,color=[red,blue],thickness=3,view=-20..20);
plot(abs(ee),K[1]=-3..3,color=[red,blue],thickness=3,view=0..20);

The difficulties with specifying the domain affect the Roots command as well.

Student:-Calculus1:-Roots(ee,K[1]=-1..1,numeric);
     [               -13                 -13              ]
     [-2.901814752 10   , -2.539955697 10   , 0.9832314847]

Student:-Calculus1:-Roots(abs(ee),K[1]=-2..2,numeric);
                         [0.9832314847]

# These next can return the empty list, it varies with range supplied
Student:-Calculus1:-Roots(ee,K[1]=-2..2,numeric);
                               []

Student:-Calculus1:-Roots(ee,K[1]=-2..20,numeric);
                               []

The solve command can be made to return a RootOf that can also produce the root your want (but is slower).

restart;
ee:=-2*sqrt(-K[1]^2+1)*K[1]+4*K[1]^2-Pi-2*arctan(sqrt(-K[1]^2+1)/K[1]):

evalf(allvalues([solve(ee,K[1])]));
Warning, solutions may have been lost

              [               -13]                
              [-2.147052793 10   ], [0.9832314847]