Using MAPLE V, Release 11, a creep curve has been formulated, which represents the mechanical behavior of metals, polymers, and ceramics, for instance.

Inspired by the post

Re: the physics package I decided to have a closer look at the function

`FeynmanDiagrams`

. As the Lagrangian I thought I might as well take the QED Lagrangian for a massless spinor field

`Q[i](X)`

coupled to an external electromagnetic field

`A[mu](X)`

:

restart:
with(Physics):
Setup(advanced):
L_QED :=
+Dagger(Q[i](X)) * Dgamma[4] * Dgamma[mu][i,j] * I * diff(Q[j](X),X[mu])
+Dagger(Q[i](X)) * Dgamma[4] * Dgamma[mu][i,j] * e * A[mu](X) * (Q[j](X));

Can someone explain why is 0 handled differently by evalf[10] than nonzero numbers in the following examples?
Digits:=50:
epsilon:=Float(1.0,-30);
-30
1.0 10
for x in [0,0.0,1,sqrt(2),Pi] do
x,evalb(evalf[10](x)=evalf[10](x+epsilon));
od;
0, false
0., false
1, true
(1/2)
2 , true
Pi, true

In trying to answer the second question in

How to determine the order of an ODE? I have unsuccessfully tried to use

`select`

to filter out the appropiate parts of the differential equations.
In these attempts I have hit upon a behaviour of

`select`

I do not understand: In my opinion each of the following two code lines (or at the very least the second line) should return the differential expression itself:

select(has,diff(y(t),t),y);
select(has,diff(y(t),t),y(t));

But they do not; each line returns

`diff(y(t))`

, where the variable

`t`

with respect to which is being differentiated is missing. Why? Is it just me having fundamentally misunderstood something?

So what is the best way to put a "link" from one place in a maple document to another. So that someone can jump quickly when clicked?
Thanks!

I recently changed the system from 10.4.10 to 10.4.11 and not too long afterwards noticed the following problem: when I restart my machine the maple 9.5 does not load properly. It takes about three restarts to get maple to open.
Any suggestions?

The following is the code for the 2nd Fick's law with initial/boundary conditions. Unfortunately this code does not show me the result required for next process. It would be useful for us to proceed this work. Thanks in advance. ( Currently we are using Maple 10.)
> restart;
> DiffusionCoefficientST := 0.5e-2;
> ExperienceConstant := 5;
> Temperature := 273+25;
> PDE := diff(C(x, t), t) =
> DiffusionCoefficientST*(exp(1))(-ExperienceConstant(1/Temperature-1/296))*(diff(C(x,
> t), x, x));
> IBCondition := {C(x, 0) = 2, C(0, t) = 0, ((D[1])(C))(5, t) = 0};
> pds := pdsolve(

Maple 11 has been working flawlessly for me under Mac OS X Leopard, with both updated. However, while the screen output appears to be fine, the Times New Roman (and other?) fonts seem to disappear and are replaced by a sans serif font (like Helvetica or Geneva). This occurs whether I send the output to a postscript laser printer (HP 2200) or to a non-postscript inkjet (HP 5550). I vaguely remember having a similar problem years ago, i.e., prior to Mac OS X. Has anyone else encountered this problem? Has anyone who encountered this identified a solution? So far, I'm stuck exporting my resu

I hope someone can shed so light on the following:
I upgraded to SuSE10.3 -32bit recently and everything seemed to go well. Maple 11.01 was installed and has worked fine until now. Today was the first time I tried to print a file and 'Lo and Behold. There is no print function at all! Whenever 'Print' or 'Page Setup' is clicked there is a brief moment of 'wait' cursor and then nothing happens. No dialog box, no warnings just silence.
I did a search for similar issues on Google but came up empty. I've checked the CUPS config file for the Linux fix regarding Sockets, that made no difference, I checked the installation of CUPS and it seems fine, indeed, every other application prints fine. By the end of the day I resorted to reinstalling Maple and that didn't make any difference either. I'm at a loss. Anyone using SuSE and Maple 11.01 care to comment?

For a long thread it is often a bit difficult to locate the new posts referred to in the Replies column of recent posts, especially if the thread has laid dormant for some period of time over which its detailed history has been forgotten.
Therefore, could new posts be highlighted in some way to make them stand out?

This is a follow-up on one of the unresolved issues raised in a previous

post of mine.
In view of the fact that 1 + I is indeed of type complexcons, can anybody please explain why the following is reasonable:

restart:
assume(x::complexcons):
evalc(x + conjugate(x)),
evalc(x - conjugate(x));
restart:
x := 1 + I:
evalc(x + conjugate(x)),
evalc(x - conjugate(x));
2 x~, 0
2, 2 I

Would someone try the Integration Tutor with csc^3(x). On SuSE Linux 10.3 with maple 11.01 it just loops through the Parts rule. Endlessly it seems. Worksheet works fine though.
Tim

I am writing to discuss an issue which arises due to a Java bug
combined with updated X11 libraries.
I have been trying to get Maple 11 to run in a new version of Fedora Linux
(F8).
After a lot of searching I have found a solution. Note that unless the
Maple developers issue a new corrected CD image changed to work with the
new libX11 library then this fix will be required on all linux machines
with updated libX11. In my case this came to light after upgrading my
computer from Fedora 7 where the application was installed (and kept in an
untouched partition during the install of F8)

Is there anybody, MapleSoft staff included, of course, that could give some help or advice on the issues raised in

thread1 (which died unresolved) and

thread2 (which I somewhat expect to share destiny with thread1)?

The most trivial task in option pricing is to compute values through the Black-Scholes formula: type in the formula, feed Maple with data, done. The same in computational environments like C programs or Excel (assuming a good implementation of the cumulative normal function). Really? And the limiting cases? Or coming close to them? How about small volatility (say below 10% like in FX trading?) or short expiry times (say some weeks)? No problem to back-out volatility from prices to fit models?
First I give an example that using the common formula even Maple quickly runs into numerical errors. That can be avoided by decomposing calls and puts into their so-called intrinsic value (the discounted pay-off) and their premium (that's wht has to be payed beyond that, the actual 'speculation').