[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #63937] `residue` returns incorrect result in
|
From: |
Arun Giridhar |
|
Subject: |
[Octave-bug-tracker] [bug #63937] `residue` returns incorrect result in case of pole at zero |
|
Date: |
Fri, 17 Mar 2023 11:41:51 -0400 (EDT) |
Follow-up Comment #1, bug #63937 (project octave):
Your analysis looks accurate.
In your test, shouldn't the last input parameter to mpoles be 1 (true)?
If you have a patch for mpoles, I'm happy to review it and push it under your
name.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63937>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #63937] `residue` returns incorrect result in case of pole at zero, Michael Asam, 2023/03/17
- [Octave-bug-tracker] [bug #63937] `residue` returns incorrect result in case of pole at zero,
Arun Giridhar <=
- [Octave-bug-tracker] [bug #63937] `residue` returns incorrect result in case of pole at zero, Rik, 2023/03/20
- [Octave-bug-tracker] [bug #63937] residue() returns incorrect result in case of pole at zero, Rik, 2023/03/20
- [Octave-bug-tracker] [bug #63937] mpoles uses relative, not absolute, tolerance for zero poles, Rik, 2023/03/21
- [Octave-bug-tracker] [bug #63937] mpoles uses relative, not absolute, tolerance for zero poles, Michael Asam, 2023/03/21
- [Octave-bug-tracker] [bug #63937] mpoles uses relative, not absolute, tolerance for zero poles, Rik, 2023/03/21