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

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

[Octave-patch-tracker] [patch #9722] [octave forge] (image) new objects


From: Avinoam Kalma
Subject: [Octave-patch-tracker] [patch #9722] [octave forge] (image) new objects imref2d and imref3d
Date: Thu, 3 Jan 2019 16:38:48 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Follow-up Comment #6, patch #9722 (project octave):

Two comments:


Matlab:

>> R = imref2d([100 200], 0.1, 0.4)

R = 

  imref2d with properties:

           XWorldLimits: [0.0500 20.0500]
           YWorldLimits: [0.2000 40.2000]
              ImageSize: [100 200]
    PixelExtentInWorldX: 0.1000
    PixelExtentInWorldY: 0.4000
    ImageExtentInWorldX: 20
    ImageExtentInWorldY: 40
       XIntrinsicLimits: [0.5000 200.5000]
       YIntrinsicLimits: [0.5000 100.5000]

Octave:

>> R = imref2d([100 200], 0.1, 0.4)
R =
imref2d with properties:

         XWorldLimits: [0.05 10.05]
         YWorldLimits: [0.2 80.2]
            ImageSize: [100 200]
  PixelExtentInWorldX: 0.1
  PixelExtentInWorldY: 0.4
  ImageExtentInWorldX: 10
  ImageExtentInWorldY: 80
     XIntrinsicLimits: [0.5 200.5]
     YIntrinsicLimits: [0.5 100.5]


it seems that m and n have swapped places in lines 111-112.


>> R = imref2d([100 200], [1.5 0.5], [2.5 0.5])


Matlab throws error because xWorldLimits(2) should be greater than
xWorldLimits(1) (and of course, the same for yWorldLimits)


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?9722>

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




reply via email to

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