mmcdara

6149 Reputation

17 Badges

9 years, 72 days

MaplePrimes Activity


These are replies submitted by mmcdara

@acer 

Sure, this seems like a good idea for... Maple 2021 maybe?

See you soon

@acer 

Blimey!
You had already told me that for matrixplot a few weeks ago!
Sorry for the inconvenience.

@tomleslie 

You're right.
If I do remember correctly the 2015 Maple version (and even maybe another one, was it 2016 ?)  suffered some problems when running on MacOS X.
I had delayed my purchase of Maple 2015 during several months for this reason and since then I've been very careful to renewing my 2015 (some have even talked recently about compatibility issues between Maple 2019 and MacOS Catalina... )

@Axel Vogt 

Thanks Axel, 

it also appears to work this way

numelems([solve( simplify(LegendreP(18,x), 'LegendreP') )])
                               18

 

Thanks, 

Here is my file with interface(version) included
 

restart:

interface(version)

`Standard Worksheet Interface, Maple 2015.2, Mac OS X, December 21 2015 Build ID 1097895`

(1)

Z := n -> op~(2, { allvalues(solve(LegendreP(n,x))) } );

proc (n) options operator, arrow; `~`[op](2, {allvalues(solve(LegendreP(n, x)))}) end proc

(2)

Digits:=10:
Z(17):
numelems(%);

17

(3)

Z(18):
numelems(%);

16

(4)

Digits:=15:
Z(18):
numelems(%);

16

(5)

Digits:=20:
Z(18):
numelems(%);

15

(6)

 


 

Download LegendreP_zeros.mw

@nm 

Thanks nm, maybe an old bug?

Even forcing maxsols=n doesn't help.

@acer 

Thanks for having corrected the product field.

@vv 

Why did I pick up at noon to 2:00 p.m.?

Thanks, I vote up;

ps: the output of  (2*A * B^(-1) - C)^* is not very pretty (1/B instead of B-1)

 

@Carl Love @nm @acer @tomleslie

Thanks to all of you.
Decidedly I have to replace my personal license.

 

@Carl Love 

Thanks for your reply (I wasn't aware of the appliable type checking).

PS: I guess you have a little typo in the last line of the second code snippet; probably

div5(f(5));

instead of

div5(f[5]);

@Carl Love 

Hi, 
what do you think about a syntax like 

f := i -> x -> sin(i*x);

to define a two-stage" function?
It seems to me this is a better syntax than f[i](x), for instance,  for which i looks more like an index than a parameter.

 

Another way based on MathML coding:
 

ks := [123, 456, 789, 101112];
Ns := [seq](1900..1960, 20);

code := (k, N) -> parse(cat("`#mrow(mfrac(mo(", k, "),mo(", N, ")))`")):

plot(sqrt(x) - 0.5,  x= 0..10, axis[1]=[tickmarks=[seq(2*k=code(ks[k], Ns[k]), k=1..4)]])

Download With_MathML.mw

@vv @tomleslie

Until now I used to save the solution procedure in a ".m" file for later use the solution procedure and to save in the same file the bold quantity below  (if any)

sol := solve(sys, numeric, parameters=params)

This until I realized that sol(parameters) enabled recovering the list of the parameters.
Thus I thought that saving params was useless and decided to save sol alone.

What you both say, if I understand correctly, is that I have to save params also (it's not for the size it costs...)?

 

i don't know what you want to do, but if you just want do obtain the output LaTeX code fir your Matrix do 

latex(B);

and copy-paste the result in your LaTeX document within the \begin{S} ... \end{S} structure S you want.
Anyway, no automatic Maple code generation of the LaTeX code will be able to correctly handle all cases (matrix on two pages, centering, scaling in case there are a lot of columns...).
In all cases you will have to finish the work by hand (unless you use LaTex as Word and don't care about the beauty of the document).
 

@gkokovidis 

Thanks for the reply, 

Regards

First 66 67 68 69 70 71 72 Last Page 68 of 125