octave-dev — GNU Octave developers' list

[OctDev] Fem PLotting: fpl 1.3.2 released

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

Hi everyone

a new release of fpl package is out, version 1.3.2, by Carlo de Falco.
Enjoy Octave responsibly.

Carnë

Re: [OctDev] xlread in 3.6.1

[Philip N. <pr....@hc...>]

TedSwift [via Octave] wrote:
> I've followed this thread, but am still not able to get
> chk_spreadsheet_support
> to check out right. After putting Java in what I thought was the right
> place, these are the results of my last check:
>
> octave:5> chk_spreadsheet_support ('', 3)
>
> Checking Excel/ActiveX/COM... not working.
>
> Checking Java support...
> 1. Checking Java JRE presence.... OK, found one.
> 2. Checking Octave Java support... error: No Java support found:
> `java_invoke' undefined near line 49 column 16.

=> no or improperly installed Java package.

> error: called from:
> error:
> C:/Octave/Octave3.6.1_gcc4.6.2/share/octave/packages\io-1.0.18\chk_spreadsheet_support.m
> at line 176, column 3
>
> Something fundamental is still missing, or I don't have the setenv path
> set right. Are there any other diagnostic tools that will help me figure
> out where the breakdown is? Thanks, all.

Try to run the newest Java package preinstall.m before your next attempt 
to install the Java package (any version).
This file is in the svn repo here:

http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/java/pre_install.m?sortby=rev&view=log
(watch for line wrap, take revision 10760, "download" or "as text", be 
sure to save it as a .m-file, and run it in Octave)

I've only recently committed it in an attempt to avoid half-baked Java 
package installations.
It'll check where Octave should look for the jvm lib and the executables 
and will complain if any of them is not found.

I think the fact that the Java package installer not being able to find 
the Java executables (java, jar, javac) in the place it expects them to 
be was the creepy showstopper in many frustrating cases.
You might make symlinks to them in your $PATH (in my Mageia 2 linux 
installation they seem to be silently created in /usr/bin by urpmi).

Please copy preinstall.m's error msg (if any) in a reply mail. For me 
that's handy to have, because I might decide to implement (parts of) 
preinstall.m's functionality in chk_spreadsheet_support as well.

BTW I've also recently updated the Octave wiki on exactly this subject:
http://wiki.octave.org/Java_package#Make_sure_that_the_build_environment_is_configured_properly
(line wrap!)

Philip

Re: [OctDev] xlread in 3.6.1

[Markus B. [v. Octave] <ml-...@n4...>]

Am 13.09.2012 01:17 schrieb "TedSwift" <ts...@wa...>:
>
> I've followed this thread, but am still not able to get
> chk_spreadsheet_support
> to check out right. After putting Java in what I thought was the right
> place, these are the results of my last check:
>
> octave:5> chk_spreadsheet_support ('', 3)
>
> Checking Excel/ActiveX/COM... not working.
>
> Checking Java support...
>   1. Checking Java JRE presence.... OK, found one.
>   2. Checking Octave Java support... error: No Java support found:
> `java_invoke' undefined near line 49 column 16.
> error: called from:
> error:
>
C:/Octave/Octave3.6.1_gcc4.6.2/share/octave/packages\io-1.0.18\chk_spreadsheet_support.m
> at line 176, column 3
>
> Something fundamental is still missing, or I don't have the setenv path
set
> right. Are there any other diagnostic tools that will help me figure out
> where the breakdown is? Thanks, all.
> -Ted

You could try to follow Thema instruction in the Wiki from arch linux.
https://wiki.archlinux.org/index.php/Octave

>
>
>
> --
> View this message in context:
http://octave.1599824.n4.nabble.com/xlread-in-3-6-0-tp4451557p4644061.html
> Sent from the Octave - General mailing list archive at Nabble.com.
> _______________________________________________
> Help-octave mailing list
> Hel...@oc...
> https://mailman.cae.wisc.edu/listinfo/help-octave

_______________________________________________
Help-octave mailing list
Hel...@oc...
https://mailman.cae.wisc.edu/listinfo/help-octave




_______________________________________________
If you reply to this email, your message will be added to the discussion below:
http://octave.1599824.n4.nabble.com/xlread-in-3-6-0-tp4451557p4644065.html

To unsubscribe from xlread in 3.6.0, visit http://octave.1599824.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4451557&code=b2N0YXZlLWRldkBsaXN0cy5zb3VyY2Vmb3JnZS5uZXR8NDQ1MTU1N3wtODQ3MzA3MzI2

Re: [OctDev] xlread in 3.6.1

[TedSwift [v. Octave] <ml-...@n4...>]

I've followed this thread, but am still not able to get 
chk_spreadsheet_support
to check out right. After putting Java in what I thought was the right
place, these are the results of my last check:

octave:5> chk_spreadsheet_support ('', 3)

Checking Excel/ActiveX/COM... not working.

Checking Java support...
  1. Checking Java JRE presence.... OK, found one.
  2. Checking Octave Java support... error: No Java support found:
`java_invoke' undefined near line 49 column 16.
error: called from:
error:  
C:/Octave/Octave3.6.1_gcc4.6.2/share/octave/packages\io-1.0.18\chk_spreadsheet_support.m
at line 176, column 3

Something fundamental is still missing, or I don't have the setenv path set
right. Are there any other diagnostic tools that will help me figure out
where the breakdown is? Thanks, all.
-Ted



_______________________________________________
If you reply to this email, your message will be added to the discussion below:
http://octave.1599824.n4.nabble.com/xlread-in-3-6-0-tp4451557p4644061.html

To unsubscribe from xlread in 3.6.0, visit http://octave.1599824.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4451557&code=b2N0YXZlLWRldkBsaXN0cy5zb3VyY2Vmb3JnZS5uZXR8NDQ1MTU1N3wtODQ3MzA3MzI2

[OctDev] Fwd: Application to use SPM ID Toolbox

[Lukas R. <luk...@gm...>]

Begin forwarded message:

> From: Lukas Reichlin <luk...@gm...>
> Date: 12. September 2012 13:42:25 MESZ
> To: Juan Pablo Carbajal <car...@if...>
> Cc: Brett Ninness <bre...@ne...>
> Subject: Re: Application to use SPM ID Toolbox
> 
> Dear Brett,
> 
> Sounds like very good news! :-)
> 
> Regarding Octave installation on a Mac, I recommend the use of the Fink package manager [1] because of its well-maintained and up-to-date Octave packages. First install the Xcode tools, then Fink according to the instructions on [1]. After that step, run
> 	fink selfupdate
> followed by
> 	fink update all
> Then use
> 	fink install PACKAGE
> where PACKAGE stands for octave363-ref, octave363-ref-dev and octave-ref
> There are many dependencies and building takes some time.
> Once Octave is installed, run
> 	pkg install -forge control
> from the Octave prompt to download, compile and install the control package. You can check the package by running test_control.
> 
> Hope this helps!
> 
> Best regards,
> Lukas
> 
> 
> [1]
> http://www.finkproject.org/
> 
> 
> On 12.09.2012, at 12:39, Juan Pablo Carbajal wrote:
> 
>> Dear Brett,
>> 
>> This are great news! I am very happy.
>> I have forwarded your mail to the packages developer mailing list
>> <oct...@li...> and to the help mailing list
>> <hel...@oc...>, we will try to support you as much as
>> possible.
>> 
>> Lukas (in CC) is the developer and maintainer of the control package.
>> He also uses Mac, so it should be easy to get help on this platform.
>> 
>> Looking forward for SPM for GNU Octave. Remember that the only
>> constraint that we have is code released under GPL compatible licenses
>> :D.
>> 
>> Please let me know if I can be of any assistance.
>> 
>> Regards,
>> 
>> JPi
>> 
>> 
>> On Wed, Sep 12, 2012 at 11:52 AM, Brett Ninness
>> <bre...@ne...> wrote:
>>> Dear Juan Pablo,
>>> 
>>> Thanks for your email.
>>> 
>>> The situation regarding the toolbox has changed since last I wrote - I am currently actively updating it and in fact just
>>> in the last few weeks was investigating what it would take to make it run under octave.
>>> 
>>> A problem here is that I work on a Mac, and the distribution of octave on that platform does not seem to be so well supported.
>>> 
>>> To begin with, there is no .pkg or .dmg distribution as for almost all other mac software - one needs to install fink.
>>> 
>>> I have done that, but then the octave package management does not seem to work - attached is a screen grab on my mac
>>> illustrating that I cannot install the control package you mention.
>>> 
>>> Having said that - I am very interested in making my software available and working with octave.
>>> 
>>> Best regards
>>> 
>>> Brett
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> Dear Brett Ninness,
>>>> 
>>>> I am writing you once more in relation to the SPM toolbox
>>>> (http://sigpromu.org/idtoolbox/).
>>>> 
>>>> GNU Octave is now in its 3.6.x version and the packages are
>>>> experiencing fast development. Take for example (and most related to
>>>> your package) the control package
>>>> (http://octave.sourceforge.net/control/overview.html). You may notice
>>>> under the section "Experimental data handling" and "System
>>>> identification" some interesting new functionality.
>>>> 
>>>> Do you have plans to release your package under a GPL compatible
>>>> license (http://en.wikipedia.org/wiki/List_of_FSF-approved_software_licenses)?
>>>> Only under this licesing scheme we can include and extended your
>>>> package into GNU Octave packages. It may be advantageous, in terms of
>>>> visibility and use, to release a free version that can be shipped with
>>>> GNU Octave packages, since users can download it and install it
>>>> directly from the prompt. Additionally, the packages that are most
>>>> popular are shipped within Linux distributions like Debian and Fedora.
>>>> 
>>>> Please let us know about your decision.
>>>> 
>>>> Thank you very much in advance.
>>>> 
>>>> Kind regards,
>>>> 
>>>> On Tue, Jul 12, 2011 at 3:28 PM, Brett Ninness
>>>> <Bre...@ne...> wrote:
>>>>> Dear Juan Pablo
>>>>> 
>>>>> Many thanks for your interest in our toolbox.
>>>>> 
>>>>> We began with octave compatibility, but as the toolbox evolved and we started to use
>>>>> more new matlab features, we have not have the manpower/time to maintain octave
>>>>> compatibility, and do not currently have plans for octave 3.5.0+ porting.
>>>>> 
>>>>> Best regards
>>>>> 
>>>>> Brett
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> Dear Brett,
>>>>>> 
>>>>>> Thank you very much for your toolbox.
>>>>>> I am trying to run it in Octave 3.5.0+ and it doesn't work. On one
>>>>>> side the control functions of octave have been updated and the old
>>>>>> ones (that apparently are dumped by Mathworks in the signal toolbox)
>>>>>> were removed, but I am working on it. On the other side, I found some
>>>>>> bugs in your package.
>>>>>> 
>>>>>> For example, the function rksqrtv.m is empty! which makes demo_unit
>>>>>> option 19 fail. However, even if the function were there, with the
>>>>>> interface as explained in the help, then ks.m would produce an error
>>>>>> at the end, because the matrix G has no field called ss.
>>>>>> 
>>>>>> Another bug I found in m2f line 165. The output of mimofr would be of
>>>>>> size number-of-ouputs x number-of-inputs x number-of-frequencies. As
>>>>>> it is used there, the addition will fail for the option 20 of
>>>>>> demo_unit I corrected by doing
>>>>>>                    G.H=mimofr(G.ss.A,G.ss.K,G.ss.C,[],ww);
>>>>>>                            DK = eye(size(G.H,1),size(G.H,2));
>>>>>>                            G.H=G.H + DK(:,:,ones(1,length(ww)));
>>>>>> 
>>>>>> by the way, if you were aiming to make UNIT compatible with Octave
>>>>>> 3.5.0+, you would have freqresp.m available in the control package.
>>>>>> 
>>>>>> Are you planning to produce an Octave 3.5.0+ compatible version of
>>>>>> your excellent package?
>>>>>> 
>>>>>> Thanks again,
>>>>>> 
>>>>>> Regards,
>>>>>> 
>>>>>> On Fri, Jul 1, 2011 at 1:34 AM, SPM Admin
>>>>>> <Bre...@ne...> wrote:
>>>>>>> Dear Juan Pablo Carbajal,
>>>>>>> 
>>>>>>> This email has been sent in response to a request for downloads
>>>>>>> registration at http://sigpromu.org/idtoolbox/
>>>>>>> If you did not request registration, you may safely ignore this email.
>>>>>>> 
>>>>>>> Otherwise, thank you for your interest.
>>>>>>> 
>>>>>>> You may log into the site with the following details:
>>>>>>> 
>>>>>>> email:      car...@if...
>>>>>>> Access Key: r6cst
>>>>>>> 
>>>>>>> Regards,
>>>>>>> 
>>>>>>> Brett Ninness
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> M. Sc. Juan Pablo Carbajal
>>>>>> -----
>>>>>> PhD Student
>>>>>> University of Zürich
>>>>>> www.ailab.ch/carbajal
>>>>> 
>>>>> 
>>>>> ------------------------------------------
>>>>> 
>>>>> Brett Ninness,
>>>>> School of Elec.Eng&Comp.Sci.
>>>>> University of Newcastle,
>>>>> Callaghan, 2308, AUSTRALIA
>>>>> 
>>>>> Phone: +61 (0)2 49 216032
>>>>> FAX:   +61 (0)2 49 216993
>>>>> 
>>>>> http://sigpromu.org/brett/
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> M. Sc. Juan Pablo Carbajal
>>>> -----
>>>> PhD Student
>>>> University of Zürich
>>>> http://ailab.ifi.uzh.ch/carbajal/
>>> 
>>> 
>>> ------------------------------------------
>>> 
>>> Brett Ninness,
>>> School of Elec.Eng&Comp.Sci.
>>> University of Newcastle,
>>> Callaghan, 2308, AUSTRALIA
>>> 
>>> Phone: +61 (0)2 49 216032
>>> FAX:   +61 (0)2 49 216993
>>> 
>>> http://sigpromu.org/brett/
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> -- 
>> M. Sc. Juan Pablo Carbajal
>> -----
>> PhD Student
>> University of Zürich
>> http://ailab.ifi.uzh.ch/carbajal/
> 

Re: [OctDev] Application to use SPM ID Toolbox

[Ben A. <bpa...@ma...>]

On Sep 12, 2012, at 6:20 AM, Juan Pablo Carbajal wrote:

> Dear developers and user,
> 
> Please read the following answer from the SPM developer.
> 
> @Lukas: I think you work in Mac, right? Can you give him some tips?
> 
> We may get a great System Indentification toolbox in Octave! :D

Juan,

Did Brett figure out that he needs to use Fink to install the control package for Octave?

For Octave 3.6.3, the syntax to install the control package is ...

	fink install control-oct363

Ben

> ---------- Forwarded message ----------
> From: Brett Ninness <bre...@ne...>
> Date: Wed, Sep 12, 2012 at 11:52 AM
> Subject: Re: Application to use SPM ID Toolbox
> To: Juan Pablo Carbajal <car...@if...>
> 
> 
> Dear Juan Pablo,
> 
> Thanks for your email.
> 
> The situation regarding the toolbox has changed since last I wrote - I
> am currently actively updating it and in fact just
> in the last few weeks was investigating what it would take to make it
> run under octave.
> 
> A problem here is that I work on a Mac, and the distribution of octave
> on that platform does not seem to be so well supported.
> 
> To begin with, there is no .pkg or .dmg distribution as for almost all
> other mac software - one needs to install fink.
> 
> I have done that, but then the octave package management does not seem
> to work - attached is a screen grab on my mac
> illustrating that I cannot install the control package you mention.
> 
> Having said that - I am very interested in making my software
> available and working with octave.
> 
> Best regards
> 
> Brett
> 
> 
> 
> 
> 
>> Dear Brett Ninness,
>> 
>> I am writing you once more in relation to the SPM toolbox
>> (http://sigpromu.org/idtoolbox/).
>> 
>> GNU Octave is now in its 3.6.x version and the packages are
>> experiencing fast development. Take for example (and most related to
>> your package) the control package
>> (http://octave.sourceforge.net/control/overview.html). You may notice
>> under the section "Experimental data handling" and "System
>> identification" some interesting new functionality.
>> 
>> Do you have plans to release your package under a GPL compatible
>> license (http://en.wikipedia.org/wiki/List_of_FSF-approved_software_licenses)?
>> Only under this licesing scheme we can include and extended your
>> package into GNU Octave packages. It may be advantageous, in terms of
>> visibility and use, to release a free version that can be shipped with
>> GNU Octave packages, since users can download it and install it
>> directly from the prompt. Additionally, the packages that are most
>> popular are shipped within Linux distributions like Debian and Fedora.
>> 
>> Please let us know about your decision.
>> 
>> Thank you very much in advance.
>> 
>> Kind regards,
>> 
>> On Tue, Jul 12, 2011 at 3:28 PM, Brett Ninness
>> <Bre...@ne...> wrote:
>>> Dear Juan Pablo
>>> 
>>> Many thanks for your interest in our toolbox.
>>> 
>>> We began with octave compatibility, but as the toolbox evolved and we started to use
>>> more new matlab features, we have not have the manpower/time to maintain octave
>>> compatibility, and do not currently have plans for octave 3.5.0+ porting.
>>> 
>>> Best regards
>>> 
>>> Brett
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> Dear Brett,
>>>> 
>>>> Thank you very much for your toolbox.
>>>> I am trying to run it in Octave 3.5.0+ and it doesn't work. On one
>>>> side the control functions of octave have been updated and the old
>>>> ones (that apparently are dumped by Mathworks in the signal toolbox)
>>>> were removed, but I am working on it. On the other side, I found some
>>>> bugs in your package.
>>>> 
>>>> For example, the function rksqrtv.m is empty! which makes demo_unit
>>>> option 19 fail. However, even if the function were there, with the
>>>> interface as explained in the help, then ks.m would produce an error
>>>> at the end, because the matrix G has no field called ss.
>>>> 
>>>> Another bug I found in m2f line 165. The output of mimofr would be of
>>>> size number-of-ouputs x number-of-inputs x number-of-frequencies. As
>>>> it is used there, the addition will fail for the option 20 of
>>>> demo_unit I corrected by doing
>>>>                     G.H=mimofr(G.ss.A,G.ss.K,G.ss.C,[],ww);
>>>>                             DK = eye(size(G.H,1),size(G.H,2));
>>>>                             G.H=G.H + DK(:,:,ones(1,length(ww)));
>>>> 
>>>> by the way, if you were aiming to make UNIT compatible with Octave
>>>> 3.5.0+, you would have freqresp.m available in the control package.
>>>> 
>>>> Are you planning to produce an Octave 3.5.0+ compatible version of
>>>> your excellent package?
>>>> 
>>>> Thanks again,
>>>> 
>>>> Regards,
>>>> 
>>>> On Fri, Jul 1, 2011 at 1:34 AM, SPM Admin
>>>> <Bre...@ne...> wrote:
>>>>> Dear Juan Pablo Carbajal,
>>>>> 
>>>>> This email has been sent in response to a request for downloads
>>>>> registration at http://sigpromu.org/idtoolbox/
>>>>> If you did not request registration, you may safely ignore this email.
>>>>> 
>>>>> Otherwise, thank you for your interest.
>>>>> 
>>>>> You may log into the site with the following details:
>>>>> 
>>>>> email:      car...@if...
>>>>> Access Key: r6cst
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> Brett Ninness
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> M. Sc. Juan Pablo Carbajal
>>>> -----
>>>> PhD Student
>>>> University of Zürich
>>>> www.ailab.ch/carbajal
>>> 
>>> 
>>> ------------------------------------------
>>> 
>>> Brett Ninness,
>>> School of Elec.Eng&Comp.Sci.
>>> University of Newcastle,
>>> Callaghan, 2308, AUSTRALIA
>>> 
>>> Phone: +61 (0)2 49 216032
>>> FAX:   +61 (0)2 49 216993
>>> 
>>> http://sigpromu.org/brett/
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> --
>> M. Sc. Juan Pablo Carbajal
>> -----
>> PhD Student
>> University of Zürich
>> http://ailab.ifi.uzh.ch/carbajal/
> 
> 
> ------------------------------------------
> 
> Brett Ninness,
> School of Elec.Eng&Comp.Sci.
> University of Newcastle,
> Callaghan, 2308, AUSTRALIA
> 
> Phone: +61 (0)2 49 216032
> FAX:   +61 (0)2 49 216993
> 
> http://sigpromu.org/brett/
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -- 
> M. Sc. Juan Pablo Carbajal
> -----
> PhD Student
> University of Zürich
> http://ailab.ifi.uzh.ch/carbajal/
> <Screen Shot 2012-09-12 at 10.48.33 AM.png><Brett Ninness.vcf>_______________________________________________
> Help-octave mailing list
> Hel...@oc...
> https://mailman.cae.wisc.edu/listinfo/help-octave

[OctDev] Application to use SPM ID Toolbox

[Juan P. C. <car...@if...>]

Dear developers and user,

Please read the following answer from the SPM developer.

@Lukas: I think you work in Mac, right? Can you give him some tips?

We may get a great System Indentification toolbox in Octave! :D



---------- Forwarded message ----------
From: Brett Ninness <bre...@ne...>
Date: Wed, Sep 12, 2012 at 11:52 AM
Subject: Re: Application to use SPM ID Toolbox
To: Juan Pablo Carbajal <car...@if...>


Dear Juan Pablo,

Thanks for your email.

The situation regarding the toolbox has changed since last I wrote - I
am currently actively updating it and in fact just
in the last few weeks was investigating what it would take to make it
run under octave.

A problem here is that I work on a Mac, and the distribution of octave
on that platform does not seem to be so well supported.

To begin with, there is no .pkg or .dmg distribution as for almost all
other mac software - one needs to install fink.

I have done that, but then the octave package management does not seem
to work - attached is a screen grab on my mac
illustrating that I cannot install the control package you mention.

Having said that - I am very interested in making my software
available and working with octave.

Best regards

Brett





> Dear Brett Ninness,
>
> I am writing you once more in relation to the SPM toolbox
> (http://sigpromu.org/idtoolbox/).
>
> GNU Octave is now in its 3.6.x version and the packages are
> experiencing fast development. Take for example (and most related to
> your package) the control package
> (http://octave.sourceforge.net/control/overview.html). You may notice
> under the section "Experimental data handling" and "System
> identification" some interesting new functionality.
>
> Do you have plans to release your package under a GPL compatible
> license (http://en.wikipedia.org/wiki/List_of_FSF-approved_software_licenses)?
> Only under this licesing scheme we can include and extended your
> package into GNU Octave packages. It may be advantageous, in terms of
> visibility and use, to release a free version that can be shipped with
> GNU Octave packages, since users can download it and install it
> directly from the prompt. Additionally, the packages that are most
> popular are shipped within Linux distributions like Debian and Fedora.
>
> Please let us know about your decision.
>
> Thank you very much in advance.
>
> Kind regards,
>
> On Tue, Jul 12, 2011 at 3:28 PM, Brett Ninness
> <Bre...@ne...> wrote:
>> Dear Juan Pablo
>>
>> Many thanks for your interest in our toolbox.
>>
>> We began with octave compatibility, but as the toolbox evolved and we started to use
>> more new matlab features, we have not have the manpower/time to maintain octave
>> compatibility, and do not currently have plans for octave 3.5.0+ porting.
>>
>> Best regards
>>
>> Brett
>>
>>
>>
>>
>>
>>
>>> Dear Brett,
>>>
>>> Thank you very much for your toolbox.
>>> I am trying to run it in Octave 3.5.0+ and it doesn't work. On one
>>> side the control functions of octave have been updated and the old
>>> ones (that apparently are dumped by Mathworks in the signal toolbox)
>>> were removed, but I am working on it. On the other side, I found some
>>> bugs in your package.
>>>
>>> For example, the function rksqrtv.m is empty! which makes demo_unit
>>> option 19 fail. However, even if the function were there, with the
>>> interface as explained in the help, then ks.m would produce an error
>>> at the end, because the matrix G has no field called ss.
>>>
>>> Another bug I found in m2f line 165. The output of mimofr would be of
>>> size number-of-ouputs x number-of-inputs x number-of-frequencies. As
>>> it is used there, the addition will fail for the option 20 of
>>> demo_unit I corrected by doing
>>>                      G.H=mimofr(G.ss.A,G.ss.K,G.ss.C,[],ww);
>>>                              DK = eye(size(G.H,1),size(G.H,2));
>>>                              G.H=G.H + DK(:,:,ones(1,length(ww)));
>>>
>>> by the way, if you were aiming to make UNIT compatible with Octave
>>> 3.5.0+, you would have freqresp.m available in the control package.
>>>
>>> Are you planning to produce an Octave 3.5.0+ compatible version of
>>> your excellent package?
>>>
>>> Thanks again,
>>>
>>> Regards,
>>>
>>> On Fri, Jul 1, 2011 at 1:34 AM, SPM Admin
>>> <Bre...@ne...> wrote:
>>>> Dear Juan Pablo Carbajal,
>>>>
>>>> This email has been sent in response to a request for downloads
>>>> registration at http://sigpromu.org/idtoolbox/
>>>> If you did not request registration, you may safely ignore this email.
>>>>
>>>> Otherwise, thank you for your interest.
>>>>
>>>> You may log into the site with the following details:
>>>>
>>>> email:      car...@if...
>>>> Access Key: r6cst
>>>>
>>>> Regards,
>>>>
>>>> Brett Ninness
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> M. Sc. Juan Pablo Carbajal
>>> -----
>>> PhD Student
>>> University of Zürich
>>> www.ailab.ch/carbajal
>>
>>
>> ------------------------------------------
>>
>> Brett Ninness,
>> School of Elec.Eng&Comp.Sci.
>> University of Newcastle,
>> Callaghan, 2308, AUSTRALIA
>>
>> Phone: +61 (0)2 49 216032
>> FAX:   +61 (0)2 49 216993
>>
>> http://sigpromu.org/brett/
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
> --
> M. Sc. Juan Pablo Carbajal
> -----
> PhD Student
> University of Zürich
> http://ailab.ifi.uzh.ch/carbajal/


------------------------------------------

Brett Ninness,
School of Elec.Eng&Comp.Sci.
University of Newcastle,
Callaghan, 2308, AUSTRALIA

Phone: +61 (0)2 49 216032
FAX:   +61 (0)2 49 216993

http://sigpromu.org/brett/










-- 
M. Sc. Juan Pablo Carbajal
-----
PhD Student
University of Zürich
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] Application to use SPM ID Toolbox

[Juan P. C. <car...@if...>]

Dear Brett Ninness,

I am writing you once more in relation to the SPM toolbox
(http://sigpromu.org/idtoolbox/).

GNU Octave is now in its 3.6.x version and the packages are
experiencing fast development. Take for example (and most related to
your package) the control package
(http://octave.sourceforge.net/control/overview.html). You may notice
under the section "Experimental data handling" and "System
identification" some interesting new functionality.

Do you have plans to release your package under a GPL compatible
license (http://en.wikipedia.org/wiki/List_of_FSF-approved_software_licenses)?
Only under this licesing scheme we can include and extended your
package into GNU Octave packages. It may be advantageous, in terms of
visibility and use, to release a free version that can be shipped with
GNU Octave packages, since users can download it and install it
directly from the prompt. Additionally, the packages that are most
popular are shipped within Linux distributions like Debian and Fedora.

Please let us know about your decision.

Thank you very much in advance.

Kind regards,

On Tue, Jul 12, 2011 at 3:28 PM, Brett Ninness
<Bre...@ne...> wrote:
> Dear Juan Pablo
>
> Many thanks for your interest in our toolbox.
>
> We began with octave compatibility, but as the toolbox evolved and we started to use
> more new matlab features, we have not have the manpower/time to maintain octave
> compatibility, and do not currently have plans for octave 3.5.0+ porting.
>
> Best regards
>
> Brett
>
>
>
>
>
>
>> Dear Brett,
>>
>> Thank you very much for your toolbox.
>> I am trying to run it in Octave 3.5.0+ and it doesn't work. On one
>> side the control functions of octave have been updated and the old
>> ones (that apparently are dumped by Mathworks in the signal toolbox)
>> were removed, but I am working on it. On the other side, I found some
>> bugs in your package.
>>
>> For example, the function rksqrtv.m is empty! which makes demo_unit
>> option 19 fail. However, even if the function were there, with the
>> interface as explained in the help, then ks.m would produce an error
>> at the end, because the matrix G has no field called ss.
>>
>> Another bug I found in m2f line 165. The output of mimofr would be of
>> size number-of-ouputs x number-of-inputs x number-of-frequencies. As
>> it is used there, the addition will fail for the option 20 of
>> demo_unit I corrected by doing
>>                       G.H=mimofr(G.ss.A,G.ss.K,G.ss.C,[],ww);
>>                               DK = eye(size(G.H,1),size(G.H,2));
>>                               G.H=G.H + DK(:,:,ones(1,length(ww)));
>>
>> by the way, if you were aiming to make UNIT compatible with Octave
>> 3.5.0+, you would have freqresp.m available in the control package.
>>
>> Are you planning to produce an Octave 3.5.0+ compatible version of
>> your excellent package?
>>
>> Thanks again,
>>
>> Regards,
>>
>> On Fri, Jul 1, 2011 at 1:34 AM, SPM Admin
>> <Bre...@ne...> wrote:
>>> Dear Juan Pablo Carbajal,
>>>
>>> This email has been sent in response to a request for downloads
>>> registration at http://sigpromu.org/idtoolbox/
>>> If you did not request registration, you may safely ignore this email.
>>>
>>> Otherwise, thank you for your interest.
>>>
>>> You may log into the site with the following details:
>>>
>>> email:      car...@if...
>>> Access Key: r6cst
>>>
>>> Regards,
>>>
>>> Brett Ninness
>>>
>>>
>>>
>>
>>
>>
>> --
>> M. Sc. Juan Pablo Carbajal
>> -----
>> PhD Student
>> University of Zürich
>> www.ailab.ch/carbajal
>
>
> ------------------------------------------
>
> Brett Ninness,
> School of Elec.Eng&Comp.Sci.
> University of Newcastle,
> Callaghan, 2308, AUSTRALIA
>
> Phone: +61 (0)2 49 216032
> FAX:   +61 (0)2 49 216993
>
> http://sigpromu.org/brett/
>
>
>
>
>
>
>
>



-- 
M. Sc. Juan Pablo Carbajal
-----
PhD Student
University of Zürich
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] GUI Preferences: Bug or feature?

[Jordi G. H. <jo...@oc...>]

On 11 September 2012 04:38, Thorsten Liebig <Tho...@gm...> wrote:
> I did some changes concerning the "Preferences" in the Octave GUI.

Hi, Thorsten. You're talking to the wrong list. This isn't the main
Octave development list, but the Octave-Forge list for package
maintenance (I know, I know, it's got a stupid name, which explains
your confusion).

Please use this instead:

    https://mailman.cae.wisc.edu/listinfo/octave-maintainers

- Jordi G. H.

Re: [OctDev] signed distance of point from polygon

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

On 11 Sep 2012, at 10:12, JuanPi wrote:

> Please go ahead!. Can you leave the original code commented at the end
> of the function? If you can't do not worry.
> Thank you!

OK, I committed the new version and left the old one as a comment.
c.

[OctDev] GUI Preferences: Bug or feature?

[Thorsten L. <Tho...@gm...>]

Hi,

I did some changes concerning the "Preferences" in the Octave GUI.

What I noticed is, that changes to the e.g. "Editor" Preferences would only affect newly opened editor tabs.

For example: Disabling line numbers, would not affect currently open tabs.

My question: Is this a desired effect. Because I would expect that if you change some preferences it would effect all editor tabs, already open and
new ones.

Changing this behavior would require quite some doing, the Settings Dialog would need to emit a signal, that changes have been made and all GUI
classes would need to have a new slot to receive this signal and eventually act on it.

I would be willing to look into it, but not if the current behavior is desired as it is. To me this looks like it should be changed...

regards
Thorsten

Re: [OctDev] signed distance of point from polygon

[JuanPi <aj...@gm...>]

On Tue, Sep 11, 2012 at 8:46 AM, c. <car...@gm...> wrote:
>
> On 10 Sep 2012, at 13:20, JuanPi wrote:
>
>> On Mon, Sep 10, 2012 at 1:01 PM, c. <car...@gm...> wrote:
>>> Hi,
>>>
>>> I need to compute the "signed distance" of a point P from a polygon Q,
>>> i.e., the distance of P from the polyline including Q with a "+" sign if
>>> the point is inside the polygon and a "-" sign if it is outside.
>>>
>>> I see "distancePointPolygon" in the geometry package computes the distance
>>> but always returns a positive number. Is there already a function to do
>>> what I need?
>>>
>>> If not, any idea where I can look-up the algorithm to modify "distancePointPolygon"
>>> according to my needs?
>>>
>>> Thanks,
>>> c.
>>
>> Hi,
>>
>> I would not modify the function, but use it together with inpolygon
>> (in the core geomtry package).
>>
>> I guess this is what you want
>> http://agora.octave.org/snippet/FRXH/
>>
>> Let me know
>
> I found that the function "distancePointPolyline" contains a for loop that can be easily vectorized away.
> As I work with a large number of points this has a strong impact on running time for me.
> Do you mind if I commit this patch?
> c.
>
> Index: inst/polygons2d/distancePointPolyline.m
> ===================================================================
> --- inst/polygons2d/distancePointPolyline.m     (revision 10796)
> +++ inst/polygons2d/distancePointPolyline.m     (working copy)
> @@ -1,5 +1,6 @@
> ## Copyright (C) 2003-2011 David Legland <dav...@gr...>
> ## Copyright (C) 2012 Adapted to Octave by Juan Pablo Carbajal <car...@if...>
> +## Copyright (C) 2012 Carlo de Falco (Speed up by vectorization)
> ## All rights reserved.
> ##
> ## Redistribution and use in source and binary forms, with or without
> @@ -51,17 +52,14 @@
>   # allocate memory for result
>   minDist = inf * ones(Np, 1);
>
> -  # process each point
> -  for p = 1:Np
> -      # construct the set of edges
> -      edges = [poly(1:end-1, :) poly(2:end, :)];
> +  ## construct the set of edges
> +  edges = [poly(1:end-1, :) poly(2:end, :)];
>
> -      # compute distance between current each point and all edges
> -      dist = distancePointEdge(point(p, :), edges);
> +  ## compute distance between current each point and all edges
> +  dist = distancePointEdge(point, edges);
>
> -      # update distance if necessary
> -      minDist(p) = min(dist);
> -  end
> +  ## update distance if necessary
> +  minDist = min(dist, [], 2);
>
>   # process output arguments
>   if nargout<=1
>
>

Please go ahead!. Can you leave the original code commented at the end
of the function? If you can't do not worry.
Thank you!

-- 
JuanPi Carbajal
-----
"The bad economist pursues a small present good, which will be
followed by a great evil to come, while the true economist pursues a
great good to come, at the risk of a small present evil." - Frédéric
Bastiat
-----
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] signed distance of point from polygon

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

On 10 Sep 2012, at 13:20, JuanPi wrote:

> On Mon, Sep 10, 2012 at 1:01 PM, c. <car...@gm...> wrote:
>> Hi,
>> 
>> I need to compute the "signed distance" of a point P from a polygon Q,
>> i.e., the distance of P from the polyline including Q with a "+" sign if
>> the point is inside the polygon and a "-" sign if it is outside.
>> 
>> I see "distancePointPolygon" in the geometry package computes the distance
>> but always returns a positive number. Is there already a function to do
>> what I need?
>> 
>> If not, any idea where I can look-up the algorithm to modify "distancePointPolygon"
>> according to my needs?
>> 
>> Thanks,
>> c.
> 
> Hi,
> 
> I would not modify the function, but use it together with inpolygon
> (in the core geomtry package).
> 
> I guess this is what you want
> http://agora.octave.org/snippet/FRXH/
> 
> Let me know

I found that the function "distancePointPolyline" contains a for loop that can be easily vectorized away.
As I work with a large number of points this has a strong impact on running time for me.
Do you mind if I commit this patch?
c.

Index: inst/polygons2d/distancePointPolyline.m
===================================================================
--- inst/polygons2d/distancePointPolyline.m	(revision 10796)
+++ inst/polygons2d/distancePointPolyline.m	(working copy)
@@ -1,5 +1,6 @@
## Copyright (C) 2003-2011 David Legland <dav...@gr...>
## Copyright (C) 2012 Adapted to Octave by Juan Pablo Carbajal <car...@if...>
+## Copyright (C) 2012 Carlo de Falco (Speed up by vectorization)
## All rights reserved.
##
## Redistribution and use in source and binary forms, with or without
@@ -51,17 +52,14 @@
  # allocate memory for result
  minDist = inf * ones(Np, 1);

-  # process each point
-  for p = 1:Np
-      # construct the set of edges
-      edges = [poly(1:end-1, :) poly(2:end, :)];
+  ## construct the set of edges
+  edges = [poly(1:end-1, :) poly(2:end, :)];

-      # compute distance between current each point and all edges
-      dist = distancePointEdge(point(p, :), edges);
+  ## compute distance between current each point and all edges
+  dist = distancePointEdge(point, edges);

-      # update distance if necessary
-      minDist(p) = min(dist);
-  end
+  ## update distance if necessary
+  minDist = min(dist, [], 2);

  # process output arguments
  if nargout<=1

Re: [OctDev] Ode23s

[davide p. <dav...@ho...>]

Hi everyone, I've loaded on Sourceforge a new version of ode23s.m file, with some updates. I hope that someone will control and test it.
http://sourceforge.net/tracker/?func=detail&aid=3565098&group_id=2888&atid=352888

Regards,Davide 		 	   		  

Re: [OctDev] GNU Octave: FAST RECOGNITION OF OBJECTS

[Juan P. C. <car...@if...>]

2012/9/10 Laura Gelsi <lau...@ya...>:
> Estimado Juan Pablo Carabajal;
>
>
>
>
>
>
>
> Es un placer ponerme en contacto con Usted, actualmente estamos optimizando
> el algoritmo y estará disponible (software abierto) hacia fin de año.
>
>
>  Si aun está interesado nos ponemos nuevamente en contacto.
> Un cordial saludo, y perdón por la demora.
> Ing. Laura Gelsi
>
>
> ----- Mensaje reenviado -----
> De: Juan Pablo Carbajal <car...@if...>
> Para: lau...@ya...
> CC: Octave Forge <oct...@li...>
> Enviado: lunes, 3 de septiembre de 2012 11:39
> Asunto: GNU Octave: FAST RECOGNITION OF OBJECTS
>
> Estimada Ing. Laura Gelsi,
>
> Mi nombre es Juan Pablo Carbajal, colaboro en el desarrollo del
> programa libre para analisis numérico GNU Octave
> (http://www.gnu.org/software/octave/ altamente compatible con Matlab y
> con la misma sintaxis). He leido su articulo RECONOCIMIENTO RÁPIDO DE
> OBJETOS
> (http://anales.fisica.org.ar/journal/index.php/analesafa/article/view/22),
> publicado en los anales de la AFA este año. Me gustaría saber si el
> código se encuentra disponible bajo alguna licencia libre
> (http://es.wikipedia.org/wiki/Anexo:Licencias_de_software_aprobadas_por_la_FSF).
> Si ese es el caso me gustaría agregarlo al paquete "image" de GNU
> Octave (http://octave.sourceforge.net/image/overview.html). De esta
> manera su código (que conservará su autoría) será obtenible a través
> de la internet (Muchas distribuciones de linux incluyen los paquetes
> de GNU Octzave, ejemplo: Debian, Fedora, etc) y a través de la linea
> de comando de GNU Octave.
>
> Espero que comprenda la importancia de compartir el código cientifico
> de manera que sea accesible para todos (es decir, que no depdenda de
> software pago para su utilización).
>
> Desde ya le agradezco su articulo y su colaboración
>
> Atentamente,
>
> --
> M. Sc. Juan Pablo Carbajal
> -----
> PhD Student
> University of Zürich
> http://ailab.ifi.uzh.ch/carbajal/
>
>
>
>

Estimada Laura Gelsi,

Desde ya le comunico mi interés (y el de la comunidad de GNU Octave)
en su código. Por favor no se olvide de notificarnos cuanod el código
est disponible.

Muchas gracias en anticipación.


-- 
M. Sc. Juan Pablo Carbajal
-----
PhD Student
University of Zürich
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] GNU Octave: FAST RECOGNITION OF OBJECTS

[Laura G. <lau...@ya...>]

Estimado Juan Pablo Carabajal;
 
 
 
 
 
 
 
Es un placer ponerme en contacto con Usted, actualmente estamos optimizando el algoritmo y estará disponible (software abierto) hacia fin de año.
 
 
 Si aun está interesado nos ponemos nuevamente en contacto.
Un cordial saludo, y perdón por la demora.
Ing. Laura Gelsi
 


----- Mensaje reenviado -----
De: Juan Pablo Carbajal <car...@if...>
Para: lau...@ya... 
CC: Octave Forge <oct...@li...> 
Enviado: lunes, 3 de septiembre de 2012 11:39
Asunto: GNU Octave: FAST RECOGNITION OF OBJECTS

Estimada Ing. Laura Gelsi,

Mi nombre es Juan Pablo Carbajal, colaboro en el desarrollo del
programa libre para analisis numérico GNU Octave
(http://www.gnu.org/software/octave/ altamente compatible con Matlab y
con la misma sintaxis). He leido su articulo RECONOCIMIENTO RÁPIDO DE
OBJETOS (http://anales.fisica.org.ar/journal/index.php/analesafa/article/view/22),
publicado en los anales de la AFA este año. Me gustaría saber si el
código se encuentra disponible bajo alguna licencia libre
(http://es.wikipedia.org/wiki/Anexo:Licencias_de_software_aprobadas_por_la_FSF).
Si ese es el caso me gustaría agregarlo al paquete "image" de GNU
Octave (http://octave.sourceforge.net/image/overview.html). De esta
manera su código (que conservará su autoría) será obtenible a través
de la internet (Muchas distribuciones de linux incluyen los paquetes
de GNU Octzave, ejemplo: Debian, Fedora, etc) y a través de la linea
de comando de GNU Octave.

Espero que comprenda la importancia de compartir el código cientifico
de manera que sea accesible para todos (es decir, que no depdenda de
software pago para su utilización).

Desde ya le agradezco su articulo y su colaboración

Atentamente,

-- 
M. Sc. Juan Pablo Carbajal
-----
PhD Student
University of Zürich
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] signed distance of point from polygon

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

On 10 Sep 2012, at 13:20, JuanPi wrote:

> On Mon, Sep 10, 2012 at 1:01 PM, c. <car...@gm...> wrote:
>> Hi,
>> 
>> I need to compute the "signed distance" of a point P from a polygon Q,
>> i.e., the distance of P from the polyline including Q with a "+" sign if
>> the point is inside the polygon and a "-" sign if it is outside.
>> 
>> I see "distancePointPolygon" in the geometry package computes the distance
>> but always returns a positive number. Is there already a function to do
>> what I need?
>> 
>> If not, any idea where I can look-up the algorithm to modify "distancePointPolygon"
>> according to my needs?
>> 
>> Thanks,
>> c.
> 
> Hi,
> 
> I would not modify the function, but use it together with inpolygon
> (in the core geomtry package).
> 
> I guess this is what you want
> http://agora.octave.org/snippet/FRXH/
> 
> Let me know

Yes,
I had already answered my own qeustion seconds after I posted it ;)
Cool to see that snippets are working on the new Agora though ...
c.

Re: [OctDev] signed distance of point from polygon

[JuanPi <aj...@gm...>]

On Mon, Sep 10, 2012 at 1:01 PM, c. <car...@gm...> wrote:
> Hi,
>
> I need to compute the "signed distance" of a point P from a polygon Q,
> i.e., the distance of P from the polyline including Q with a "+" sign if
> the point is inside the polygon and a "-" sign if it is outside.
>
> I see "distancePointPolygon" in the geometry package computes the distance
> but always returns a positive number. Is there already a function to do
> what I need?
>
> If not, any idea where I can look-up the algorithm to modify "distancePointPolygon"
> according to my needs?
>
> Thanks,
> c.

Hi,

I would not modify the function, but use it together with inpolygon
(in the core geomtry package).

I guess this is what you want
http://agora.octave.org/snippet/FRXH/

Let me know



-- 
JuanPi Carbajal
-----
"The bad economist pursues a small present good, which will be
followed by a great evil to come, while the true economist pursues a
great good to come, at the risk of a small present evil." - Frédéric
Bastiat
-----
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] signed distance of point from polygon

[c. <kin...@ti...>]

On 10 Sep 2012, at 13:01, c. wrote:

> Hi,
> 
> I need to compute the "signed distance" of a point P from a polygon Q,
> i.e., the distance of P from the polyline including Q with a "+" sign if
> the point is inside the polygon and a "-" sign if it is outside.
> 
> I see "distancePointPolygon" in the geometry package computes the distance
> but always returns a positive number. Is there already a function to do 
> what I need?
> 
> If not, any idea where I can look-up the algorithm to modify "distancePointPolygon"
> according to my needs?
> 
> Thanks,
> c.

To answer my own question, I just found the built-in function "inpolygon" that checks whether a point is inside or outside a polygon.
Sorry for the noise.
c.

[OctDev] signed distance of point from polygon

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

Hi,

I need to compute the "signed distance" of a point P from a polygon Q,
i.e., the distance of P from the polyline including Q with a "+" sign if
the point is inside the polygon and a "-" sign if it is outside.

I see "distancePointPolygon" in the geometry package computes the distance
but always returns a positive number. Is there already a function to do 
what I need?

If not, any idea where I can look-up the algorithm to modify "distancePointPolygon"
according to my needs?

Thanks,
c.

Re: [OctDev] No isimag() curioso

[Daniel J S. <dan...@ie...>]

On 09/08/2012 08:52 PM, Michael D Godfrey wrote:

[snip]

> And, this may just add to the noise, but a few days ago I created a
> vector which was composed
> of complex elements, and some "real" elements, i.e. isreal(x(4)) said 1
> and whos x(4) said
> it was only 8 bytes.

That is similar to the example:

octave:20> z = complex([1 2 3],[1 0 2])
z =

    1 + 1i   2 + 0i   3 + 2i

octave:21> isreal(z)
ans = 0
octave:22> isreal(z(1))
ans = 0
octave:23> isreal(z(2))
ans =  1
octave:24> whos z z(1) z(2)
Variables in the current scope:

    Attr Name        Size                     Bytes  Class
    ==== ====        ====                     =====  =====
    c    z           1x3                         48  double
    c    z(1)        1x1                         16  double
         z(2)        1x1                          8  double

Total is 5 elements using 72 bytes

...

Interchanging the square and curved parentheses is another, simpler 
illustration:

octave:28> iscomplex(complex(1,0))
ans =  1
octave:29> iscomplex([complex(1,0)])
ans = 0

Dan

Re: [OctDev] No isimag() curioso

[Michael D G. <mic...@gm...>]

On 09/08/2012 05:33 PM, Daniel J Sebald wrote:
> How do others feel about deprecating "iscomplex()" if it simply is the 
> complement of "isreal()"?
>
> I would be open to an "iscomplex" and "isimag" that have a more 
> "class-related" behavior as I pondered above.  I don't think that 
> would go against compatibility.
>
> I'm also wondering if it might be worth writing in the documentation 
> for isreal() that "isreal(x) is not the same as all(imag(x)==0)".
>
> Dan 
Dan,

Just a brief answer to all you comments.  It seems to me that the 
current state has just
evolved from various forces.  It is not either consistent nor likely to 
be clear to most
users.  Maybe its only good feature is that it is not obviously in 
direct conflict with Matlab.
However, I think that any single change, without carefully thinking 
through all the issues,
is likely to do as much harm as good.

One thing that you said should be followed up: a clearer description of 
the current state
should go somewhere in the Manual.

And, this may just add to the noise, but a few days ago I created a 
vector which was composed
of complex elements, and some "real" elements, i.e. isreal(x(4)) said 1 
and whos x(4) said
it was only 8 bytes.  But, the vector was complex and whos x showed it 
as composed of 16 byte
complex elements.  Just another bit of schizophrenia.   Since I have not 
been able to
reproduce this I have not been able to try it on Matlab.

I do think that creating an isimag() and at least deprecating 
iscomplex() is a good idea.

However, someone with at least a day or two of time should go through 
this carefully and propose
a good set of actions.

Michael

Re: [OctDev] No isimag() curioso

[Daniel J S. <dan...@ie...>]

On 09/07/2012 11:05 PM, Michael D Godfrey wrote:
> On 09/07/2012 05:30 PM, Daniel J Sebald wrote:
>> In working with the fftfilt() routine and wanting to know if the
>> inputs were purely imaginary I wondered why there is no such thing as
>> isimag(). It seems as though it would be as useful as or more useful
>> than iscomplex().
>>
>> Here's the thing: iscomplex() appears to be simply the complement of
>> isreal(), unless I'm missing a more sophisticated use of syntax:
>>
>> octave:5> x = 1
>> x = 1
>> octave:6> [isreal(x) iscomplex(x)]
>> ans =
>>
>> 1 0
>>
>> octave:7> x = i
>> x = 0 + 1i
>> octave:8> [isreal(x) iscomplex(x)]
>> ans =
>>
>> 0 1
>>
>> octave:9> x = 1+i
>> x = 1 + 1i
>> octave:10> [isreal(x) iscomplex(x)]
>> ans =
>>
>> 0 1
>>
>> octave:11>
>>
>> I ask, What's the point of having a function that is simply !isreal()?
>> On the other hand isimag(), which is equivalent to "all (real (x) ==
>> 0)) && !isreal (x)", would be a nice shorthand.
>>
>> Just an observation. Usually duplication of function (or its
>> complement) is weeded out of programming languages.
>>
>> Dan
> I also recently noticed some quirks with complex:
> x = 1 + 0i is treated as real and not complex.
> but
> x = 0 + 1i is treated as imag and complex.

Talking of Octave, there is no "isimag()", so what do you mean "treated 
as imag"?


> But, this is consistent with Matlab. However, Matlab has no iscomplex
> and also
> differs in its example for help isreal. There, Matlab gives an example:
> x = magic(3);
> y = complex(x);
>
> which gives:
>> > y
>
> y =
>
> 8 1 6
> 3 5 7
> 4 9 2
>> > isreal(y)
>
> ans =
>
> 0
> but, ~isreal(y) gives:
> ans =
>
> 1
>
> The text in the help messages says that
> isreal(y) returns
> false, because COMPLEX returns y with an all zero imaginary
> part.
> -------------------------------------------
> but Octave gives:
>
> y =
>
> 8 + 0i 1 + 0i 6 + 0i
> 3 + 0i 5 + 0i 7 + 0i
> 4 + 0i 9 + 0i 2 + 0i
>
> and:
> octave:21> isreal(y)
> ans = 0
> and:
> octave:29> ~isreal(y)
> ans = 1
>
> The only difference is in the display of y.

Well, if y is complex, I sort of prefer the Octave printout format.


> This hardly qualifies as a bug, but does add a bit
> to the confusion.

Add to, yes.  Meaning it is already somewhat confusing by the Matlab 
standard.


>  Some people would imagine
> that real and imaginary would be treated "symmetrically."

I guess that is what I would prefer.  For example

PREFERRED, NOT CURRENT BEHAVIOR:

octave:29> x = 1
x =  1
octave:30> isreal(x)
ans =  1
octave:31> isimag(x)
ans =  0
octave:32> iscomplex(x)
ans = 0
octave:33> y = i
y =  1i
octave:34> isreal(y)
ans = 0
octave:35> isimag(y)
ans =  1
octave:36> iscomplex(y)
ans =  0
octave:37> z = 1 + i
z =  1 + 1i
octave:38> isreal(z)
ans = 0
octave:39> isimag(z)
ans = 0
octave:40> iscomplex(z)
ans =  1

The above scenario seems to me consistent and all three functions would 
be "orthogonal", i.e., not duplicate function or simple complement.  If 
one were to mix-and-match real and imaginary, I'd think that promoting 
to "complex" in that case would make sense.

...

Just trying a few things here, I've sort of lost my faith in the meaning 
of "isreal()".  Generally speaking, it could mean:

1) The class of the variable is real, meaning there is no imaginary 
component present.
2) The variable has no imaginary component, or it does have an imaginary 
component which is zero.

Unfortunately by having the property you describe above, i.e., "complex 
returns an all zero imaginary part", the two are sort of conflated.

Consider for example if I want to test if the imaginary portion of some 
variable is zero:

octave:41> isreal(1 + 0i)
ans =  1
octave:42> isreal(complex(1,0))
ans = 0

Well, "isreal()" clearly doesn't mean that.  I just put together a patch 
for fftfilt() that intends to check if the imaginary component of the 
inputs are zero using "isreal()", but I think I will change that to 
all(imag(x) == 0)) instead because the latter expression has clear 
definition.

One could be lead to think that "isreal" DOES mean the imaginary portion 
is zero.  Check this out:

octave:50> z = complex([1 2 3],[1 0 2])
z =

    1 + 1i   2 + 0i   3 + 2i

octave:51> isreal(z(2))
ans =  1
octave:52> iscomplex(z(2))
ans = 0

Perhaps the above is a compatibility disagreement.  Otherwise it is a 
little confounding.  Conceptually, I can grasp either scenario 1 or 
scenario 2 above, but there seems to be a hybrid that escapes me.

How do others feel about deprecating "iscomplex()" if it simply is the 
complement of "isreal()"?

I would be open to an "iscomplex" and "isimag" that have a more 
"class-related" behavior as I pondered above.  I don't think that would 
go against compatibility.

I'm also wondering if it might be worth writing in the documentation for 
isreal() that "isreal(x) is not the same as all(imag(x)==0)".

Dan

[OctDev] queueing 1.1.1 released

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

Hi everyone

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

Carnë

[OctDev] Cannot upload package queueing to tracker

[Moreno M. <mo...@mo...>]

Hello,

I can not upload a new version of the queueing package to the tracker, 
since both the package and the documentation are larger than 256k each.
I have put the tarballs on my web site; if there is a different 
procedure to handle this situation please tell me.

http://www.moreno.marzolla.name/software/queueing/queueing-1.1.1.tar.gz
http://www.moreno.marzolla.name/software/queueing/queueing-html.tar.gz

MD5 checksums follow:

1bfea9b4bf00b269ab9f43303e20ab9c  queueing-1.1.1.tar.gz
bca21866b0b7f8e8b7c7c6e7c3fedebf  queueing-html.tar.gz

Version 1.1.1 fixes some errors raised by the embedded test blocks.

Regards,

Moreno.

-- 
Moreno Marzolla
EMail: mo...@mo...
WWW  : http://www.moreno.marzolla.name/