Menu
▾
▴
octave-dev — GNU Octave developers' list
This list is closed, nobody may subscribe to it.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(10) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
(4) |
Mar
|
Apr
(3) |
May
(13) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
(2) |
Oct
(5) |
Nov
(8) |
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
(19) |
Apr
(8) |
May
(8) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(19) |
Oct
(13) |
Nov
(37) |
Dec
(2) |
| 2003 |
Jan
(7) |
Feb
(23) |
Mar
(16) |
Apr
(4) |
May
(18) |
Jun
(9) |
Jul
(7) |
Aug
(6) |
Sep
(7) |
Oct
|
Nov
(39) |
Dec
(57) |
| 2004 |
Jan
(21) |
Feb
(15) |
Mar
(17) |
Apr
(9) |
May
(17) |
Jun
(65) |
Jul
(33) |
Aug
(48) |
Sep
(93) |
Oct
(35) |
Nov
(18) |
Dec
(4) |
| 2005 |
Jan
(20) |
Feb
(59) |
Mar
(17) |
Apr
(59) |
May
(77) |
Jun
(32) |
Jul
(34) |
Aug
(8) |
Sep
(34) |
Oct
(26) |
Nov
(65) |
Dec
(66) |
| 2006 |
Jan
(45) |
Feb
(37) |
Mar
(50) |
Apr
(32) |
May
(48) |
Jun
(42) |
Jul
(12) |
Aug
(53) |
Sep
(51) |
Oct
(79) |
Nov
(46) |
Dec
(25) |
| 2007 |
Jan
(120) |
Feb
(78) |
Mar
(45) |
Apr
(91) |
May
(155) |
Jun
(66) |
Jul
(96) |
Aug
(110) |
Sep
(145) |
Oct
(189) |
Nov
(68) |
Dec
(160) |
| 2008 |
Jan
(163) |
Feb
(212) |
Mar
(209) |
Apr
(157) |
May
(216) |
Jun
(120) |
Jul
(80) |
Aug
(83) |
Sep
(98) |
Oct
(120) |
Nov
(80) |
Dec
(129) |
| 2009 |
Jan
(45) |
Feb
(80) |
Mar
(174) |
Apr
(142) |
May
(133) |
Jun
(191) |
Jul
(183) |
Aug
(138) |
Sep
(77) |
Oct
(141) |
Nov
(209) |
Dec
(131) |
| 2010 |
Jan
(85) |
Feb
(213) |
Mar
(245) |
Apr
(222) |
May
(168) |
Jun
(82) |
Jul
(50) |
Aug
(144) |
Sep
(92) |
Oct
(80) |
Nov
(64) |
Dec
(78) |
| 2011 |
Jan
(58) |
Feb
(98) |
Mar
(112) |
Apr
(98) |
May
(64) |
Jun
(150) |
Jul
(126) |
Aug
(59) |
Sep
(271) |
Oct
(154) |
Nov
(321) |
Dec
(183) |
| 2012 |
Jan
(146) |
Feb
(217) |
Mar
(426) |
Apr
(208) |
May
(206) |
Jun
(230) |
Jul
(158) |
Aug
(170) |
Sep
(237) |
Oct
(260) |
Nov
(178) |
Dec
|
|
From: Bogdan <lov...@ya...> - 2012-08-21 15:38:20
|
Hi again, Sadly, it seems like I am forced to drop the project. The MinGW developers have the habit to simply not check tickets (sometimes in the middle of the conversation; even if they're expecting a patch) and the Octave-Forge community also seems disinterested... or maybe Nitzan just doesn't have the time to document what he did; I'm not judging. Cheers, Bogdan -- View this message in context: http://octave.1599824.n4.nabble.com/Regarding-the-MSYS-installer-tp4632442p4643045.html Sent from the Octave - Dev mailing list archive at Nabble.com. |
|
From: Bogdan <lov...@ya...> - 2012-08-21 15:37:49
|
Hi again, Sadly, it seems like I am forced to drop the project. The MinGW developers have the habit to simply not check tickets (sometimes in the middle of the conversation; even if they're expecting a patch) and the Octave-Forge community also seems disinterested... or maybe Nitzan just doesn't have the time to document what he did; I'm not judging. Cheers, Bogdan -- View this message in context: http://octave.1599824.n4.nabble.com/Regarding-the-MSYS-installer-tp4632442p4643044.html Sent from the Octave - Dev mailing list archive at Nabble.com. |
|
From: Martin H. <ma...@mh...> - 2012-08-21 15:23:20
|
Am 21.08.2012 17:33, schrieb fabien amiot:
> On 21/08/2012 17:03, Martin Helm wrote:
>> Am 21.08.2012 17:22, schrieb fabien amiot:
>>
>>> signal | 1.1.3 |
>>>
>> There is no * which means signal is not loaded.
>>
>> Either do a
>> pkg load signal
>> or
>> pkg rebuild -auto signal
>>
>>
>>
> adding
>
> pkg load signal
>
> yields
>
> Package Name | Version | Installation directory
> ---------------+---------+-----------------------
> control *| 2.3.52 |
> .../octave/3.6.2/share/octave/packages/control-2.3.52
> general | 1.3.1 |
> .../octave/3.6.2/share/octave/packages/general-1.3.1
> gnuplot | 1.0.1 |
> .../octave/3.6.2/share/octave/packages/gnuplot-1.0.1
> gsl *| 1.0.8 |
> .../apps/octave/3.6.2/share/octave/packages/gsl-1.0.8
> image *| 1.0.15 |
> .../octave/3.6.2/share/octave/packages/image-1.0.15
> miscellaneous *| 1.1.0 |
> .../3.6.2/share/octave/packages/miscellaneous-1.1.0
> optim *| 1.2.0 |
> .../octave/3.6.2/share/octave/packages/optim-1.2.0
> parallel *| 2.0.5 |
> .../octave/3.6.2/share/octave/packages/parallel-2.0.5
> signal *| 1.1.3 |
> .../octave/3.6.2/share/octave/packages/signal-1.1.3
> specfun *| 1.1.0 |
> .../octave/3.6.2/share/octave/packages/specfun-1.1.0
> struct *| 1.0.10 |
> .../octave/3.6.2/share/octave/packages/struct-1.0.10
>
> but also the same error:
> error: Invalid call to fminbnd. Correct usage is:
>
> Function File: [X, FVAL, INFO, OUTPUT] = fminbnd (FUN, A, B,
> OPTIONS)
>
>
> Fabien
>
I do not get that with 3.6.2 and signal 1.1.3
check with
which fminbnd
if the fminbnd which is called is really from the signal package!
octave:1> pkg load signal
octave:2> pkg list
Package Name | Version | Installation directory
---------------+---------+-----------------------
control *| 2.3.52 | /usr/share/octave/packages/control-2.3.52
image *| 1.0.15 | /usr/share/octave/packages/image-1.0.15
java | 1.2.9 | /usr/share/octave/packages/java-1.2.9
miscellaneous *| 1.1.0 | /usr/share/octave/packages/miscellaneous-1.1.0
odepkg | 0.8.2 | /usr/share/octave/packages/odepkg-0.8.2
optim *| 1.2.0 | /usr/share/octave/packages/optim-1.2.0
signal *| 1.1.3 | /usr/share/octave/packages/signal-1.1.3
specfun *| 1.1.0 | /usr/share/octave/packages/specfun-1.1.0
struct *| 1.0.10 | /usr/share/octave/packages/struct-1.0.10
octave:3> [b,a]=ellip(5,1,90,[.1,.2])
b =
Columns 1 through 6:
0.0001321 -0.0006639 0.0014925 -0.0019624 0.0014425 0.0000000
Columns 7 through 11:
-0.0014425 0.0019624 -0.0014925 0.0006639 -0.0001321
a =
Columns 1 through 6:
1.00000 -8.64826 34.60318 -84.21550 137.92762 -158.75980
Columns 7 through 11:
130.04250 -74.86358 29.00444 -6.83593 0.74556
octave:4>
|
|
From: Martin H. <ma...@mh...> - 2012-08-21 15:17:00
|
Am 21.08.2012 17:22, schrieb fabien amiot: > signal | 1.1.3 | There is no * which means signal is not loaded. Either do a pkg load signal or pkg rebuild -auto signal |
|
From: fabien a. <fab...@fe...> - 2012-08-21 15:13:15
|
On 21/08/2012 17:03, Martin Helm wrote:
> Am 21.08.2012 17:22, schrieb fabien amiot:
>
>> signal | 1.1.3 |
>>
> There is no * which means signal is not loaded.
>
> Either do a
> pkg load signal
> or
> pkg rebuild -auto signal
>
>
>
adding
pkg load signal
yields
Package Name | Version | Installation directory
---------------+---------+-----------------------
control *| 2.3.52 |
.../octave/3.6.2/share/octave/packages/control-2.3.52
general | 1.3.1 |
.../octave/3.6.2/share/octave/packages/general-1.3.1
gnuplot | 1.0.1 |
.../octave/3.6.2/share/octave/packages/gnuplot-1.0.1
gsl *| 1.0.8 |
.../apps/octave/3.6.2/share/octave/packages/gsl-1.0.8
image *| 1.0.15 |
.../octave/3.6.2/share/octave/packages/image-1.0.15
miscellaneous *| 1.1.0 |
.../3.6.2/share/octave/packages/miscellaneous-1.1.0
optim *| 1.2.0 |
.../octave/3.6.2/share/octave/packages/optim-1.2.0
parallel *| 2.0.5 |
.../octave/3.6.2/share/octave/packages/parallel-2.0.5
signal *| 1.1.3 |
.../octave/3.6.2/share/octave/packages/signal-1.1.3
specfun *| 1.1.0 |
.../octave/3.6.2/share/octave/packages/specfun-1.1.0
struct *| 1.0.10 |
.../octave/3.6.2/share/octave/packages/struct-1.0.10
but also the same error:
error: Invalid call to fminbnd. Correct usage is:
Function File: [X, FVAL, INFO, OUTPUT] = fminbnd (FUN, A, B,
OPTIONS)
Fabien
--
Fabien AMIOT
Chargé de recherche CNRS en colere / cross Research Associate
fab...@fe...
Tel : (+33) (0)3.81.66.60.14
Fax : (+33) (0)3.81.66.67.00
UMR6174 / FEMTO-ST, Dpt. Mécanique Appliquée
24, rue de l'Épitaphe
25000 Besancon
France
|
|
From: fabien a. <fab...@fe...> - 2012-08-21 15:01:30
|
On 21/08/2012 14:48, Carnë Draug wrote: > On 21 August 2012 13:39, Jordi Gutiérrez Hermoso<jo...@oc...> wrote: > >> Hi. >> >> On 21 August 2012 08:44, fabien amiot<fab...@fe...> wrote: >> >>>> On 26/06/2011 20:24, The Theorizer wrote: >>>> >>>> invoking ellip() of signal package causes error when calling to fminbnd(). >>>> Obviously __ellip_ws() expects some other parameter signature of fminbnd. >>>> >>>> >> >>> Upgrading from 3.2.4 to 3.6.2 on our cluster yields the same problem when >>> invoking fminbnd, >>> >> The problem isn't the Octave version, but the version of the signal >> package. What version are you using? >> > Seems to be 1.0.11. > > Try to upgrade to 1.1.3. > > Carnë > > There was no signal installed. The install is now : ---------------------------------------------------------------------- GNU Octave Version 3.6.2 GNU Octave License: GNU General Public License Operating System: Linux 2.6.32-220.13.1.el6.x86_64 #1 SMP Tue Apr 17 23:56:34 BST 2012 x86_64 ---------------------------------------------------------------------- Package Name | Version | Installation directory ---------------+---------+----------------------- control *| 2.3.52 | /share/apps/octave/3.6.2/share/octave/packages/control-2.3.52 general | 1.3.1 | /share/apps/octave/3.6.2/share/octave/packages/general-1.3.1 gnuplot | 1.0.1 | /share/apps/octave/3.6.2/share/octave/packages/gnuplot-1.0.1 gsl *| 1.0.8 | /share/apps/octave/3.6.2/share/octave/packages/gsl-1.0.8 image *| 1.0.15 | /share/apps/octave/3.6.2/share/octave/packages/image-1.0.15 miscellaneous | 1.1.0 | /share/apps/octave/3.6.2/share/octave/packages/miscellaneous-1.1.0 optim | 1.2.0 | /share/apps/octave/3.6.2/share/octave/packages/optim-1.2.0 parallel *| 2.0.5 | /share/apps/octave/3.6.2/share/octave/packages/parallel-2.0.5 signal | 1.1.3 | /share/apps/octave/3.6.2/share/octave/packages/signal-1.1.3 specfun | 1.1.0 | /share/apps/octave/3.6.2/share/octave/packages/specfun-1.1.0 struct | 1.0.10 | /share/apps/octave/3.6.2/share/octave/packages/struct-1.0.10 and the problem is still there... Fabien -- Fabien AMIOT Chargé de recherche CNRS en colere / cross Research Associate fab...@fe... Tel : (+33) (0)3.81.66.60.14 Fax : (+33) (0)3.81.66.67.00 UMR6174 / FEMTO-ST, Dpt. Mécanique Appliquée 24, rue de l'Épitaphe 25000 Besancon France |
|
From: Carnë D. <car...@gm...> - 2012-08-21 12:48:48
|
On 21 August 2012 13:39, Jordi Gutiérrez Hermoso <jo...@oc...> wrote: > Hi. > > On 21 August 2012 08:44, fabien amiot <fab...@fe...> wrote: >> > On 26/06/2011 20:24, The Theorizer wrote: >> > >> > invoking ellip() of signal package causes error when calling to fminbnd(). >> > Obviously __ellip_ws() expects some other parameter signature of fminbnd. >> > > >> Upgrading from 3.2.4 to 3.6.2 on our cluster yields the same problem when >> invoking fminbnd, > > The problem isn't the Octave version, but the version of the signal > package. What version are you using? Seems to be 1.0.11. Try to upgrade to 1.1.3. Carnë |
|
From: Jordi G. H. <jo...@oc...> - 2012-08-21 12:40:08
|
Hi. On 21 August 2012 08:44, fabien amiot <fab...@fe...> wrote: > > On 26/06/2011 20:24, The Theorizer wrote: > > > > invoking ellip() of signal package causes error when calling to fminbnd(). > > Obviously __ellip_ws() expects some other parameter signature of fminbnd. > > > Upgrading from 3.2.4 to 3.6.2 on our cluster yields the same problem when > invoking fminbnd, The problem isn't the Octave version, but the version of the signal package. What version are you using? - Jordi G. H. |
|
From: fabien a. <fab...@fe...> - 2012-08-21 12:24:28
|
Dear all, Upgrading from 3.2.4 to 3.6.2 on our cluster yields the same problem when invoking fminbnd, and it doen't seem from browsing the mailing list that it's been fixed so far. Is there a smart way to ensure compatibility ? Best, Fabien On 26/06/2011 20:24, The Theorizer wrote: > invoking ellip() of signal package causes error when calling to > fminbnd(). Obviously __ellip_ws() expects some other parameter > signature of fminbnd. > [b,a]=ellip(5,1,90,[.1,.2]) > error: Invalid call to fminbnd. Correct usage is: > > -- Function File: [X, FVAL, INFO, OUTPUT] = fminbnd (FUN, A, B, > OPTIONS) > > error: called from: > error: /usr/local/share/octave/3.4.1/m/help/print_usage.m at line > 87, column 5 > error: /usr/local/share/octave/3.4.1/m/optimization/fminbnd.m at > line 64, column 5 > error: /usr/local/share/octave/packages/signal-1.0.11/__ellip_ws.m > at line 37, column 3 > error: /usr/local/share/octave/packages/signal-1.0.11/ncauer.m at > line 40, column 3 > error: /usr/local/share/octave/packages/signal-1.0.11/ellip.m at > line 110, column 21 > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > > > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev > -- Fabien AMIOT Chargé de recherche CNRS en colere / cross Research Associate fab...@fe... Tel : (+33) (0)3.81.66.60.14 Fax : (+33) (0)3.81.66.67.00 UMR6174 / FEMTO-ST, Dpt. Mécanique Appliquée 24, rue de l'Épitaphe 25000 Besancon France |
|
From: Carnë D. <car...@gm...> - 2012-08-21 11:32:00
|
Always make reply to all to include the mailing list and avoid top posting (we do bottom posting on this mailing list) http://www.idallen.com/topposting.html On 21 August 2012 06:17, <ro...@bu...> wrote: > Quoting Carnë Draug <car...@gm...>: > >> On 20 August 2012 13:33, Roman Bumerl-Lexa <ro...@bu...> wrote: >>> >>> When using the golay decoder (an error correcting decoder), and there are >>> more than the three allowed erroneous bits, the function crashes instead >>> of >>> setting the error flag. >>> >>> Golaytestcase.m: >>> >>> %octave >>> % Testcase for crashing egolaydec.m >>> x=[1 0 1 0 1 0 1 0 1 0 1 0 ]; >>> y=egolayenc(x); % create the encoded vector. >>> y(17:2:23)=0; % set four errors in this vector. >>> [res,err]=egolaydec (y) % try to decode this erroneous vector. >>> >>> >>> >>> I contacted the author Annamalai, Muthiah >>> <mut...@ma...> >>> and he wrote : >>> >>> "Roman, >>> >>> I will not be able to debug the algorithm. But the error can be fixed by >>> inserting the line, >>> >>> E=[S, zeros(1,12)]; >>> >>> just after the statement >>> >>> done = 0; >>> >>> You may also submit a patch to the Octave project. I won't be able to >>> do this. >>> >>> Thanks, >>> -Muthu" >>> >>> I have inserted the line and it works now fine. I have tested it also for >>> some other bitvectors containing more than the four errors used in my >>> test >>> case. >>> >>> Can anyone please fix this in the repository. >>> >>> Roman >> >> >> Hi Roman, >> >> thank you for the fix. I have applied it now to the development tree. >> Could you check if everything is right now? >> >> Carnë >> > > Hi Carnë > > I have downloaded this actualized version of egolaydec.m from the link > below, but it did not work. Maybe this is caused by running the older Octave > Version 3.2.4. > I will try it on another installation with Octave 3.6. I will inform you. > > http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/comm/inst/egolaydec.m?revision=10893 > > > > My working version consists of the egolaydec.m out of the following link, > including the inserted line from Muthiah. > > http://sourceforge.net/projects/octave/files/Octave%20Forge%20Packages/Individual%20Package%20Releases/communications-1.1.1.tar.gz/download > > Roman Hi Roman maybe. I don't have 3.2 installed but it passes both tests in 3.6.2. Carnë |
|
From: Juan P. C. <car...@if...> - 2012-08-21 08:51:29
|
On Mon, Aug 20, 2012 at 12:37 AM, Andrius Sutas <and...@gm...> wrote:
> Hi everyone,
>
> I would like to announce a public commit for i2c package in main/i2c. Also,
> snapshot attached for testing convenience.
>
> Simple example:
> Assume we are working with AD7991 ADC ( goo.gl/TsFMZ ) and our i2c adapter
> is at /dev/i2c-0 (hint: nodes are usually created by i2c-dev module)
>
> pkg load i2c
>
> adc = i2c("/dev/i2c-0"); # Open the interface
> i2c_addr(adc, bin2dec(00101001)); # Set i2c slave address, see datasheet
> (Table 8)
>
> # Reads all 4 channels
> for i = 1:4
> data = i2c_read(adc, 2)
> endfor
>
> i2c_write(adc, uint8( [bin2dec("01000000")] )) # Enable only CH2, see
> datasheet (Table 9)
>
> # Reads ch2, 4 times
> for i = 1:4
> [data, count] = i2c_read(adc, 2)
> endfor
>
> i2c_close(adc)
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
>
Hi Andrius,
Thank you very much.
I haven't testes i2c yet, but I will do it soon. I am very curious!
I just went again through the code and I see no documentation yet.
Please understand that documentation is a very important (I would say
critical) art of your programming activity. Without documentation your
code is not as valuable as it could be! Please document serial and i2c
properly before continuing developing code.
It is not only necessary to add comments to your code, but also (and
this is necessary if you want your project to be released publicly, or
ever migrate to core) add documentation for the user in the help
string.
Do not underestimate the time and difficulty of documenting your
functions. A professor of mine used to say documenting is about 30% of
the time of a project.
Keep up the good job.
--
M. Sc. Juan Pablo Carbajal
-----
PhD Student
University of Zürich
http://ailab.ifi.uzh.ch/carbajal/
|
|
From: Carlo de F. <car...@gm...> - 2012-08-21 08:25:29
|
I agree with JuanPi's point, abandoning the "forge" name abruptly might cause some confusion. So I'd say let's use "forge" as a collective name for all "modules", we could refer to the section of the site containing the source repository documentation and released downloads of modules as 'forge'. What do you think? c. On Aug 21, 2012 12:02 AM, "JuanPi" <aj...@gm...> wrote: On Mon, Aug 20, 2012 at 5:57 PM, Carnë Draug <car...@gm...> wrote: > On 20 August 2012 1... Single, Bundle, Module sounds good to me. Though I do not see why we are running away from Forge package. Are we going to drop all the Octave Forge presence? I think it may be wise to leave the "Forge" connection somewhere, otherwise it can get quite confusing for newcomers doing search on the internet and add to the general obscurity/misunderstanding. -- JuanPi Carbajal ----- "The bad economist pursues a small present good, which will be followed ... |
|
From: Carnë D. <car...@gm...> - 2012-08-21 03:01:32
|
On 14 August 2012 17:40, c. <car...@gm...> wrote: > Hi, > > It seems from a few recent posts on the list that openmpi_ext is getting some > attention lately, so I decided to have a look at its current status. > > It seems that although it received very little maintainace in the last three years > it is still in very good shape and is still useful. > > I went through the code and did a little cleanup, fixed some trivial bugs and removed > a lot of code duplication making use of templates and macros where possible. > > Does anyone object if I apply the attached patch and prepare a new release? Seems no one has anything against it, so I'd say "Go for it". Carnë |
|
From: Carnë D. <car...@gm...> - 2012-08-21 01:13:53
|
On 20 August 2012 13:33, Roman Bumerl-Lexa <ro...@bu...> wrote: > When using the golay decoder (an error correcting decoder), and there are > more than the three allowed erroneous bits, the function crashes instead of > setting the error flag. > > Golaytestcase.m: > > %octave > % Testcase for crashing egolaydec.m > x=[1 0 1 0 1 0 1 0 1 0 1 0 ]; > y=egolayenc(x); % create the encoded vector. > y(17:2:23)=0; % set four errors in this vector. > [res,err]=egolaydec (y) % try to decode this erroneous vector. > > > > I contacted the author Annamalai, Muthiah <mut...@ma...> > and he wrote : > > “Roman, > > I will not be able to debug the algorithm. But the error can be fixed by > inserting the line, > > E=[S, zeros(1,12)]; > > just after the statement > > done = 0; > > You may also submit a patch to the Octave project. I won't be able to > do this. > > Thanks, > -Muthu“ > > I have inserted the line and it works now fine. I have tested it also for > some other bitvectors containing more than the four errors used in my test > case. > > Can anyone please fix this in the repository. > > Roman Hi Roman, thank you for the fix. I have applied it now to the development tree. Could you check if everything is right now? Carnë |
|
From: JuanPi <aj...@gm...> - 2012-08-20 18:32:22
|
On Mon, Aug 20, 2012 at 5:57 PM, Carnë Draug <car...@gm...> wrote: > On 20 August 2012 16:23, John W. Eaton <jw...@oc...> wrote: >> On 20-Aug-2012, Jordi Gutiérrez Hermoso wrote: >> >> | On 20 August 2012 01:18, c. <car...@gm...> wrote: >> | > What about following Matlab's naming conventions and using "toolbox" or "toolchest"? >> | >> | Might as well. People keep referring to OF packages as "toolboxes". >> | Alois for example uses this term exclusively to refer to the NaN >> | package. >> >> I would rather stay away from the term "toolbox" because, for example, >> "Control System Toolbox" is a registered trademark. > > What about using the, already quite standardized by other languages, > word module? > > Carnë Single, Bundle, Module sounds good to me. Though I do not see why we are running away from Forge package. Are we going to drop all the Octave Forge presence? I think it may be wise to leave the "Forge" connection somewhere, otherwise it can get quite confusing for newcomers doing search on the internet and add to the general obscurity/misunderstanding. -- 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/ |
|
From: Carnë D. <car...@gm...> - 2012-08-20 15:58:06
|
On 20 August 2012 16:23, John W. Eaton <jw...@oc...> wrote: > On 20-Aug-2012, Jordi Gutiérrez Hermoso wrote: > > | On 20 August 2012 01:18, c. <car...@gm...> wrote: > | > What about following Matlab's naming conventions and using "toolbox" or "toolchest"? > | > | Might as well. People keep referring to OF packages as "toolboxes". > | Alois for example uses this term exclusively to refer to the NaN > | package. > > I would rather stay away from the term "toolbox" because, for example, > "Control System Toolbox" is a registered trademark. What about using the, already quite standardized by other languages, word module? Carnë |
|
From: John W. E. <jw...@oc...> - 2012-08-20 15:40:17
|
On 20-Aug-2012, Jordi Gutiérrez Hermoso wrote: | On 20 August 2012 01:18, c. <car...@gm...> wrote: | > What about following Matlab's naming conventions and using "toolbox" or "toolchest"? | | Might as well. People keep referring to OF packages as "toolboxes". | Alois for example uses this term exclusively to refer to the NaN | package. I would rather stay away from the term "toolbox" because, for example, "Control System Toolbox" is a registered trademark. jwe |
|
From: Jordi G. H. <jo...@oc...> - 2012-08-20 12:36:24
|
On 20 August 2012 01:18, c. <car...@gm...> wrote: > What about following Matlab's naming conventions and using "toolbox" or "toolchest"? Might as well. People keep referring to OF packages as "toolboxes". Alois for example uses this term exclusively to refer to the NaN package. - Jordi G. H. |
|
From: c. <car...@gm...> - 2012-08-20 05:18:27
|
On 19 Aug 2012, at 18:53, Ben Abbott wrote: > I like the idea of using consistent names. Is there a reason to use "Single" instead of "Function", and "Forge" instead of "Package"? > > Ben I also like "package" more than forge, but it might be a problem as that word has a different meaning in Matlab: http://www.mathworks.it/help/techdoc/matlab_oop/brfynt_-1.html and the same feature is soon to be available in Octave so it might be confusing to use the same term for different things. What about following Matlab's naming conventions and using "toolbox" or "toolchest"? c. |
|
From: Benjamin L. <be...@gm...> - 2012-08-19 18:17:54
|
Le 2012-08-19 à 12:53, Ben Abbott <bpa...@ma...> a écrit : > On Aug 19, 2012, at 7:28 AM, JuanPi wrote: > >> Hi, >> >> Carne rose the issue that the names single, bundle and forge weren't >> meant to stick. I personally like them. But maybe is time to collect >> some ideas >> >> In general lines the names stand for >> >> * Single: A upload of a single file. The only requirement are that it >> is code usable in Octave and that the file is released under a GPL >> compatible license. >> * Bundle: A zip file with multiple files. May or may not have the >> structure of a package. Even with package structure it is not >> guaranteed that it will install. >> * Forge: A zip file containing the structure of a package. A Forge >> package must install correctly, must work and all GNU Octave coding >> criteria applies. >> >> Any body against these names? If so, please give alternatives. >> >> Thanks >> >> -- >> JuanPi Carbajal > > I like the idea of using consistent names. Is there a reason to use "Single" instead of "Function", and "Forge" instead of "Package"? > > Ben Well, a given file might be either a script or a function, so I'm not sure whether we'd want two terms for a single file, but I agree that "Package" makes more sense than "Forge". Ben Lewis |
|
From: Ben A. <bpa...@ma...> - 2012-08-19 16:53:56
|
On Aug 19, 2012, at 7:28 AM, JuanPi wrote: > Hi, > > Carne rose the issue that the names single, bundle and forge weren't > meant to stick. I personally like them. But maybe is time to collect > some ideas > > In general lines the names stand for > > * Single: A upload of a single file. The only requirement are that it > is code usable in Octave and that the file is released under a GPL > compatible license. > * Bundle: A zip file with multiple files. May or may not have the > structure of a package. Even with package structure it is not > guaranteed that it will install. > * Forge: A zip file containing the structure of a package. A Forge > package must install correctly, must work and all GNU Octave coding > criteria applies. > > Any body against these names? If so, please give alternatives. > > Thanks > > -- > JuanPi Carbajal I like the idea of using consistent names. Is there a reason to use "Single" instead of "Function", and "Forge" instead of "Package"? Ben |
|
From: JuanPi <aj...@gm...> - 2012-08-19 11:28:42
|
Hi, Carne rose the issue that the names single, bundle and forge weren't meant to stick. I personally like them. But maybe is time to collect some ideas In general lines the names stand for * Single: A upload of a single file. The only requirement are that it is code usable in Octave and that the file is released under a GPL compatible license. * Bundle: A zip file with multiple files. May or may not have the structure of a package. Even with package structure it is not guaranteed that it will install. * Forge: A zip file containing the structure of a package. A Forge package must install correctly, must work and all GNU Octave coding criteria applies. Any body against these names? If so, please give alternatives. Thanks -- 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/ |
|
From: Carnë D. <car...@gm...> - 2012-08-17 19:39:41
|
Hi everyone a new release of lssa package is out, version 0.1.2, by Ben Lewis. Enjoy Octave responsibly. Carnë |
|
From: Joni H. <jo...@gm...> - 2012-08-17 11:13:51
|
Thanks Michael. Adding vc100-libhdf5 hl-7.dll to the bin folder did the trick. Now it passes 23 out of 23 tests. Joni On Fri, Aug 17, 2012 at 3:21 AM, Michael Goffioul < mic...@gm...> wrote: > On Fri, Aug 17, 2012 at 9:03 AM, Michael Goffioul < > mic...@gm...> wrote: > >> On Thu, Aug 16, 2012 at 11:32 PM, Joni Hall <jo...@gm...> wrote: >> >>> Dear Mr. Goffioul >>> I am using octave-3.6.2-vs2010 I'm having a bit of a problem using >>> octcdf-1.1.4 >>> Can you please look at the attached log file and netcdf.oct file. Maybe >>> you suggest what I can do to get my setup working properly. >>> >> >> Your error is weird, it appears you're missing dependent DLL's. Could you >> check whether you have a DLL named vc100-libnetcdf-...dll >> in C:\Octave\Octave-3.6.2\bin folder? >> >> A useful tool to track DLL dependencies is given here [1] (it's a simple >> ZIP file with a self-contained executable, no installation required). I >> suggest you copy netcdf.oct into C:\Octave\Octave-3.6.2\bin, then starts >> the dependency walker and drag-n-drop netcdf.oct >> from C:\Octave\Octave-3.6.2\bin into the program window. This should tell >> you what depedency is missing. >> > > Nevermind, I found the problem. The installer is indeed missing a DLL, my > apologies. You can download it from here: > > http://dl.dropbox.com/u/45539519/vc100-libhdf5_hl-7.dll > > Drop this file into C:\Octave\Octave-3.6.2\bin, it should solve your > problem. > > Michael. > > |
|
From: Juan P. C. <car...@if...> - 2012-08-17 10:21:05
|
On Fri, Aug 17, 2012 at 12:20 PM, Juan Pablo Carbajal <car...@if...> wrote: > On Fri, Aug 17, 2012 at 1:38 AM, Andrius Sutas <and...@gm...> wrote: >> Hey Juan, >> >> So I upgraded VM to Ubuntu 10.10 and ran several tests with different serial >> adapters and a virtual interface: pl2303 ( http://pastebin.com/0B2CdyYZ ), >> FT232RL ( http://pastebin.com/Wb4Yq1r6 ) and socat ( >> http://pastebin.com/uFCVtCgc ). Everything works as it should. >> >> I can not reproduce the bug. I think the best for now would be to continue >> the development and make a public release and see if anyone else has this >> problem, as now there is a huge lack of testing feedback. >> >> P.S. for socat I used: socat -d -d pty,raw,echo=0, pty,raw,echo=0 >> >> Best Regards, >> >> On Thu, Aug 16, 2012 at 1:21 AM, Juan Pablo Carbajal <car...@if...> >> wrote: >>> >>> On Thu, Aug 16, 2012 at 1:59 AM, Andrius Sutas <and...@gm...> >>> wrote: >>> > Hi Juan, >>> > >>> > that is really strange. I fired up an Ubuntu VM (vmware) based on your >>> > previous post for testing: >>> > >>> > andrew@ubuntu:~$ lsb_release -a >>> > No LSB modules are available. >>> > Distributor ID: Ubuntu >>> > Description: Ubuntu 10.04.4 LTS >>> > Release: 10.04 >>> > Codename: lucid >>> > andrew@ubuntu:~$ uname -a >>> > Linux ubuntu 2.6.32-42-generic #95-Ubuntu SMP Wed Jul 25 15:56:09 UTC >>> > 2012 >>> > x86_64 GNU/Linux >>> > andrew@ubuntu:~$ gcc --version >>> > gcc (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3 >>> > andrew@ubuntu:~$ octave --version >>> > GNU Octave, version 3.2.3 >>> > >>> > Everything works as expected: http://pastebin.com/E9DMVeVt >>> > >>> > What I noticed is that it takes a few seconds to open the interface in >>> > VM, >>> > which happens virtually instantaneously on my host (Arch Linux, Kernel >>> > 3.4.8), need to investigate if that is distribution or VM related. >>> > >>> > Could you provide more details about your environment for further >>> > debugging? >>> > Also, is there any related output to dmesg when octave hangs? >>> > >>> > On Wed, Aug 15, 2012 at 3:04 PM, Juan Pablo Carbajal >>> > <car...@if...> >>> > wrote: >>> >> >>> >> On Mon, Aug 13, 2012 at 11:45 AM, Andrius Sutas >>> >> <and...@gm...> >>> >> wrote: >>> >> > s = serial(sif, 115200, 0); srl_flush(s) ; srl_write(s, "Hello!"); >>> >> > sleep >>> >> > ( >>> >> > 0.2 ); tic(); [data, count] = srl_read(s, 10); toc(); char(data), >>> >> > count, >>> >> > srl_close(s); >>> >> >>> >> Hi Andrius, >>> >> >>> >> I tested the new version of the package you send (and the one in svn) >>> >> and all examples except the first one hang my Octave completely. It >>> >> seems the timeout is not working here. To cancel execution I have to >>> >> do twice Ctrl-C (this closes Octave). >>> >> >>> >> What can it be? >>> >> >>> >> >>> >> -- >>> >> M. Sc. Juan Pablo Carbajal >>> >> ----- >>> >> PhD Student >>> >> University of Zürich >>> >> http://ailab.ifi.uzh.ch/carbajal/ >>> > >>> > >>> >>> Hi, >>> Sorry, I am running 10.10 >>> >>> $ lsb_release -a >>> LSB Version: >>> core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch >>> Distributor ID: Ubuntu >>> Description: Ubuntu 10.10 >>> Release: 10.10 >>> Codename: maverick >>> >>> Please, suggest any test that I can run to help solving the problem. >>> >>> -- >>> M. Sc. Juan Pablo Carbajal >>> ----- >>> PhD Student >>> University of Zürich >>> http://ailab.ifi.uzh.ch/carbajal/ >> >> > > Andrius, > > That sounds ok! > > However, you need to document your functions before we can do a public > release. That is probably the only one strict condition in OF (and > Agora in the future). > > All your functions give "Hello World Help String" when using the command "help". > > Good documentation, imho has the following: > 1. A short description of the file (1 sentence) > 2. A description explaining what the function is meant to do. > 3. Explanations of inputs and outputs. > 4. Examples > 5. Demos > > Number 5 may be impossible in your case since to run demos you need to > open a serial port and I guess that is hard to automatically find in a > random machine. Check the help of core functions (like sqp) or in the > control package. > > Cheers > > > -- > M. Sc. Juan Pablo Carbajal > ----- > PhD Student > University of Zürich > http://ailab.ifi.uzh.ch/carbajal/ btw, You can use Agora for pasting code and output http://agora.octave.org/ -- M. Sc. Juan Pablo Carbajal ----- PhD Student University of Zürich http://ailab.ifi.uzh.ch/carbajal/ |
541 messages has been excluded from this view by a project administrator.
