|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #60384] `mpoles` incorrectly classifies distinct poles as unique ones |
Date: | Wed, 14 Apr 2021 09:09:14 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36 Edg/89.0.774.76 |
Update of bug #60384 (project octave): Status: Confirmed => Patch Submitted _______________________________________________________ Follow-up Comment #5: Turns out the error occurred because one of the poles was orders of magnitude larger than the others *and* it was negative. Should be fixed with the attached patch. That changes the order of poles as returned by `mpoles` to be sorted in descending order of *magnitude*. That seems to match what Matlab is doing. Before that change Octave returned the poles in descending order of *value*. (file #51264) _______________________________________________________ Additional Item Attachment: File name: bug60384_mpoles.patch Size:2 KB <https://file.savannah.gnu.org/file/bug60384_mpoles.patch?file_id=51264> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?60384> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |