[Octave-bug-tracker] [bug #51148] residue function potentially inaccurate

[Marco Caliari]

Follow-up Comment #18, bug #51148 (project octave):

Although in general it is not safe something like


rem = rem(find(rem~=0,1):end);


and should be replaced by (e.g.)


rem = rem(find(abs(rem)>eps/2,1):end);


now the problem is maybe in deconv (or even in filter). For instance


[div,rem]=deconv([1.92306958582241e+15,3.20449986572221e+24,1.34271290136344e+32,2.32739765751038e+38],[7.33727670161595e+27,1.05919311870816e+36,4.56169848520627e+42])


gives rem with two leading zeros, while


[div,rem]=deconv([1.92306958582241e+15,3.204499865722215e+24,1.34271290136344e+32,2.32739765751038e+38],[7.33727670161595e+27,1.05919311870816e+36,4.56169848520627e+42])


(I added a 5 as last digit of second element of first input) gives rem with
one leading zero.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51148>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/