octave-dev — GNU Octave developers' list

Re: [OctDev] minmax

[Carnë D. <car...@gm...>]

Please avoid top posting and reply at the bottom of the e-mail

On 8 November 2012 12:57, Salva Ardid <js...@gm...> wrote:
> El Dijous, 8 de novembre de 2012, a les 11:46:19, Carnë Draug va escriure:
>
>> On 21 October 2012 15:15,  <gio...@un...> wrote:
>> > Hi!
>> > there is a difference between matlab's minmax, and octave nnet pkg's
>> > min_max.
>> >
>> > In matlab:
>> > minmax([1 2 3 4 3 4 5 6 4 3 4 5])
>> > gives
>> > ans =
>> >
>> >      1     6
>> >
>> > In octave with nnet:
>> > min_max([1 2 3 4 3 4 5 6 4 3 4 5])
>> > gives
>> > error: Argument must be a matrix.
>> >
>> > Octave does not like the input image to be a single line.
>>
>> On 8 November 2012 01:52, Salva Ardid <js...@gm...> wrote:
>> > I recently ran into these troubles too.
>>
>> Hi Giorgio and Salva
>>
>> please give the following new version function a try
>> https://sourceforge.net/p/octave/code/11403/tree/trunk/octave-forge/main/nne
>> t/inst/minmax.m
>>
> Hi Carnë,
>
> The link seems to be broken
>
> Salva

Seems to be one more problem of the new SF code viewer. It also
appears to be 2 revisions behind. Use SVN to get it

svn cat -r 11403
https://svn.code.sf.net/p/octave/code/trunk/octave-forge/main/nnet/inst/minmax.m

or wait some time until sourceforge updates it.

Carnë

Re: [OctDev] minmax

[Salva A. <js...@gm...>]

Hi Carnë,

The link seems to be broken

Salva

El Dijous, 8 de novembre de 2012, a les 11:46:19, Carnë Draug va escriure:

> On 21 October 2012 15:15,  <gio...@un...> wrote:
> > Hi!
> > there is a difference between matlab's minmax, and octave nnet pkg's
> > min_max.
> > 
> > In matlab:
> > minmax([1 2 3 4 3 4 5 6 4 3 4 5])
> > gives
> > ans =
> > 
> >      1     6
> > 
> > In octave with nnet:
> > min_max([1 2 3 4 3 4 5 6 4 3 4 5])
> > gives
> > error: Argument must be a matrix.
> > 
> > Octave does not like the input image to be a single line.
> 
> On 8 November 2012 01:52, Salva Ardid <js...@gm...> wrote:
> > I recently ran into these troubles too.
> 
> Hi Giorgio and Salva
> 
> please give the following new version function a try
> https://sourceforge.net/p/octave/code/11403/tree/trunk/octave-forge/main/nne
> t/inst/minmax.m
> 
> Carnë Draug

Re: [OctDev] minmax

[Carnë D. <car...@gm...>]

On 21 October 2012 15:15,  <gio...@un...> wrote:
> Hi!
> there is a difference between matlab's minmax, and octave nnet pkg's min_max.
>
> In matlab:
> minmax([1 2 3 4 3 4 5 6 4 3 4 5])
> gives
> ans =
>      1     6
>
> In octave with nnet:
> min_max([1 2 3 4 3 4 5 6 4 3 4 5])
> gives
> error: Argument must be a matrix.
>
> Octave does not like the input image to be a single line.

On 8 November 2012 01:52, Salva Ardid <js...@gm...> wrote:
> I recently ran into these troubles too.

Hi Giorgio and Salva

please give the following new version function a try
https://sourceforge.net/p/octave/code/11403/tree/trunk/octave-forge/main/nnet/inst/minmax.m

Carnë Draug

Re: [OctDev] minmax

[Salva A. <js...@gm...>]

Sure!

>> x=minmax ({[0 1; -1 -2; 34 56] [2 3; 8 0; 21 23]; [1 -2; 9 7] [12 5; 13 
11]})

x = 

    [3x2 double]
    [2x2 double]

>> x{1}

ans =

     0     3
    -2     8
    21    56

>> x{2}

ans =

    -2    12
     7    13

Salva

El Dijous, 8 de novembre de 2012, a les 02:39:06, Carnë Draug va escriure:

> On 8 November 2012 02:23, Salva Ardid <js...@gm...> wrote:
> >>> minmax ({[0 1; -1 -2; 34 56] [2 3; 8 0; 21 23]; [1 -2; 9 7] [12 5; 13
> >>> 11]})
> > 
> > ans =
> > 
> >     [3x2 double]
> >     [2x2 double]
> 
> Could you tell me what this values are exactly? It's not clear to me
> from their documentation what they are computing.
> 
> Carnë

Re: [OctDev] minmax

[Carnë D. <car...@gm...>]

On 8 November 2012 02:23, Salva Ardid <js...@gm...> wrote:
>>> minmax ({[0 1; -1 -2; 34 56] [2 3; 8 0; 21 23]; [1 -2; 9 7] [12 5; 13 11]})
>
> ans =
>
>     [3x2 double]
>     [2x2 double]

Could you tell me what this values are exactly? It's not clear to me
from their documentation what they are computing.

Carnë

Re: [OctDev] minmax

[Salva A. <js...@gm...>]

Yes, it seems they have a bug in their own code or that the example is just 
wrong:

>> P = {[0 1; -1 -2] [2 3 -2; 8 0 2]; [1 -2] [9 7 3]};
>> pr = minmax(P)
Error using minmax (line 27)
Data{1,2} and Data{1,1} have different numbers of columns.
 
>> minmax ({[0 1; -1 -2] [2 3; 8 0]; [1 -2; 9 7] [12 5; 13 11]})

ans = 

    [2x2 double]
    [2x2 double]

>> minmax ({[0 1; -1 -2] [2 3; 8 0; 85 75]; [1 -2; 9 7] [12 5; 13 11]})
Error using minmax (line 27)
Data{1,2} and Data{1,1} have different numbers of rows.
 
>> minmax ({[0 1; -1 -2; 34 56] [2 3; 8 0]; [1 -2; 9 7; 21 23] [12 5; 13 11]})
Error using minmax (line 27)
Data{1,2} and Data{1,1} have different numbers of rows.
 
>> minmax ({[0 1; -1 -2; 34 56] [2 3; 8 0; 21 23]; [1 -2; 9 7] [12 5; 13 11]})

ans = 

    [3x2 double]
    [2x2 double]

Salva

El Dijous, 8 de novembre de 2012, a les 02:19:06, Carnë Draug va escriure:

> On 8 November 2012 01:52, Salva Ardid <js...@gm...> wrote:
> >>> minmax ({[0 1; -1 -2] [2 3 -2; 8 0 2]; [1 -2] [9 7 3]})
> >
> >Error using minmax (line 27)
> >Data{1,2} and Data{1,1} have different numbers of columns.
> 
> This is weird. This an example taken from Matlab's own documentation
> 
> http://www.mathworks.co.uk/help/nnet/ref/minmax.html
> 
> It should have not failed. Could you tell me what does the following
> returns then?
> 
> minmax ({[0 1; -1 -2] [2 3; 8 0]; [1 -2; 9 7] [12 5; 13 11]})
> minmax ({[0 1; -1 -2] [2 3; 8 0; 85 75]; [1 -2; 9 7] [12 5; 13 11]})
> minmax ({[0 1; -1 -2; 34 56] [2 3; 8 0]; [1 -2; 9 7; 21 23] [12 5; 13 11]})
> minmax ({[0 1; -1 -2; 34 56] [2 3; 8 0; 21 23]; [1 -2; 9 7] [12 5; 13 11]})
> 
> Carnë

Re: [OctDev] minmax

[Carnë D. <car...@gm...>]

On 8 November 2012 01:52, Salva Ardid <js...@gm...> wrote:
>>> minmax ({[0 1; -1 -2] [2 3 -2; 8 0 2]; [1 -2] [9 7 3]})
>Error using minmax (line 27)
>Data{1,2} and Data{1,1} have different numbers of columns.

This is weird. This an example taken from Matlab's own documentation

http://www.mathworks.co.uk/help/nnet/ref/minmax.html

It should have not failed. Could you tell me what does the following
returns then?

minmax ({[0 1; -1 -2] [2 3; 8 0]; [1 -2; 9 7] [12 5; 13 11]})
minmax ({[0 1; -1 -2] [2 3; 8 0; 85 75]; [1 -2; 9 7] [12 5; 13 11]})
minmax ({[0 1; -1 -2; 34 56] [2 3; 8 0]; [1 -2; 9 7; 21 23] [12 5; 13 11]})
minmax ({[0 1; -1 -2; 34 56] [2 3; 8 0; 21 23]; [1 -2; 9 7] [12 5; 13 11]})

Carnë

Re: [OctDev] minmax

[Salva A. <js...@gm...>]

Hi,

I recently ran into these troubles too.

It's nice if this can get fixed. And unless some particular reason I may not 
know, I would suggest to use the same name as in matlab (minmax instead of, or 
in addition to min_max) so code is consistent.

I also checked what you asked in matlab r2012b:

>> minmax (1)

ans =

     1     1

>> minmax ([i 2; 3 4])
Error using minmax (line 27)
Data is complex.
 
>> minmax (rand (2,2,2))
Error using minmax (line 27)
Data is not two-dimensional.
 
>> minmax ({[0 1; -1 -2] [2 3 -2; 8 0 2]; [1 -2] [9 7 3]})
Error using minmax (line 27)
Data{1,2} and Data{1,1} have different numbers of columns.
 
>> minmax ({[0 1; -1 -2] [2 3; 8 0]; [1 -2] [9 7 3]})
Error using minmax (line 27)
Data{2,2} and Data{1,1} have different numbers of columns.
 
>> minmax ({[0 1; -1 -2] [2 3 -2; 8 0 2]; [1 -2] [9 7 3; 8 0 2]})
Error using minmax (line 27)
Data{1,2} and Data{1,1} have different numbers of columns.

Thanks,
Salva

El Dijous, 8 de novembre de 2012, a les 01:08:09, Carnë Draug va escriure:

> minmax (1)
> minmax ([i 2; 3 4])
> minmax (rand (2,2,2))
> minmax ({[0 1; -1 -2] [2 3 -2; 8 0 2]; [1 -2] [9 7 3]})
> minmax ({[0 1; -1 -2] [2 3; 8 0]; [1 -2] [9 7 3]})
> minmax ({[0 1; -1 -2] [2 3 -2; 8 0 2]; [1 -2] [9 7 3; 8 0 2]})

Re: [OctDev] minmax

[Carnë D. <car...@gm...>]

On 21 October 2012 15:15,  <gio...@un...> wrote:
> Hi!
> there is a difference between matlab's minmax, and octave nnet pkg's min_max.
>
> In matlab:
> minmax([1 2 3 4 3 4 5 6 4 3 4 5])
> gives
> ans =
>      1     6
>
> In octave with nnet:
> min_max([1 2 3 4 3 4 5 6 4 3 4 5])
> gives
> error: Argument must be a matrix.
>
> Octave does not like the input image to be a single line.
>
> Best regards!
> Ciao
> Giorgio

Hi Giorgio

could you please tell me what matlab's minmax returns in the following cases?

minmax (1)
minmax ([i 2; 3 4])
minmax (rand (2,2,2))
minmax ({[0 1; -1 -2] [2 3 -2; 8 0 2]; [1 -2] [9 7 3]})
minmax ({[0 1; -1 -2] [2 3; 8 0]; [1 -2] [9 7 3]})
minmax ({[0 1; -1 -2] [2 3 -2; 8 0 2]; [1 -2] [9 7 3; 8 0 2]})

I would expect that some, maybe all, will fail but would like to be
sure to fix this.

Carnë

Re: [OctDev] [gnu.org #779464] FreeBSD vs simplified BSD

[Carnë D. <car...@gm...>]

CC'ing the mailing list with the reply...

On 1 November 2012 22:23, Donald R Robertson III via RT
<lic...@fs...> wrote:
>> [car...@gm... - Sun Oct 28 15:48:26 2012]:
>>
>> Hi
>>
>> I'm the maintainer of the Octave-Forge project
>> http://octave.sourceforge.net/ which is a loosely organized collection
>> of functions for GNU Octave. Because of this, each file has its own
>> license. I'm trying to organize this properly and facing a problem
>> with the multiple BSD licenses.
>>
>> The FreeBSD license seems to exist in 2 forms, with and without a
>> disclaimer about views and opinions expressed in the software. However
>> the FSF list of licenses has both of them under the same name:
>>
>> http://www.gnu.org/licenses/license-list.html#FreeBSD links to
>> http://directory.fsf.org/wiki?title=License:FreeBSD which displays the
>> disclaimer
>> http://www.gnu.org/licenses/license-list.html#FreeBSDDL links to
>> http://www.freebsd.org/copyright/freebsd-doc-license.html which does
>> not displays the disclaimer
>
> The BSDDL is very similar to the FreeBSD license, except that it is for documentation instead of
> software. It also omits the disclaimer found at the end of the FreeBSD license.
>
>>
>> I was reading about the subject and apparently, the OSI recognized
>> both of them, calling the version without the disclaimer, simplified
>> BSD license. In Octave Forge we do have some code under such license
>> but are planning to adopt
>> http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses as
>> the list of allowed licenses. I believe this license also belongs to
>> list of GPL compatible, there's simply no FSF-given name for it. Could
>> you please update the list and advise a name to avoid confusions?
>
> It is a bit confusing, but I think I understand what the issue is here. The FreeBSD license is the two-
> clause or 'simplified BSD' license, but then they also include an additional disclaimer/notice at the
> end of the license. The OSI doesn't seem to address that final disclaimer at the end of the FreeBSD
> license. In looking at their note on the approval of the 2-clause or 'simplified BSD' license, they
> state that it is the license of FreeBSD, <http://opensource.org/licenses/BSD-3-Clause>. But the license
> on FreeBSD does actually include the disclaimer at the end, while the OSI provided copy of the 2-clause
> <http://opensource.org/licenses/BSD-2-Clause> does not. The disclaimer does not seem to appear anywhere
> at OSI.
>
> I would guess that they omitted it because the disclaimer is more like a notice, or just some
> additional information for the user. It does not seem to be a condition of the license. To me, it seems
> that a license that has the disclaimer adds no additional burdens to the user than a license that omits
> it. In short, I am not sure that it is actually a separate license in the practical sense.
>
> Thanks so much for your time, and please let me know if you have further questions.
>
> --
> Sincerely,
>
> Donald R. Robertson, III, J.D.
> Copyright & Licensing Associate
> Free Software Foundation
> 51 Franklin Street, Fifth Floor
> Boston, MA 02110, USA
> Phone +1-617-542-5942
> Fax +1-617-542-2652

Hi Donald

thanks for you answer. I think my confusion came from reading the BSD
license page on wikipedia <http://en.wikipedia.org/wiki/BSD_license>
which reads as if they are indeed two separate licenses: ``Other
projects, such as NetBSD, use a similar 2-clause license, but without
the additional disclaimer. This version has been vetted as an Open
source license by the OSI as the "Simplified BSD License."''

We'll treat them all as FreeBSD licenses from now on.

Thank you once more,
Carnë Draug

[OctDev] License of medfilt1 in Octave-Forge

[Carnë D. <car...@gm...>]

Hi Paul

I'm Carnë Draug, the current maintainer of the Octave Forge. You have
released all of your code under GPL+ or public domain with the
exception of medfilt1 on the signal package.

https://sourceforge.net/p/octave/code/11396/tree/trunk/octave-forge/main/signal/src/medfilt1.cc

Your license text reads:

Copyright 2000 Paul Kienzle <pki...@us...>
This source code is freely redistributable and may be used for
any purpose.  This copyright notice must be maintained.
Paul Kienzle is not responsible for the consequences of using
this software.

However, we decided to drop usage of non-standard licenses. Could you
please use a more standard one? Being able to give it a recognisable
name not only eases our organisation but also its
acceptance by downstream package maintainers such as Debian. From
Debian's upstream guide "Please do not write your own license text if
you can at all avoid it. Depending on your wishes, the GPL, LGPL or a
BSD-style license will most likely be appropriate, and it is far
easier to tell whether something is allowed if we can look at past
discussions of the same text. "

I'm sorry to bother with such non-scientific things. I'm not a lawyer
myself, but unfortunately things like this need to be made clear.
Please just let me know which one you prefer and I'll take care of
everything else.

Thanks in advance,
Carnë Draug

Re: [OctDev] License Andy Adler's code in Octave-Forge

[Carnë D. <car...@gm...>]

Hi everyone

I realize now I should have CC'ed the mailing list from the start to
have this public. Doing it now for those purposes.

I asked Andy to relicense his code in OF (image and general package)
and he agreed to do it for GPLv3+. I have just made the commit that
does exactly that.

https://sourceforge.net/p/octave/code/11396

Carnë

On 5 November 2012 22:04, Andy Adler <ad...@sc...> wrote:
> Hi Carnë
>
> Sorry for the delay.
>
> I'm happy to see it relicenced under the GPL 3+ if you'd like.
>
> Thanks for doing this.
> --
> Andy Adler <ad...@sc...> +1-613-520-2600x8785
>
>
> On 5 November 2012 13:44, Carnë Draug <car...@gm...> wrote:
>> Hi Andy
>>
>> could you please take a look at this soon? I want to make a new
>> release of the image package but the license you wrote for SHA1.cc,
>> bwselect, bwfill and rotate_scale are a blocker. Again, I would
>> recommend that you choose GPLv3+. Otherwise, simplified BSD would work
>> fine. Just write back to me which one and I'll take care of everything
>> else.
>>
>> Thanks,
>> Carnë
>>
>> On 28 October 2012 14:40, Carnë Draug <car...@gm...> wrote:
>>> Hi Andy
>>>
>>> I'm Carnë Draug, current maintainer of the Octave Forge project and
>>> the image package. We have a couple of your functions written by you
>>> in the project. We are very thankful of your contribution but I'm
>>> afraid that the non-standard license you have chosen may become a
>>> problem. Your license text reads:
>>>
>>> // Copyright (C) 1999 Andy Adler
>>> // This code has no warrany whatsoever.
>>> // Do what you like with this code as long as you leave this copyright in place.
>>>
>>> Could you please use a more standard one? Being able to give it a
>>> recognisable name not only eases our organisation but also its
>>> acceptance by downstream package maintainers such as Debian. From
>>> Debian's upstream guide "Please do not write your own license text if
>>> you can at all avoid it. Depending on your wishes, the GPL, LGPL or a
>>> BSD-style license will most likely be appropriate, and it is far
>>> easier to tell whether something is allowed if we can look at past
>>> discussions of the same text. "
>>>
>>> I would prefer if you choose something such as GPLv3+ of course. Your
>>> later contributions to the project were actually under this license,
>>> only your older code shows this license. However, if you wish to keep
>>> the spirit of the current license, some less typical license which
>>> have at least already been revised by the FSF and OSI are (I tried to
>>> sort them in order of how closely they enforce the principles in your
>>> current license):
>>>
>>> * simplifiedBSD (the license in this link is the FreeBSD license. The
>>> simplified BSD refers to the same but without the disclaimer at the
>>> bottom) http://en.wikipedia.org/wiki/BSD_license#2-clause_license_.28.22Simplified_BSD_License.22_or_.22FreeBSD_License.22.29
>>> * ICS license http://en.wikipedia.org/wiki/ISC_license
>>> * Fair license http://en.wikipedia.org/wiki/Fair_Licence
>>> * WTFPL http://en.wikipedia.org/wiki/Do_What_The_Fuck_You_Want_To_Public_License
>>> (not the this one is almost public and would also allow to remove the
>>> copyright provided the name is also changed)
>>>
>>> The files in question are:
>>>
>>> https://sourceforge.net/p/octave/code/11372/tree/trunk/octave-forge/main/general/src/SHA1.cc
>>> https://sourceforge.net/p/octave/code/11372/tree/trunk/octave-forge/main/image/inst/bwselect.m
>>> https://sourceforge.net/p/octave/code/11372/tree/trunk/octave-forge/main/image/src/bwfill.cc
>>> https://sourceforge.net/p/octave/code/11372/tree/trunk/octave-forge/main/image/src/rotate_scale.cc
>>>
>>> On the file https://sourceforge.net/p/octave/code/11372/tree/trunk/octave-forge/main/image/inst/edge.m
>>> there is also a notice on line 138 mentioning that part of the code
>>> bears is under that same copyright notice.
>>>
>>> I'm sorry to bother with such non-scientific things. I'm not a lawyer
>>> myself, but unfortunately things like this need to be made clear.
>>>
>>> Thanks in advance,
>>> Carnë Draug

[OctDev] Octave Users needed for Test of new IDE

[Kate W. <kwi...@fo...>]

We are looking for Octave users to test a new IDE for us sometime on
Thursday or Friday. You should have experience with large datasets.

You will use our new IDE for 30 minutes, and then give us feedback on it.

For your time, you will receive a $50 gift certificate to Amazon.

To participate please reply to this email with a brief note about your
experience with Octave and some times you are available on Thursday or
Friday.

Best,

Kate Willett | *Forio* Online Simulations | http://forio.com
*1159 Howard Street     |     San Francisco, CA 94103      |      (415)
440-7500 ex. 84*

Re: [OctDev] removal of non-standard licenses in Octave Forge

[Juan P. C. <aju...@gm...>]

On Mon, Nov 5, 2012 at 2:57 PM, Carnë Draug <car...@gm...> wrote:
> On 28 October 2012 19:13, Carnë Draug <car...@gm...> wrote:
>> Hi everyone
>>
>> we have a couple of files in Octave Forge with non-standard licenses.
>> This is bad. Being able to give it a recognisable name not only eases
>> our organisation but also its acceptance by downstream package
>> maintainers such as Debian. From Debian's upstream guide "Please do
>> not write your own license text if you can at all avoid it. Depending
>> on your wishes, the GPL, LGPL or a BSD-style license will most likely
>> be appropriate, and it is far easier to tell whether something is
>> allowed if we can look at past discussions of the same text. "
>>
>> I believe that in most cases such user-made licenses are not made
>> because there's no appropriate license out there, but out of
>> indifference for the subject and belief on others better part. For
>> example, some functions in the image package have the following
>> license "This code has no warrany whatsoever. Do what you like with
>> this code as long as you leave this copyright in place" which could
>> easily be replaced by something such as the simplified BSD, FreeBSD or
>> ICS license which I have already suggested to the original author.
>>
>> I'd like to propose that we no longer accept such non-standard
>> licenses and propose this list
>> http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses as
>> the ones that are acceptable. Does anyone oppose to such change?
>>
>> Carnë
>
> After 1 week there has been no opposition.
>
> >From now on, only code under a license listed on
> http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses
> will be released through Octave Forge.
>
> Carnë
>
> ------------------------------------------------------------------------------
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> http://p.sf.net/sfu/logmein12331_d2d
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

Thank you Carnë

Some people may find this table easier to read
http://en.wikipedia.org/wiki/List_of_FSF-approved_software_licenses

Re: [OctDev] removal of non-standard licenses in Octave Forge

[Carnë D. <car...@gm...>]

On 28 October 2012 19:13, Carnë Draug <car...@gm...> wrote:
> Hi everyone
>
> we have a couple of files in Octave Forge with non-standard licenses.
> This is bad. Being able to give it a recognisable name not only eases
> our organisation but also its acceptance by downstream package
> maintainers such as Debian. From Debian's upstream guide "Please do
> not write your own license text if you can at all avoid it. Depending
> on your wishes, the GPL, LGPL or a BSD-style license will most likely
> be appropriate, and it is far easier to tell whether something is
> allowed if we can look at past discussions of the same text. "
>
> I believe that in most cases such user-made licenses are not made
> because there's no appropriate license out there, but out of
> indifference for the subject and belief on others better part. For
> example, some functions in the image package have the following
> license "This code has no warrany whatsoever. Do what you like with
> this code as long as you leave this copyright in place" which could
> easily be replaced by something such as the simplified BSD, FreeBSD or
> ICS license which I have already suggested to the original author.
>
> I'd like to propose that we no longer accept such non-standard
> licenses and propose this list
> http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses as
> the ones that are acceptable. Does anyone oppose to such change?
>
> Carnë

After 1 week there has been no opposition.

>From now on, only code under a license listed on
http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses
will be released through Octave Forge.

Carnë

Re: [OctDev] Image package (imread problem)

[Carnë D. <car...@gm...>]

On 5 November 2012 07:05, Lucas Sá <luc...@gm...> wrote:
> Today I noticed that the image package treats indexed images differently in
> functions within the module.
>
> Using [X, map] = imread will give me a matrix X with values from 0 to n-1,
> while all other image package functions expect index mapping from 1 to n,
> such as imshow, ind2rgb, ind2gray.
>
> This fact makes the execution of a simple imshow('some_file.gif') to show
> something different from the original image. imshow(X+1, map) would show it
> fine as well.
>
> The function ind2rgb, for example, even has a validation for indices less
> than 1 in line 43 of ind2rgb.m:
>
>   ## Check if X is an indexed image.
>   if (ndims (x) != 2 || any (x(:) != fix (x(:))) || min (x(:)) < 1)
>     error ("ind2rgb: X must be an indexed image");
>
>
> Is it normal that I am receving 0 values in X matrix? I am using octave
> 3.6.2 and graphicsmagick 1.3.16.

Hi Lucas

imshow, ind2rgb and ind2gray do not belong to the image package, they
belong to octave core. I'm CC'ing the octave core mailing list.

If you believe this to be a bug, please report at at
http://savannah.gnu.org/bugs/?func=additem&group=octave

Carnë

[OctDev] Non-linear optimization: optim 1.2.2 released

[Carnë D. <car...@gm...>]

Hi everyone

a new release of optim package is out, version 1.2.2, by Olaf Till.
Enjoy Octave responsibly.

Carnë

[OctDev] optim-1.2.2 release

[Olaf T. <i7...@t-...>]

Hi,

optim-1.2.2 has been posted to the release forum. It is a bug-fix
release. Could you please release it?

Olaf

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

[OctDev] Image package (imread problem)

[Lucas Sá <luc...@gm...>]

Today I noticed that the image package treats indexed images differently in
functions within the module.

Using [X, map] = *imread *will give me a matrix X with values from 0 to
n-1, while all other image package functions expect index mapping from 1 to
n, such as *imshow*, *ind2rgb*, *ind2gray*.

This fact makes the execution of a simple *imshow('some_file.gif') *to show
something different from the original image. imshow(*X+1*, map) would show
it fine as well.

The function ind2rgb, for example, even has a validation for indices less
than 1 in line 43 of ind2rgb.m:

  ## Check if X is an indexed image.
  if (ndims (x) != 2 || any (x(:) != fix (x(:))) || *min (x(:)) < 1*)
    error ("ind2rgb: X must be an indexed image");


Is it normal that I am receving 0 values in X matrix? I am using octave
3.6.2 and graphicsmagick 1.3.16.

Re: [OctDev] Function ILU

[c. <car...@gm...>]

On 4 Nov 2012, at 23:58, marco atzeri wrote:

> On 11/4/2012 11:48 PM, Giovanni Matteo Fumarola wrote:
>> Dear all,
>> I'm Giovanni Matteo Fumarola, a italian student of Computer Science of
>> Politecnico di Milano.
>> For a university project, I want to realize a ILU function, this is
>> missing in Octave.
>> I send you this mail for know if someone has working about it, and some
>> information about octave standard for development.
>> 
>> Best Regard
>> Fumarola GM
>> 
> 
> Hi Giovanni,
> are you planning to add the fuction as addon package or
> as core octave function ?
> 
> In the second case the right mailing list is:
> https://mailman.cae.wisc.edu/listinfo/octave-maintainers
> 
> Regards
> MArco

Giovanni,

ILU is a core Matlab function so it should go into core Octave in principle
as Marco suggested.


On the other hand, Octave has more strict requirements for accepting contributed code than Octave-Forge,
so I suggest you start by contributing your function to the Octave-Forge in the package linear_algebra 
and then we can help you moving it into Octave later.

Anyway it is a good idea to ask on the maintainers list as well to know if someone else is working on this.

Here is some general info about contributing to Octave:
http://www.gnu.org/software/octave/doc/interpreter/Contributing-Guidelines.html#Contributing-Guidelines

and to Octave Forge:
http://wiki.octave.org/Contributing_to_the_development_of_packages/modules


Welcome to Octave!
Carlo

[OctDev] Queueing Networks and Markov chains analysis: queueing 1.2.0 released

[Carnë D. <car...@gm...>]

Hi everyone

a new release of queueing package is out, version 1.2.0, by Moreno Marzolla.
Enjoy Octave responsibly.

Carnë

Re: [OctDev] Function ILU

[marco a. <mar...@gm...>]

On 11/4/2012 11:48 PM, Giovanni Matteo Fumarola wrote:
> Dear all,
> I'm Giovanni Matteo Fumarola, a italian student of Computer Science of
> Politecnico di Milano.
> For a university project, I want to realize a ILU function, this is
> missing in Octave.
> I send you this mail for know if someone has working about it, and some
> information about octave standard for development.
>
> Best Regard
> Fumarola GM
>

Hi Giovanni,
are you planning to add the fuction as addon package or
as core octave function ?

In the second case the right mailing list is:
https://mailman.cae.wisc.edu/listinfo/octave-maintainers

Regards
MArco

[OctDev] Function ILU

[Giovanni M. F. <gio...@gm...>]

Dear all,
I'm Giovanni Matteo Fumarola, a italian student of Computer Science of
Politecnico di Milano.
For a university project, I want to realize a ILU function, this is missing
in Octave.
I send you this mail for know if someone has working about it, and some
information about octave standard for development.

Best Regard
Fumarola GM

Re: [OctDev] complex error function

[Steven G. J. <st...@al...>]

There is an updated version of my package 
(http://ab-initio.mit.edu/Faddeeva) which computes not only the Faddeeva 
function (the scaled complex error function) but also the ordinary erf 
and erfc functions of complex arguments, as well as the erfcx and erfi 
variants and the Dawson function (a scaled erfi).

This should make it relatively painless to drop it in as a replacement 
for the Octave erf and erfc functions in order to support complex arguments.

I would also strongly recommend providing user-callable interfaces for 
the erfcx, erfi, Dawson, and Faddeeva functions as well.  (The scaled 
variants are especially important to work with error functions in the 
regimes where they are exponentially small or large, in order to avoid 
overflow/underflow limitations.)

Let me know if there is anything else I can do to help.

Steven

[OctDev] control 2.4.1 released

[Carnë D. <car...@gm...>]

Hi everyone

a new release of the control package is out, version 2.4.1, by Lukas Reichlin.
Enjoy Octave responsibly.

Carnë