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: Brent Baccala
Subject: [Octave-bug-tracker] [bug #54610] imagesc doesn't implement ranges properly
Date: Fri, 31 Aug 2018 17:50:11 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/68.0.3440.75 Chrome/68.0.3440.75 Safari/537.36

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

                 Summary: imagesc doesn't implement ranges properly
                 Project: GNU Octave
            Submitted by: baccala
            Submitted on: Fri 31 Aug 2018 09:50:09 PM UTC
                Category: Plotting with OpenGL
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.4.1
        Operating System: GNU/Linux

    _______________________________________________________

Details:

The `imagesc` documentation states:

The axis values corresponding to the matrix elements are specified in x and y,
either as pairs giving the minimum and maximum values for the respective axes,
or as values for each row and column of the matrix img.

`imagesc` doesn't seem to be properly respecting the limits when they're given
as pairs.  For example,


figure()
xlim([-1,1])
ylim([-1,1])
imagesc([-1,1], [-0.5, 0.5], 1:10)


What I expect is a colored band in the middle of the figure, since I specified
the y range as a pair giving -0.5 and 0.5 as the minimum and maximum values,
respectively, yet the figure's y limits go from -1 to 1.

What I get is a colored band that fills the entire figure.  I've tested this
with Octave 4.4.1 on Ubuntu 18.04.

I've looked at the code, and I think the problem is at lines 3665-3667 in
gl-render.cc (4.4.1 release).

My first question, though, is am I understanding the documentation and the
intent correctly?  Do we agree that this is a bug?






    _______________________________________________________

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]