octave-dev — GNU Octave developers' list

Re: [OctDev] DPCM

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

On 4 October 2012 18:03, LEo <le...@gm...> wrote:
> I have implemented the following function:
> dpcmenco, dpcmdeco and dpcmopt
> They were not implement yet.
> (see: http://octave.sourceforge.net/communications/overview.html)
> I would like share it, so it might be incorporated into Octave-Forge.
> They follow in the attachment. An usage example follows along it.
> If someone could include them into Octave-Forge tree, I would be pleased.
> Regards,
> Leonardo Araujo

I have added them and made the following changes:
  * use of @seealso macro for help text (instead of literal text)
  * license to GPLv3+
  * indentaton issues
  * closed function blocks with endfunction
  * replaced usage by print_usage
  * replaced @var{...} by @dots{}

We cannot use your examples since you copied them from matlab
documentation and they might have intellectual property on them...

Could you please submit a patch to add a test or a demo block to these
functions?

Carnë

[OctDev] DPCM

[LEo <le...@gm...>]

I have implemented the following function:
dpcmenco, dpcmdeco and dpcmopt
They were not implement yet.
(see: http://octave.sourceforge.net/communications/overview.html)
I would like share it, so it might be incorporated into Octave-Forge.
They follow in the attachment. An usage example follows along it.
If someone could include them into Octave-Forge tree, I would be pleased.
Regards,
Leonardo Araujo

Re: [OctDev] xlread in 3.6.1

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

Swift, Ted J. wrote:
>
>
>
>
> -----Original Message-----
> From: Philip Nienhuis [mailto:pr....@hc...]
> Sent: Wednesday, September 26, 2012 12:16 AM
> To: Swift, Ted J.
> Cc: hel...@oc...
> Subject: Re: [OctDev] xlread in 3.6.1
>>
> <snip>
>>
>> Swift, Ted J. wrote:
>>> -----Original Message-----
>>> From: prn...@us... [mailto:prn...@us...]
>>> Sent: Thursday, September 13, 2012 1:41 AM
>>> To: Swift, Ted J.
>>> Subject: FWD: Re: [OctDev] xlread in 3.6.1
>>>
>>> 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_s
>>>>> preadsheet_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/ext
>>> ra/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_environme
>>> nt_is_configured_properly
>>> (line wrap!)
>>   >
>>   >  Philip,
>>   >  Thank you very much for the advice and pointers. And sorry for the>  delay in replying; I was busy last week being part of the>  organizing team for a scientific conference.
>>   >  Thanks for writing pre_install.m. I downloaded it and tried it,>  but it didn't provide any new insight: It did not return any errors.
>>   >  However, after I ran pre_install, I immediately ran>  chk_spreadsheet_support, and received the same error I've received>  before. Here's the transcript:
>>   >
>>   >>  GNU Octave, version 3.6.1
>> <snip>
>>   >>  octave:1>   pwd
>>   >>  ans = C:\Users\tswift
>>   >>  octave:2>   run pre_install.m                    %<--------- NOTE: No
>>   >>  error returned
>>
>> You should have just typed:
>>
>> preinstall
>>
>> and watch the output. No "run", no ".m" suffix. Just:
>> preinstall
>>
>> Note: scripts and function files seem to run better if invoked with just their file name w/o suffix.
>>
>> Philip
>
>   --------
> Hello again, Philip,
> I'm going back to the basics and taking a close look at
> http://wiki.octave.org/Java_package#Make_sure_that_the_build_environment_is_configured_properly
>
> I looked for where the JDK was installed and it is in (recall this is in Windows 7; sorry)
>
> C:\Program Files (x86)\Java\jdk1.7.0_05
>
> After setting the environment in octaverc:
>
>> setenv('JAVA_HOME','C:/Program Files (x86)/Java/jdk1.7.0_05');
>
> I launched Octave again, and invoked pre_install again. This time it returned silently, no errors.:
>
>> octave:1>  pwd
>> ans = C:\Users\tswift
>> octave:2>  pre_install
>> octave:3>  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
>> octave:3>  system ('javac -version 2>  nul')
>> ans =  1
>> octave:4>  system ('javac -version 2>  null')
>> ans =  1
>> octave:5>
>
>
> In the file 'null' is the message:
>> 'javac' is not recognized as an internal or external command,
>> operable program or batch file.
>
> There is a javac in the /bin subdirectory, however.
> Any thoughts? Thank you.

Please keep list cc'd

Yes; clearly javac isn't in the PATH. Which makes sense as on Windows 
systems, the <JDK>/bin directory is usually not in the PATH, unlike *nix 
systems where there are usually symlinks to java, javac and jar in /usr/bin

Apparently the relevant statements in preinstall.m that should fix this 
don't work properly.
So what you can do, in Octave, is (after setting JAVA_HOME):

  setenv ("PATH", [getenv('PATH') pathsep '/full/path/to/JDK/bin'])

(single quotes) where I suppose (but please check) that 
'/full/path/to/JDK/bin' boils down to
'C:/Program Files (x86)/Java/jdk1.7.0_05/bin'
and then again try to install the Java package.
If it doesn't work, try again with backslashes instead of forward slashes.

If none of this works I'm out of ideas.

Philip

[OctDev] Invalid path specification in math.h

[Magne S. <mag...@ce...>]

Hi,

When using mkoctfile.exe to compile an Octave plugin for VS2010 32-bit causes the following error.

D:\Octave\Octave-3.6.2\include\math.h(74): fatal error C1083: Cannot open include file: 'c:/Program Files/Microsoft Visual Studio 10.0/VC/include/math.h': No such file or directory

The same compilation works successfully using Octave 3.6.1.

Regards,

Magne Sjaastad                       Phone:  +47 73 54 61 50
Senior Software Engineer             Fax:    +47 73 54 61 44
Ceetron ASA (http://www.ceetron.com) Direct: +47 73 54 61 37
P.O. Box 1247, Pirsenteret           Mob:    +47 98 60 78 38
7462 Trondheim, NORWAY               E-mail: mag...@ce...<mailto:mag...@ce...>

Re: [OctDev] Analyze75

[adam a. <ada...@ho...>]

> From: car...@gm...
> Date: Tue, 2 Oct 2012 11:42:25 +0200
> Subject: Re: [OctDev] Analyze75
> To: ada...@ho...
> CC: oct...@li...
> 
> On 2 October 2012 11:11, adam aitkenhead <ada...@ho...> wrote:
> >> From: car...@gm...
> >> Date: Tue, 2 Oct 2012 09:33:17 +0200
> >> Subject: Re: [OctDev] Analyze75
> >> To: ada...@ho...
> >> CC: oct...@li...
> >>
> >> On 1 October 2012 22:30, adam aitkenhead <ada...@ho...>
> >> wrote:
> >> > I've just submitted analyze75write.m to SVN.
> >>
> >> Nice, thank you. The code looks nice. I have added the function to the
> >> INDEX and NEWS file, and to the see also of the other functions.
> >>
> >> Some tips, you don't need to check the value returned by isfield. If
> >> there is a field with that name, it will return true so "if (isfield
> >> (x, name))" is enough, no need to "if (isfield (x, name) == 1).
> >>
> >> It would be good practice to also have analyze75filename deal with the
> >> filename part, just as it's doing for the other 2 functions. I'd guess
> >> analyze75filename would take an extra argument ("write", "info" or
> >> "read") for the part of checking if the file already exists. This
> >> would also allow to make it return the right error message with:
> >>
> >> error ('analyze75%s: error message.', analyze75function)
> >>
> >> Carnë
> >
> > Those suggestions sound good, I can make those changes although I probably
> > won't have time before the weekend. If you're ready for the release of the
> > image package then don't wait, as it won't affect functionality.
> 
> Not yet. There's some warnings and error messages for Mac users that
> should be fixed before.
> 
> Carnë
 
Hi Carnë

I submitted a couple of changes to analyze75read and analyze75write last night to allow them to work properly for int16 and int32 images.  Still to do the other updates to analyze75write though.
 
Adam
 		 	   		  

Re: [OctDev] [PKG] lssa

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

On Thu, Oct 4, 2012 at 5:03 AM, Benjamin Lewis <be...@gm...> wrote:
> Le 2012-10-03 à 09:39, JuanPi <aj...@gm...> a écrit :
>
>> On Wed, Oct 3, 2012 at 3:14 PM, Benjamin Lewis <be...@gm...> wrote:
>>> Le 2012-10-03 à 05:41, JuanPi <aj...@gm...> a écrit :
>>>
>>>> Hi there,
>>>>
>>>> I am exploring the lssa package, looks really handy. however I am
>>>> finding difficult to understand the use.
>>>>
>>>> I started testing lsreal and the last three input arguments are a
>>>> little puzzling ( MAXFREQ, NUMCOEFF, NUMOCTAVES).
>>>> Questions:
>>>>
>>>> - Can't this arguments be estimated form the data by default and given
>>>> as optional in case the user wants some specifics?
>>>> - Is there an example of use of the function? A demo would be very very handy.
>>>> - The doc string should contain a minimum explanation of what is
>>>> maxfreq (at least in what units should be given (rad/s? Hz? normalized
>>>> as in butter?), numcoef (i expected the result to be this length, but
>>>> octave I was wrong), numoctaves.
>>>>
>>>> If I get the grip of these functions I can help writing demos.
>>>>
>>>> Thank you very much for your support.
>>>>
>>>
>>> Hey;
>>>
>>> Thank you for trying out lssa. Some background on the functions is in order to explain the arguments you're wondering about, I think:
>>>
>>> The ls* functions in the lssa package implement the Lomb-Scargle transform, which is a non-invertible transform which tests independent frequencies against the provided data set; its operations expect radian input, but beyond that, the MAXFREQ term is essentially rad/(pick the unit that matches from your data). The transform (in the case of lsreal and lscomplex) operates over NUMOCTAVES octaves, testing NUMCOEFFS evenly-spaced frequencies per octave. I've got a demo in the works on Octave-Forge, I'll put some time into expanding it, and once it's ready I'll prepare another release of the package together (although it does feature an application of the functions, it doesn't use all of them yet, I don't think.)
>>>
>>> In response to the first question, then, I don't think the arguments can really be estimated without possibly running the function first; I'd be happy to get some input on that, though.
>>>
>>> Thanks for your feedback on the package!
>>>
>>> Ben
>>
>> Hi Ben,
>>
>> NUMCOEFF (which from your explanations is more like NUMFREQS. Also
>> NUMCOEFF is not happy cause the values of the transform are called
>> coefficients... according to my sources! So it seems NUMCOEFF is the
>> size of the output of the function...which is not). This is a free
>> parameter, I agree and the user must provide it, though it could still
>> have a default value, let say 10 (or whatever).
>>
>> Can't the MAXFREQ parameter be estimated form the smallest time
>> interval? something like
>> maxFreq = pi/min(diff(t))
>> Also the minimum frequncy could be minFreq = pi/(t(1)-t(end))
>>
>> If it can be done, then you could get NUMOCTAVES (again an octave is
>> not that well defined, I assume you mean halving or doubling the
>> frequencies) as
>> numoctaves = round (log (maxFreq/minFreq) / log (2))
>>
>> What do you think?
>>
>
> Hi JuanPi,
>
> A lot of the naming conventions have resulted from following the original code, which was written in a combination of R and C code; I'm thinking this was a mistake in a few areas, and I agree with renaming NUMCOEFF to NUMFREQS. I'm leery of giving it a default parameter, but 10 makes sense. (Possibly more, though; in the data set I was working with for testing, I regularly used 100 frequencies/octave.)
>
> The NUMOCTAVES concept is drawn directly from the musical idea; a doubling/halving of the frequencies. I would probably say that 10 could again be used as a starting value for this, but it depends greatly on the data set involved. I'm not sure imposing a minimum frequency is a good idea, especially not to maintain compatibility with the original code that was used as a basis for implementing this package.
>
> On the other hand, I do agree with your choice for an estimated default MAXFREQ value.
>
> I'll try out these changes tomorrow morning.
>
> Ben

Hi Ben,

The minimum freq is not an imposition, it is just a value you
calculate to be able to estimate a reasonable number of octaves. For
the calculation I gave I was assuming that maxFreq gets dividide
succesively by 2 untill you reach minFreq. It is just an estimation to
get a reasonable value nothing more.

We should made a Wiki entry discusing all the knowledge you have gain
and showcasing the package in a not uniformly sampled data (I have
some visual tracking data which is highly non regularly sampled) vs
interpolation+FFT.

Looking forward to testing more of your package, really interesting!

JPi


-- 
JuanPi Carbajal
-----
"It is one thing not to be able to perform a certain feat, but quite
another to prove that it cannot be done." - Henry Ernest Dudeney
-----
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] [PKG] lssa

[Benjamin L. <be...@gm...>]

Le 2012-10-03 à 09:39, JuanPi <aj...@gm...> a écrit :

> On Wed, Oct 3, 2012 at 3:14 PM, Benjamin Lewis <be...@gm...> wrote:
>> Le 2012-10-03 à 05:41, JuanPi <aj...@gm...> a écrit :
>> 
>>> Hi there,
>>> 
>>> I am exploring the lssa package, looks really handy. however I am
>>> finding difficult to understand the use.
>>> 
>>> I started testing lsreal and the last three input arguments are a
>>> little puzzling ( MAXFREQ, NUMCOEFF, NUMOCTAVES).
>>> Questions:
>>> 
>>> - Can't this arguments be estimated form the data by default and given
>>> as optional in case the user wants some specifics?
>>> - Is there an example of use of the function? A demo would be very very handy.
>>> - The doc string should contain a minimum explanation of what is
>>> maxfreq (at least in what units should be given (rad/s? Hz? normalized
>>> as in butter?), numcoef (i expected the result to be this length, but
>>> octave I was wrong), numoctaves.
>>> 
>>> If I get the grip of these functions I can help writing demos.
>>> 
>>> Thank you very much for your support.
>>> 
>> 
>> Hey;
>> 
>> Thank you for trying out lssa. Some background on the functions is in order to explain the arguments you're wondering about, I think:
>> 
>> The ls* functions in the lssa package implement the Lomb-Scargle transform, which is a non-invertible transform which tests independent frequencies against the provided data set; its operations expect radian input, but beyond that, the MAXFREQ term is essentially rad/(pick the unit that matches from your data). The transform (in the case of lsreal and lscomplex) operates over NUMOCTAVES octaves, testing NUMCOEFFS evenly-spaced frequencies per octave. I've got a demo in the works on Octave-Forge, I'll put some time into expanding it, and once it's ready I'll prepare another release of the package together (although it does feature an application of the functions, it doesn't use all of them yet, I don't think.)
>> 
>> In response to the first question, then, I don't think the arguments can really be estimated without possibly running the function first; I'd be happy to get some input on that, though.
>> 
>> Thanks for your feedback on the package!
>> 
>> Ben
> 
> Hi Ben,
> 
> NUMCOEFF (which from your explanations is more like NUMFREQS. Also
> NUMCOEFF is not happy cause the values of the transform are called
> coefficients... according to my sources! So it seems NUMCOEFF is the
> size of the output of the function...which is not). This is a free
> parameter, I agree and the user must provide it, though it could still
> have a default value, let say 10 (or whatever).
> 
> Can't the MAXFREQ parameter be estimated form the smallest time
> interval? something like
> maxFreq = pi/min(diff(t))
> Also the minimum frequncy could be minFreq = pi/(t(1)-t(end))
> 
> If it can be done, then you could get NUMOCTAVES (again an octave is
> not that well defined, I assume you mean halving or doubling the
> frequencies) as
> numoctaves = round (log (maxFreq/minFreq) / log (2))
> 
> What do you think?
> 

Hi JuanPi,

A lot of the naming conventions have resulted from following the original code, which was written in a combination of R and C code; I'm thinking this was a mistake in a few areas, and I agree with renaming NUMCOEFF to NUMFREQS. I'm leery of giving it a default parameter, but 10 makes sense. (Possibly more, though; in the data set I was working with for testing, I regularly used 100 frequencies/octave.)

The NUMOCTAVES concept is drawn directly from the musical idea; a doubling/halving of the frequencies. I would probably say that 10 could again be used as a starting value for this, but it depends greatly on the data set involved. I'm not sure imposing a minimum frequency is a good idea, especially not to maintain compatibility with the original code that was used as a basis for implementing this package.

On the other hand, I do agree with your choice for an estimated default MAXFREQ value.

I'll try out these changes tomorrow morning.

Ben

Re: [OctDev] Code sprint: pkg.m

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

On Wed, Oct 3, 2012 at 10:37 PM, Sergei Steshenko <ser...@ya...> wrote:
>
>
>
>
> ----- Original Message -----
>> From: JuanPi <aj...@gm...>
>> To: Octave Forge <oct...@li...>; hel...@oc...; Octave Maintainers <oct...@oc...>
>> Cc:
>> Sent: Wednesday, October 3, 2012 3:25 PM
>> Subject: Code sprint: pkg.m
>>
>> Hi all,
>>
>> I created a doodle for November. The objective is to evaluate how many
>> people are joining the code sprint
>> (http://wiki.octave.org/Code_sprint:_pkg.m) and on what days we should
>> concentrate the activity.
>>
>> http://www.doodle.com/x3bh7ity5knekda8
>>
>> Thank you for filling the poll
>>
>> --
>> JuanPi Carbajal
>> -----
>> "It is one thing not to be able to perform a certain feat, but quite
>> another to prove that it cannot be done." - Henry Ernest Dudeney
>> -----
>> http://ailab.ifi.uzh.ch/carbajal/
>> _______________________________________________
>> Help-octave mailing list
>> Hel...@oc...
>> https://mailman.cae.wisc.edu/listinfo/help-octave
>>
>
> Is there a _spec_ for 'pkg.m' ? I have my own version, which is still broken, but less - at least, for me.
>
> Looking into the code and playing with it I've come to the conclusion that _conceptually_ package management in Octave is not well defined, that's why I'm asking: is there a _functional_ spec telling what 'pkg.m' has to do ?
>
> ...
>
> Looking at http://wiki.octave.org/Code_sprint:_pkg.m :
>
> "Remove -global and -local flags
>         * Those flags are currently ignored internally anyways so they should disappear "
>
> - huh ?
>
> They are not ignored, and packages are installed into different locations.
>
> Thanks,
>   Sergei.
>

Sergei,

I do not know of functional specification for pkg.m. Maybe you can
contribute with one or maybe you can join us!

I amended the wiki.


-- 
JuanPi Carbajal
-----
"It is one thing not to be able to perform a certain feat, but quite
another to prove that it cannot be done." - Henry Ernest Dudeney
-----
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] Code sprint: pkg.m

[Sergei S. <ser...@ya...>]

----- Original Message -----
> From: JuanPi <aj...@gm...>
> To: Octave Forge <oct...@li...>; hel...@oc...; Octave Maintainers <oct...@oc...>
> Cc: 
> Sent: Wednesday, October 3, 2012 3:25 PM
> Subject: Code sprint: pkg.m
> 
> Hi all,
> 
> I created a doodle for November. The objective is to evaluate how many
> people are joining the code sprint
> (http://wiki.octave.org/Code_sprint:_pkg.m) and on what days we should
> concentrate the activity.
> 
> http://www.doodle.com/x3bh7ity5knekda8
> 
> Thank you for filling the poll
> 
> -- 
> JuanPi Carbajal
> -----
> "It is one thing not to be able to perform a certain feat, but quite
> another to prove that it cannot be done." - Henry Ernest Dudeney
> -----
> http://ailab.ifi.uzh.ch/carbajal/
> _______________________________________________
> Help-octave mailing list
> Hel...@oc...
> https://mailman.cae.wisc.edu/listinfo/help-octave
>

Is there a _spec_ for 'pkg.m' ? I have my own version, which is still broken, but less - at least, for me.

Looking into the code and playing with it I've come to the conclusion that _conceptually_ package management in Octave is not well defined, that's why I'm asking: is there a _functional_ spec telling what 'pkg.m' has to do ?

...

Looking at http://wiki.octave.org/Code_sprint:_pkg.m :

"Remove -global and -local flags  
	* Those flags are currently ignored internally anyways so they should disappear "

- huh ?

They are not ignored, and packages are installed into different locations.

Thanks,
  Sergei.

Re: [OctDev] Vectorizing code array modulo indexing

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

On Wed, Oct 3, 2012 at 6:01 PM, Torbjörn Rathsman
<tor...@st...> wrote:
> Juan Pablo Carbajal skrev 2012-10-03 17:48:
>
>> On Wed, Oct 3, 2012 at 4:55 PM, Torbjörn Rathsman
>> <tor...@st...> wrote:
>>>
>>> Juan Pablo Carbajal skrev 2012-10-03 14:02:
>>>
>>>> On Wed, Oct 3, 2012 at 12:17 PM, Torbjörn Rathsman
>>>> <tor...@st...> wrote:
>>>>>
>>>>> 2012-10-02 22:12, Juan Pablo Carbajal skrev:
>>>>>>
>>>>>> On Tue, Oct 2, 2012 at 9:00 PM, Torbjörn Rathsman
>>>>>> <tor...@st...> wrote:
>>>>>>>
>>>>>>> Is this kind of thing possible to do without do it in a loop?
>>>>>>>
>>>>>>>       notes=[1 1 0 1 1 1 0 1 1 0 1 0]';
>>>>>>>       x=12.*log(f./440)./log(2);
>>>>>>>       spectrum=spectrum.*cos(pi.*x).^16.* notes( mod(round(x),12) + 1
>>>>>>> );
>>>>>>>
>>>>>>> f is a vector of 10^7 elements and I want to take each computed index
>>>>>>> and
>>>>>>> generate corresponding value from notes.
>>>>>>> _______________________________________________
>>>>>>> Help-octave mailing list
>>>>>>> Hel...@oc...
>>>>>>> https://mailman.cae.wisc.edu/listinfo/help-octave
>>>>>>
>>>>>> Can you give more details? I do not see a loop.
>>>>>> I see that you are multiplying spectrum by something and then saving
>>>>>> it back into spectrum. What is the initial value of spectrum.
>>>>>>
>>>>>> Sorry for not understanding.
>>>>>>
>>>>>>
>>>>> Implemented using a loop:
>>>>>
>>>>> notes=[1 1 0 1 1 1 0 1 1 0 1 0]';
>>>>>
>>>>> for k=1:N %N huge
>>>>>
>>>>> x=12.*log(f(k)./440)./log(2);
>>>>>       spectrum(k)=spectrum(k).*cos(pi.*x).^16.* notes( mod(round(x),12)
>>>>> +
>>>>> 1 );
>>>>>
>>>>> end
>>>>>
>>>>> I want to implement the same thing without a loop.
>>>>>
>>>> Hi,
>>>>
>>>> Always keep the mailing list in CC.
>>>>
>>>> Here is my attempt tp vectorize your code. I expanded it so that you
>>>> understand all the stages. You do not need to create all those
>>>> intermediate variables
>>>> http://agora.octave.org/snippet/hchr/
>>>>
>>>> Note that I am assuming that the variable spectrum exists, it is a
>>>> column and has length N.
>>>>
>>>> Hope this helps.
>>>>
>>>>
>>> It does not work. You forgot that f is a vector, so is x and x_mod. Now,
>>> trying to use x_mod as index, will not expand notes into a squarewavish
>>> function but just fail with
>>>
>>>   subscript indices must be either positive integers or logicals
>>
>> Hi,
>>
>> It works here. Can you please post your complete example in Agora
>> (agora.octave.org) so we can see where is the problem?
>>
>> Thanks
>>
>>
> It works, I think I accidently put -inf in x log(0) !

Solution working
http://agora.octave.org/snippet/hchr/

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

Re: [OctDev] Vectorizing code array modulo indexing

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

On Wed, Oct 3, 2012 at 4:55 PM, Torbjörn Rathsman
<tor...@st...> wrote:
> Juan Pablo Carbajal skrev 2012-10-03 14:02:
>
>> On Wed, Oct 3, 2012 at 12:17 PM, Torbjörn Rathsman
>> <tor...@st...> wrote:
>>>
>>> 2012-10-02 22:12, Juan Pablo Carbajal skrev:
>>>>
>>>> On Tue, Oct 2, 2012 at 9:00 PM, Torbjörn Rathsman
>>>> <tor...@st...> wrote:
>>>>>
>>>>> Is this kind of thing possible to do without do it in a loop?
>>>>>
>>>>>      notes=[1 1 0 1 1 1 0 1 1 0 1 0]';
>>>>>      x=12.*log(f./440)./log(2);
>>>>>      spectrum=spectrum.*cos(pi.*x).^16.* notes( mod(round(x),12) + 1 );
>>>>>
>>>>> f is a vector of 10^7 elements and I want to take each computed index
>>>>> and
>>>>> generate corresponding value from notes.
>>>>> _______________________________________________
>>>>> Help-octave mailing list
>>>>> Hel...@oc...
>>>>> https://mailman.cae.wisc.edu/listinfo/help-octave
>>>>
>>>> Can you give more details? I do not see a loop.
>>>> I see that you are multiplying spectrum by something and then saving
>>>> it back into spectrum. What is the initial value of spectrum.
>>>>
>>>> Sorry for not understanding.
>>>>
>>>>
>>> Implemented using a loop:
>>>
>>> notes=[1 1 0 1 1 1 0 1 1 0 1 0]';
>>>
>>> for k=1:N %N huge
>>>
>>> x=12.*log(f(k)./440)./log(2);
>>>      spectrum(k)=spectrum(k).*cos(pi.*x).^16.* notes( mod(round(x),12) +
>>> 1 );
>>>
>>> end
>>>
>>> I want to implement the same thing without a loop.
>>>
>> Hi,
>>
>> Always keep the mailing list in CC.
>>
>> Here is my attempt tp vectorize your code. I expanded it so that you
>> understand all the stages. You do not need to create all those
>> intermediate variables
>> http://agora.octave.org/snippet/hchr/
>>
>> Note that I am assuming that the variable spectrum exists, it is a
>> column and has length N.
>>
>> Hope this helps.
>>
>>
> It does not work. You forgot that f is a vector, so is x and x_mod. Now,
> trying to use x_mod as index, will not expand notes into a squarewavish
> function but just fail with
>
>  subscript indices must be either positive integers or logicals

Hi,

It works here. Can you please post your complete example in Agora
(agora.octave.org) so we can see where is the problem?

Thanks


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

Re: [OctDev] Vectorizing code array modulo indexing

[Torbjörn R. <tor...@st...>]

Juan Pablo Carbajal skrev 2012-10-03 14:02:
> On Wed, Oct 3, 2012 at 12:17 PM, Torbjörn Rathsman
> <tor...@st...> wrote:
>> 2012-10-02 22:12, Juan Pablo Carbajal skrev:
>>> On Tue, Oct 2, 2012 at 9:00 PM, Torbjörn Rathsman
>>> <tor...@st...> wrote:
>>>> Is this kind of thing possible to do without do it in a loop?
>>>>
>>>>      notes=[1 1 0 1 1 1 0 1 1 0 1 0]';
>>>>      x=12.*log(f./440)./log(2);
>>>>      spectrum=spectrum.*cos(pi.*x).^16.* notes( mod(round(x),12) + 1 );
>>>>
>>>> f is a vector of 10^7 elements and I want to take each computed index and
>>>> generate corresponding value from notes.
>>>> _______________________________________________
>>>> Help-octave mailing list
>>>> Hel...@oc...
>>>> https://mailman.cae.wisc.edu/listinfo/help-octave
>>> Can you give more details? I do not see a loop.
>>> I see that you are multiplying spectrum by something and then saving
>>> it back into spectrum. What is the initial value of spectrum.
>>>
>>> Sorry for not understanding.
>>>
>>>
>> Implemented using a loop:
>>
>> notes=[1 1 0 1 1 1 0 1 1 0 1 0]';
>>
>> for k=1:N %N huge
>>
>> x=12.*log(f(k)./440)./log(2);
>>      spectrum(k)=spectrum(k).*cos(pi.*x).^16.* notes( mod(round(x),12) + 1 );
>>
>> end
>>
>> I want to implement the same thing without a loop.
>>
> Hi,
>
> Always keep the mailing list in CC.
>
> Here is my attempt tp vectorize your code. I expanded it so that you
> understand all the stages. You do not need to create all those
> intermediate variables
> http://agora.octave.org/snippet/hchr/
>
> Note that I am assuming that the variable spectrum exists, it is a
> column and has length N.
>
> Hope this helps.
>
>
It does not work. You forgot that f is a vector, so is x and x_mod. Now, 
trying to use x_mod as index, will not expand notes into a squarewavish 
function but just fail with

  subscript indices must be either positive integers or logicals

Re: [OctDev] contribution

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

> On 10/02/2012 06:49 PM, LEo wrote:
>
> what I mean by contribution is code :)
> I've written 3 functions that are not implemented in Octave and I
> would like to send the code.
>
> []s
> LEo

Hi Leo

are they functions also in matlab core? If so, open a request here
https://savannah.gnu.org/patch/?func=additem&group=octave with the
files. Of course, if you can submit a mercurial changeset, things get
processed much faster but if you don't have the time, a m file is good
too.

If the functinos are not in matlab core (either belong to a matlab
toolbox or you made it up yourself), submit them here
https://sourceforge.net/p/octave/feature-requests/ for inclusion in
the octave forge communications package.

Carnë

[OctDev] fuzzy logic toolkit 0.4.2 released

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

Hi everyone

a new release of fuzzy-logic-toolkit is out, version 0.4.2, by L. Markowsky.
Enjoy Octave responsibly.

Carnë

[OctDev] PROJ.4 bindings: OctPROJ 1.1.2 released

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

Hi everyone

a new release of octproj package is out, version 1.1.2, by José Luis
García Pallero.
Enjoy Octave responsibly.

Carnë

[OctDev] clipping polygons: OctCLIP 1.0.3 released

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

Hi everyone

a new release of octclip package is out, version 1.0.3, by José Luis
García Pallero.
Enjoy Octave responsibly.

Carnë

Re: [OctDev] [PKG] lssa

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

On Wed, Oct 3, 2012 at 3:14 PM, Benjamin Lewis <be...@gm...> wrote:
> Le 2012-10-03 à 05:41, JuanPi <aj...@gm...> a écrit :
>
>> Hi there,
>>
>> I am exploring the lssa package, looks really handy. however I am
>> finding difficult to understand the use.
>>
>> I started testing lsreal and the last three input arguments are a
>> little puzzling ( MAXFREQ, NUMCOEFF, NUMOCTAVES).
>> Questions:
>>
>> - Can't this arguments be estimated form the data by default and given
>> as optional in case the user wants some specifics?
>> - Is there an example of use of the function? A demo would be very very handy.
>> - The doc string should contain a minimum explanation of what is
>> maxfreq (at least in what units should be given (rad/s? Hz? normalized
>> as in butter?), numcoef (i expected the result to be this length, but
>> octave I was wrong), numoctaves.
>>
>> If I get the grip of these functions I can help writing demos.
>>
>> Thank you very much for your support.
>>
>
> Hey;
>
> Thank you for trying out lssa. Some background on the functions is in order to explain the arguments you're wondering about, I think:
>
> The ls* functions in the lssa package implement the Lomb-Scargle transform, which is a non-invertible transform which tests independent frequencies against the provided data set; its operations expect radian input, but beyond that, the MAXFREQ term is essentially rad/(pick the unit that matches from your data). The transform (in the case of lsreal and lscomplex) operates over NUMOCTAVES octaves, testing NUMCOEFFS evenly-spaced frequencies per octave. I've got a demo in the works on Octave-Forge, I'll put some time into expanding it, and once it's ready I'll prepare another release of the package together (although it does feature an application of the functions, it doesn't use all of them yet, I don't think.)
>
> In response to the first question, then, I don't think the arguments can really be estimated without possibly running the function first; I'd be happy to get some input on that, though.
>
> Thanks for your feedback on the package!
>
> Ben

Hi Ben,

NUMCOEFF (which from your explanations is more like NUMFREQS. Also
NUMCOEFF is not happy cause the values of the transform are called
coefficients... according to my sources! So it seems NUMCOEFF is the
size of the output of the function...which is not). This is a free
parameter, I agree and the user must provide it, though it could still
have a default value, let say 10 (or whatever).

Can't the MAXFREQ parameter be estimated form the smallest time
interval? something like
maxFreq = pi/min(diff(t))
Also the minimum frequncy could be minFreq = pi/(t(1)-t(end))

If it can be done, then you could get NUMOCTAVES (again an octave is
not that well defined, I assume you mean halving or doubling the
frequencies) as
numoctaves = round (log (maxFreq/minFreq) / log (2))

What do you think?


-- 
JuanPi Carbajal
-----
"It is one thing not to be able to perform a certain feat, but quite
another to prove that it cannot be done." - Henry Ernest Dudeney
-----
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] Instrument control 0.1.0 released [initial release]

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

On 02.10.2012, at 14:36, Andrius Sutas <and...@gm...> wrote:

> On Tue, Oct 2, 2012 at 12:12 PM, Stephen Montgomery-Smith <st...@mi...> wrote:
> On 10/02/2012 02:06 AM, Carnë Draug wrote:
> > Hi everyone
> >
> > a new package, instrument control by Andrius Sutas, has just been
> > released. See the notice at
> > http://andriussutassocis2012.blogspot.com/2012/10/progress-report.html
> > and the wiki at http://wiki.octave.org/Instrument_control_package
> 
> Would it be fair to describe this as a "linux only" package?  It wants
> various include files from a subdirectory called linux when I try to
> compile it under FreeBSD,
> 
> Hey,
> 
> I will look into BSD support this week, thanks for noting it.

Could you please add support for Mac OS X as well, which is closely related to FreeBSD? Windows support wouldn't hurt either, but it might be more difficult since Windows is not a flavour of UNIX.

Best regards,
Lukas

 

[OctDev] Code sprint: pkg.m

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

Hi all,

I created a doodle for November. The objective is to evaluate how many
people are joining the code sprint
(http://wiki.octave.org/Code_sprint:_pkg.m) and on what days we should
concentrate the activity.

http://www.doodle.com/x3bh7ity5knekda8

Thank you for filling the poll

-- 
JuanPi Carbajal
-----
"It is one thing not to be able to perform a certain feat, but quite
another to prove that it cannot be done." - Henry Ernest Dudeney
-----
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] [PKG] lssa

[Benjamin L. <be...@gm...>]

Le 2012-10-03 à 05:41, JuanPi <aj...@gm...> a écrit :

> Hi there,
> 
> I am exploring the lssa package, looks really handy. however I am
> finding difficult to understand the use.
> 
> I started testing lsreal and the last three input arguments are a
> little puzzling ( MAXFREQ, NUMCOEFF, NUMOCTAVES).
> Questions:
> 
> - Can't this arguments be estimated form the data by default and given
> as optional in case the user wants some specifics?
> - Is there an example of use of the function? A demo would be very very handy.
> - The doc string should contain a minimum explanation of what is
> maxfreq (at least in what units should be given (rad/s? Hz? normalized
> as in butter?), numcoef (i expected the result to be this length, but
> octave I was wrong), numoctaves.
> 
> If I get the grip of these functions I can help writing demos.
> 
> Thank you very much for your support.
> 

Hey;

Thank you for trying out lssa. Some background on the functions is in order to explain the arguments you're wondering about, I think:

The ls* functions in the lssa package implement the Lomb-Scargle transform, which is a non-invertible transform which tests independent frequencies against the provided data set; its operations expect radian input, but beyond that, the MAXFREQ term is essentially rad/(pick the unit that matches from your data). The transform (in the case of lsreal and lscomplex) operates over NUMOCTAVES octaves, testing NUMCOEFFS evenly-spaced frequencies per octave. I've got a demo in the works on Octave-Forge, I'll put some time into expanding it, and once it's ready I'll prepare another release of the package together (although it does feature an application of the functions, it doesn't use all of them yet, I don't think.)

In response to the first question, then, I don't think the arguments can really be estimated without possibly running the function first; I'd be happy to get some input on that, though.

Thanks for your feedback on the package!

Ben

Re: [OctDev] [SIGNAL] findpeaks

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

On Wed, Oct 3, 2012 at 2:06 PM, Johan Silen <joh...@fm...> wrote:
> Thanks for a good routine. I tested most of the cases on
> my own data and the routines seem to work. I have sometimes
> used a much simpler routine to do the same kind of things which
> is not though as versatile as yours (which I attach as an example).
> When working with this kind of a routine, the context often dictates
> what you need as output. I do not know what matlab compatibility
> demands.
>
> Quite often one would need to have the fitted parabolas or other model
> functions available and therefore it would be nice to get this data
> returned from the routine. This could possibly be made through a cell
> array of the peak defining entity which would contain position, maximum,
> width, model fit errors etc. This is an issue of practicality and
> compatibility and does not necessary belong here.
>
> If possible, add the column wise operations. It complicates the output
>   but might be doable in several ways. I have sometimes used a boolean
>   matrix for this purpose and sometimes cell arrays. This is also a
> complicated issue, but think about it.
>
> Finally the testing routine not using subplot() would be nicer with two
> independent plots as zooming is then possible and the details of the fit
> are easier to look into. The subplot() routines should in principle be
> rewritten but that is a different issue. If you still use subplot then
> please issue a subplot(1,1,1) at the end of the routine to reset
> plotting.
>
>
>              Regards Johan Silen
>
>
>
>
>
>
>
> On Tue, 2012-10-02 at 16:26 +0300, JuanPi wrote:
>> Hi,
>>
>> I added this ticket
>> https://sourceforge.net/p/octave/feature-requests/39/
>>
>> It is a first version of findpeaks. It was programmed from scratch so
>> any similarity to already existing functions is mere coincidence.
>>
>> The function depends on the general package > 1.3.2
>>
>> If there are no comments in a week I will add it to the signal package.
>>
>> Thanks for reviewing!
>>
>
> --
> -----------------------------------------------------------------------
> Dr. Johan Silén
> Finnish Meteorological Institute
> Erik Palmenin aukio 1
> 00560 Helsinki, Finland
> Phone:+358505423872, ex. +358295391000
> Email:joh...@fm....

Hi Johan,

Thank you for your very useful comments. I will work to implement what
you suggested.

-- 
JuanPi Carbajal
-----
"It is one thing not to be able to perform a certain feat, but quite
another to prove that it cannot be done." - Henry Ernest Dudeney
-----
http://ailab.ifi.uzh.ch/carbajal/

Re: [OctDev] Vectorizing code array modulo indexing

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

On Wed, Oct 3, 2012 at 12:17 PM, Torbjörn Rathsman
<tor...@st...> wrote:
> 2012-10-02 22:12, Juan Pablo Carbajal skrev:
>> On Tue, Oct 2, 2012 at 9:00 PM, Torbjörn Rathsman
>> <tor...@st...> wrote:
>>> Is this kind of thing possible to do without do it in a loop?
>>>
>>>     notes=[1 1 0 1 1 1 0 1 1 0 1 0]';
>>>     x=12.*log(f./440)./log(2);
>>>     spectrum=spectrum.*cos(pi.*x).^16.* notes( mod(round(x),12) + 1 );
>>>
>>> f is a vector of 10^7 elements and I want to take each computed index and
>>> generate corresponding value from notes.
>>> _______________________________________________
>>> Help-octave mailing list
>>> Hel...@oc...
>>> https://mailman.cae.wisc.edu/listinfo/help-octave
>> Can you give more details? I do not see a loop.
>> I see that you are multiplying spectrum by something and then saving
>> it back into spectrum. What is the initial value of spectrum.
>>
>> Sorry for not understanding.
>>
>>
> Implemented using a loop:
>
> notes=[1 1 0 1 1 1 0 1 1 0 1 0]';
>
> for k=1:N %N huge
>
> x=12.*log(f(k)./440)./log(2);
>     spectrum(k)=spectrum(k).*cos(pi.*x).^16.* notes( mod(round(x),12) + 1 );
>
> end
>
> I want to implement the same thing without a loop.
>

Hi,

Always keep the mailing list in CC.

Here is my attempt tp vectorize your code. I expanded it so that you
understand all the stages. You do not need to create all those
intermediate variables
http://agora.octave.org/snippet/hchr/

Note that I am assuming that the variable spectrum exists, it is a
column and has length N.

Hope this helps.


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

[OctDev] [PKG] lssa

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

Hi there,

I am exploring the lssa package, looks really handy. however I am
finding difficult to understand the use.

I started testing lsreal and the last three input arguments are a
little puzzling ( MAXFREQ, NUMCOEFF, NUMOCTAVES).
Questions:

- Can't this arguments be estimated form the data by default and given
as optional in case the user wants some specifics?
- Is there an example of use of the function? A demo would be very very handy.
- The doc string should contain a minimum explanation of what is
maxfreq (at least in what units should be given (rad/s? Hz? normalized
as in butter?), numcoef (i expected the result to be this length, but
octave I was wrong), numoctaves.

If I get the grip of these functions I can help writing demos.

Thank you very much for your support.

-- 
JuanPi Carbajal
-----
"It is one thing not to be able to perform a certain feat, but quite
another to prove that it cannot be done." - Henry Ernest Dudeney
-----
http://ailab.ifi.uzh.ch/carbajal/

[OctDev] fuzzy-logic-toolkit release 0.4.2

[L. M. <lm...@us...>]

Hello,

I've posted release 0.4.2 of the fuzzy-logic-toolkit to the package release forum. 
When you have time, would you upload the new files to the server?

Thank you,
L. Markowsky
 		 	   		  

Re: [OctDev] SVN permission denied

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

On Tue, Oct 2, 2012 at 5:52 PM, Carnë Draug <car...@gm...> wrote:
> On 2 October 2012 15:32, JuanPi <aj...@gm...> wrote:
>> Hi,
>>
>> Since a while I am getting this message everytime I try to commit to
>> sf repository.
>>
>>
>> Transmitting file data .svn: Commit failed (details follow):
>> svn: Can't open file '/svn/p/octave/code/db/txn-current-lock': Permission denied
>>
>>
>> Any advice? Is this a problem of sf?
>
> Open a ticket at https://sourceforge.net/p/forge/site-support/new/
>
> My experience is that they are quite fast in answering. You can also
> try #sourceforge
>
> Carnë

I will, a few hours ago I could commit. If I get this agian I will contact them.

Thx

-- 
JuanPi Carbajal
-----
"It is one thing not to be able to perform a certain feat, but quite
another to prove that it cannot be done." - Henry Ernest Dudeney
-----
http://ailab.ifi.uzh.ch/carbajal/