On 04/06/2013 04:58 PM, Michael ODonnell wrote:
kmax=1;
kfactor=(kmax-1.0)/delta/(orderbc+1.0)/delbc^orderbc;
Unless matlab treats floats and ints differently than most other
languages, I'd say its a bug because zero over anything is always zero.
Shame on anybody who'd intentionally code
Write a review of the book and indicate that the code therein has bugs!
You're the eyeball + 1. Strengthen your power by reporting the bug in a
public forum! Help prevent others from falling into the same hole.
--Bruce
On 04/07/2013 10:35 AM, Bruce Labitt wrote:
On 04/06/2013 04:58 PM, Michael
Bruce Dawson j...@codemeta.com writes:
Write a review of the book and indicate that the code therein has bugs!
You're the eyeball + 1. Strengthen your power by reporting the bug in a
public forum! Help prevent others from falling into the same hole.
favorite.
Also, consider sending a
On Sun, 07 Apr 2013 11:22:23 -0400, Joshua Judson Rosen roz...@geekspace.com
wrote:
http://thankstextbooks.tumblr.com/
O
M
G
The dinosaur one.
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
On 04/07/2013 11:22 AM, Joshua Judson Rosen wrote:
Bruce Dawson j...@codemeta.com writes:
Write a review of the book and indicate that the code therein has bugs!
You're the eyeball + 1. Strengthen your power by reporting the bug in a
public forum! Help prevent others from falling into the
I'm trying to understand a chunk of 3D FDTD code that I downloaded from
the publisher of the book, Computational Electrodynamics. It is in
matlab, so I tried to run it in Octave. Something is not quite right,
so it doesn't execute. That doesn't matter to me right now. The piece
of code is:
On Sat, 06 Apr 2013 14:03:58 -0400, Bruce Labitt bruce.lab...@myfairpoint.net
wrote:
I'm trying to understand a chunk of 3D FDTD code that I downloaded from
the publisher of the book, Computational Electrodynamics.
I can't answer your question, but I may enjoy an elaboration of the
above.
Unless matlab treats floats and ints differently than most other
languages, I'd say its a bug because zero over anything is always zero.
But, I have no clue as to what context its running in, so it may be
deliberate.
--Bruce
On 04/06/2013 02:03 PM, Bruce Labitt wrote:
I'm trying to understand
On 04/06/2013 02:21 PM, David Rysdam wrote:
On Sat, 06 Apr 2013 14:03:58 -0400, Bruce Labitt
bruce.lab...@myfairpoint.net wrote:
I'm trying to understand a chunk of 3D FDTD code that I downloaded from
the publisher of the book, Computational Electrodynamics.
I can't answer your question, but
On Sat, 06 Apr 2013 14:34:27 -0400, Bruce Labitt bruce.lab...@myfairpoint.net
wrote:
On 04/06/2013 02:21 PM, David Rysdam wrote:
On Sat, 06 Apr 2013 14:03:58 -0400, Bruce Labitt
bruce.lab...@myfairpoint.net wrote:
I'm trying to understand a chunk of 3D FDTD code that I downloaded from
kmax=1;
kfactor=(kmax-1.0)/delta/(orderbc+1.0)/delbc^orderbc;
Unless matlab treats floats and ints differently than most other
languages, I'd say its a bug because zero over anything is always zero.
Shame on anybody who'd intentionally code something like
that without also providing a
If I knew how to debug in octave I'd tell you. Maybe tonight I'll brush up
on octave...
So far my python script runs but outputs 0. Kfactor seems to be evaluated
as 0. I bet it would work better if kfactor != 0...
On Apr 6, 2013 4:59 PM, Michael ODonnell michael.odonn...@comcast.net
wrote:
12 matches
Mail list logo