Re: [OctDev] [IMAGE package] changing behaviour of isbw

2011-11-28 Thread Søren Hauberg
tir, 29 11 2011 kl. 04:09 +, skrev Carnë Draug: > Hi > > I was looking through isbw which is supposed to return 1 or 0 wether a > matrix is a black and white image. > > The way it's working now, it returns 1 if all values in a matrix are 0 > or 1. This is not completely correct since a graysc

[OctDev] [IMAGE package] changing behaviour of isbw

2011-11-28 Thread Carnë Draug
Hi I was looking through isbw which is supposed to return 1 or 0 wether a matrix is a black and white image. The way it's working now, it returns 1 if all values in a matrix are 0 or 1. This is not completely correct since a grayscale image can be of values 0 and 1. In my view, it should check if

Re: [OctDev] Deleting/deprecating apply.m

2011-11-28 Thread Jordi Gutiérrez Hermoso
On 28 November 2011 13:45, Paul Dreik wrote: > 2011-11-28 19:39, Jordi Gutiérrez Hermoso skrev: >> On 28 November 2011 12:48, Carnë Draug wrote: >>> On 19 November 2011 21:41, Jordi Gutiérrez Hermoso >>> wrote: The apply.m function in the miscellaneous package seems to be a poor reimp

[OctDev] dicominfo and sequences

2011-11-28 Thread Kris Thielemans
Hi Andy I had a look at why dicominfo doesn't store/dump sequence elements (VR=SQ). It turns out that this is very easy to fix. In element2value, you have near the beginning // skip "Group Length" tags. note: these are deprecated in DICOM 2008 if(tag.GetElement() == (uint16_t)0 ||

Re: [OctDev] Deleting/deprecating apply.m

2011-11-28 Thread Paul Dreik
2011-11-28 19:39, Jordi Gutiérrez Hermoso skrev: > On 28 November 2011 12:48, Carnë Draug wrote: >> On 19 November 2011 21:41, Jordi Gutiérrez Hermoso >> wrote: >>> The apply.m function in the miscellaneous package seems to be a poor >>> reimplementation of arrayfun and cellfun. Any objections t

Re: [OctDev] Deleting/deprecating apply.m

2011-11-28 Thread Jordi Gutiérrez Hermoso
On 28 November 2011 12:48, Carnë Draug wrote: > On 19 November 2011 21:41, Jordi Gutiérrez Hermoso wrote: >> The apply.m function in the miscellaneous package seems to be a poor >> reimplementation of arrayfun and cellfun. Any objections to deleting >> this function? Or a suggestion to properly d

Re: [OctDev] "librsb"+"sparsersb" packages proposal for octave-forge -> fixes & complex

2011-11-28 Thread Michele Martone
On 2021@09:16, Michele Martone wrote: > ... Hello list, Here is a summary of updates to sparsersb/librsb. With testing & help from Carlo last week, I made some fixes to the library in order to handle more graciously the case when system memory fails from being detected. This and other change

Re: [OctDev] Deleting/deprecating apply.m

2011-11-28 Thread Carnë Draug
On 19 November 2011 21:41, Jordi Gutiérrez Hermoso wrote: > The apply.m function in the miscellaneous package seems to be a poor > reimplementation of arrayfun and cellfun. Any objections to deleting > this function? Or a suggestion to properly deprecating it? > > - Jordi G. H. Hi Jordi seems th

Re: [OctDev] experimental dicom support: changing code for multiple elements and byteorder etc

2011-11-28 Thread Kris Thielemans
Hi Andy > > > My personal opinion is a bit different. I'm rather safe than sorry. I think > > we should first aim to get this working in all cases before trying to > > optimise. > > > > In any case, the current code is already faulty for those elements for which > > VM>1, i.e. which have multiple

Re: [OctDev] Fixes to line_min function in Optim package

2011-11-28 Thread Olaf Till
On Sun, Nov 27, 2011 at 02:54:24PM -0500, Nir Krakauer wrote: > Dear Olaf, > > Thank you for your suggestions. > > > - Why is 'h' randomized? Even if there should be a good reason, I think this > > cannot be done inside 'line_min'. Rather, make 'h' configurable so that > > users > > can randomiz