octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #64078] quiver: int inputs result in erroneous


From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #64078] quiver: int inputs result in erroneous plots
Date: Thu, 20 Apr 2023 12:02:17 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?64078>

                 Summary: quiver: int inputs result in erroneous plots
                   Group: GNU Octave
               Submitter: nrjank
               Submitted: Thu 20 Apr 2023 12:02:15 PM EDT
                Category: Plotting
                Severity: 2 - Minor
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Any
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Thu 20 Apr 2023 12:02:15 PM EDT By: Nicholas Jankowski <nrjank>
noticed that while

quiver(1,0) 

produces a simple, horizontal single arrow quiver plot and 

quiver(true, false) 

produces an identical plot,

quiver(int32(1), int32(0))

does not. it produces an line going from 0,0 to 2,1, with no linesegment.

looking at the x and ydata, they stay as int32.  normally NaNs are used to
separate data points, and int32 replaces them with 0s, and there arrowhead
size calculations can't do fractions.

recommend the quiver/quiver3 functions internally convert data to double
before handing of to `__quiver__`.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64078>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]