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

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

[Octave-bug-tracker] [bug #54610] imagesc doesn't implement ranges prope


From: Pantxo Diribarne
Subject: [Octave-bug-tracker] [bug #54610] imagesc doesn't implement ranges properly
Date: Sun, 2 Sep 2018 16:29:52 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

Update of bug #54610 (project octave):

                  Status:                    None => Confirmed              
        Operating System:               GNU/Linux => Any                    

    _______________________________________________________

Follow-up Comment #2:

I requested some code to be run in Matlab (see
http://octave.1599824.n4.nabble.com/Re-Request-for-test-in-Matlab-tp4689265.html)
and my conclusion is that the current Octave behavior is odd but not as much
as Matlab's


h = imagesc (1:10);
get (h, 'ydata')


This returns a scalar value 1 while Octave returns [1 1]. We should probably
do the same and document what a scalar value means for ydata and also that a
two element vector indicates the coordinates of the centers of corner pixels.


imagesc([-1,1], [-5, 5], 1:10)


Matlab renders the image as if the horizontal boundaries where at [-15 15]
while Octave renders between [-5.5 and 5.5]. We surely don't want to copy
Matlab here, but I'd be in favor of rendering between [-5 5] and documenting
this corner case where for 1 pixel high images, 'ydata' indicates the
coordinates of the boundaries, not the centers. Thoughts?

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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