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: > > > > 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 comment about such a seemingly > counterintuitive approach. >-/ Let's hope it's simply a bug... > > Out of morbid curiosity, how does Octave report the value of > kfactor after > > kmax=1 > kfactor=(kmax-1.0) > > ?? > > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ >
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
