[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #41674] [octave forge] (image) temporary array
From: |
Nicholas Jankowski |
Subject: |
[Octave-bug-tracker] [bug #41674] [octave forge] (image) temporary arrays in imresize are doubles |
Date: |
Fri, 27 Aug 2021 15:51:20 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36 |
Follow-up Comment #19, bug #41674 (project octave):
stepping through imresize to see if the issue has been resolved, i'm not
certain it has. currently, it pushes most of the calculation over to imremap.
just testing a simple 2x linear scaling on the first 7x10 'test' image with a
uint8 input, line 89 in impremap (on default branch) forces im to be recast as
a double before running the interp, so the output is double before being
recast in the last step back to uint8.
So this appears to be better than before, where meshgrid first made two full n
x m arrays before doing the same process described above. So, this reduces
the 'extra' memory overhead by a factor of 3.
Assuming there's no other way to get around the temporary output being a
double before being recast to match the input class, this can probably be
called complete and this old bug report closed.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?41674>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/