octave-dev — GNU Octave developers' list

Re: [OctDev] On the union of two communities - The GNU Octave atmosphere

[Júlio H. <jul...@gm...>]

Agora is a good place to discuss about the packages, missing
implementations, feature requests: the community feedback. But i still
think the development efforts should be united in a single main repository,
and people decide in what parts they can help.

By the way, Agora is very beautiful.

Júlio.

Re: [OctDev] On the union of two communities - The GNU Octave atmosphere

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

On 15 Sep 2012, at 12:18, Júlio Hoffimann wrote:

> Octave Forge packages on the other hand are much more like MATLAB Toolboxes, they're developed by MathWorks itself, and are part of the software atmosphere, really.
by the way:

1) Most Octave Forge packages are not currently developed by Octave developers

2) Not all Matlab toolboxes are developed by the Mathworks

Having toolboxes sold separately makes sense in the proprietary software world where
it has the purpose of asking users to by additional licenses.

As Octave is free software this makes little sense, if you think the functionality of
some package is of general interest to all Octave users, and there is an implementation
that meets Octaves quality standards then you might just want to propose to add that
functionality directly into Octave.

c.

Re: [OctDev] On the union of two communities - The GNU Octave atmosphere

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

On 15 Sep 2012, at 12:18, Júlio Hoffimann wrote:

> I see Agora as another level of contribution, namely http://www.mathworks.com/matlabcentral/.
> 
> In which users can submit small snippets of code, little functions and doesn't have to even know about coding standards - non-reviewed submissions. A place for users interact by submitting content of any kind, including blog posts, code, feature requests, discussions, etc.
> 
> Octave Forge packages on the other hand are much more like MATLAB Toolboxes, they're developed by MathWorks itself, and are part of the software atmosphere, really.

this is sort of the same difference we envision between different parts of Agora
it should be formed of 

1) contributions from independent developers either in the form of single files or full packages 
that are simply "dumped" on agora so users can download them (similar to matlabcentral but with more
stress on freedom, thus no restrictive terms of use)

2) a set of "core" packages developed/maintained by (or in strict collaboration with) developers of 
Octave itself, following GNU coding and licensing directives.

This latter part will probably be named "the Forge" or something similar and sounds to me like it
is very similar to what you are asking for.
Suggestions regarding which packages should be part of the Forge have been collected on this list
some time ago, I'm sure you'll find them if you google for it.

> Júlio.
c.

Re: [OctDev] On the union of two communities - The GNU Octave atmosphere

[Júlio H. <jul...@gm...>]

>
> This post on Carnë's blog summarizes the discussion about
> Octave/Octave-Forge/Agora
> at OctConf2012. A preview of Agora is here http://agora.octave.org/.
>
> HTH,
> c.
>

I see Agora as another level of contribution, namely
http://www.mathworks.com/matlabcentral/.

In which users can submit small snippets of code, little functions and
doesn't have to even know about coding standards - non-reviewed
submissions. A place for users interact by submitting content of any kind,
including blog posts, code, feature requests, discussions, etc.

Octave Forge packages on the other hand are much more like MATLAB
Toolboxes, they're developed by MathWorks itself, and are part of the
software atmosphere, really.

Júlio.

[OctDev] optim-1.2.1

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

Hi,

optim-1.2.1 has been uploaded to the release tracker. This is a bugfix
release, leasqr had not been normally usable if another package
provided a function with a certain name.

Olaf

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

Re: [OctDev] problems uploading package

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

On Sat, Sep 15, 2012 at 11:23:22AM +0200, c. wrote:
> 
> On 15 Sep 2012, at 00:20, Olaf Till wrote:
> 
> > Hi,
> > 
> > I seem to be unable to use the new package release tracker referenced
> > by the developer section of the OF website.
> > 
> > First, it seems to accept only one attachment per post ... ?
> 
> no, there is a (very well hidden) link to add another file.
> it's on the left hand side of the page, coluored in gray and
> doesn't look like a link as even if you pass the pointer over it
> it does change color.

Thanks.

> > Second, it requires splitting packages into files <= 256K.
> > 
> > Worse, even if thus splitted, or even into files <= 256000 bytes, it
> > still does not accept a single chunk and pretends the file is > 256K.
> 
> yes this is a very strict limitation. For the time being, as long as we 
> can't find anything better, if the file is too big just upload the package
> elswhere and post a link on the tracker.

Since I have no other place to upload, I tried the tracker again with
a split to chunks of 250000 bytes, and luckily it accepted these. At
least I could upload the 5 chunks without hitting a limit in the
number of attached files. Thanks for the help.

I'll make the announcement in a separate thread.

Olaf

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

Re: [OctDev] problems uploading package

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

On 15 Sep 2012, at 00:20, Olaf Till wrote:

> Hi,
> 
> I seem to be unable to use the new package release tracker referenced
> by the developer section of the OF website.
> 
> First, it seems to accept only one attachment per post ... ?

no, there is a (very well hidden) link to add another file.
it's on the left hand side of the page, coluored in gray and
doesn't look like a link as even if you pass the pointer over it
it does change color.

> Second, it requires splitting packages into files <= 256K.
> 
> Worse, even if thus splitted, or even into files <= 256000 bytes, it
> still does not accept a single chunk and pretends the file is > 256K.

yes this is a very strict limitation. For the time being, as long as we 
can't find anything better, if the file is too big just upload the package
elswhere and post a link on the tracker.

> Olaf
c.

Re: [OctDev] On the union of two communities - The GNU Octave atmosphere

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

On 15 Sep 2012, at 10:52, Philip Nienhuis wrote:

> Daniel J Sebald wrote:
>> On 09/14/2012 06:53 PM, Júlio Hoffimann wrote:
>>> Hi Daniel,
>>> 
>>>     There are three, maybe four levels of Octave code:
>>> 
>>>     1) Core Octave written in C++ (i.e., compiled code)
>>>     2) Commonly-used, moderately-general m-scripts (i.e., interpreted code)
>>>     3) Compiled or scripted code related to user interface, whether that
>>>     be a graphics engine, GUI/IDE, etc.
>>>     4) Voluminous packages of field-related m-scripts
>>> 
>>> 
>>> Thanks for your reply. These levels are familiar to me, i'm contributing
>>> with very little patches when i have time.
>>> 
>>> This week i started to use Octave Forge, precisely the optimization
>>> package. I found some missing headers during the installation and wanted
>>> to submit another patch as usual, but then i realized i should clone
>>> another repository, find another bug track system, subscribe to another
>>> mailing list to discuss about it. I said to myself, this is wrong, let's
>>> make it better.
>> 
>> I understand that, and this confusion may have been one of the
>> motivations for the conversation at OctConf 2012.  It stems from the
>> choice of name Octave Forge, which is similar to the name SourceForge
>> (whether that is the reason for the name, I'm not sure), and if I'm
>> remembering correctly Octave development too may have been on
>> SourceForge at one time.
>> 
>> Even though the web pages for Octave and OctaveForge are fairly well
>> organized, they might not be so descriptive about the relationship
>> between the two.  For example, on the main page
>> 
>> http://octave.sourceforge.net/
>> 
>> it states "Octave-Forge is a central location for the collaborative
>> development of packages for GNU Octave."  Nothing there implies
>> Octave-Forge is closely tied in with the Octave core code
> <snip>
> 
> Moreover, nothing on the main Octave web pages (www.octave.org) mentions 
> Octave-Forge anywhere, nor octave.sf.net, nor even the fact that add-on 
> packages for Octave exist at all and can be found on Sourceforge uhm..., 
> Octave-Forge.
> 
> Only indirectly, on the wiki linked to from the "Support" page, one can 
> find the first casual mention of add-on packages.
> 
> IMO this setup was a community decision at the time so I never bothered 
> much.
> 
> Philip


This post on Carnë's blog summarizes the discussion about Octave/Octave-Forge/Agora
at OctConf2012. A preview of Agora is here http://agora.octave.org/.

HTH,
c.

Re: [OctDev] On the union of two communities - The GNU Octave atmosphere

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

Daniel J Sebald wrote:
> On 09/14/2012 06:53 PM, Júlio Hoffimann wrote:
>> Hi Daniel,
>>
>>      There are three, maybe four levels of Octave code:
>>
>>      1) Core Octave written in C++ (i.e., compiled code)
>>      2) Commonly-used, moderately-general m-scripts (i.e., interpreted code)
>>      3) Compiled or scripted code related to user interface, whether that
>>      be a graphics engine, GUI/IDE, etc.
>>      4) Voluminous packages of field-related m-scripts
>>
>>
>> Thanks for your reply. These levels are familiar to me, i'm contributing
>> with very little patches when i have time.
>>
>> This week i started to use Octave Forge, precisely the optimization
>> package. I found some missing headers during the installation and wanted
>> to submit another patch as usual, but then i realized i should clone
>> another repository, find another bug track system, subscribe to another
>> mailing list to discuss about it. I said to myself, this is wrong, let's
>> make it better.
>
> I understand that, and this confusion may have been one of the
> motivations for the conversation at OctConf 2012.  It stems from the
> choice of name Octave Forge, which is similar to the name SourceForge
> (whether that is the reason for the name, I'm not sure), and if I'm
> remembering correctly Octave development too may have been on
> SourceForge at one time.
>
> Even though the web pages for Octave and OctaveForge are fairly well
> organized, they might not be so descriptive about the relationship
> between the two.  For example, on the main page
>
> http://octave.sourceforge.net/
>
> it states "Octave-Forge is a central location for the collaborative
> development of packages for GNU Octave."  Nothing there implies
> Octave-Forge is closely tied in with the Octave core code
<snip>

Moreover, nothing on the main Octave web pages (www.octave.org) mentions 
Octave-Forge anywhere, nor octave.sf.net, nor even the fact that add-on 
packages for Octave exist at all and can be found on Sourceforge uhm..., 
Octave-Forge.

Only indirectly, on the wiki linked to from the "Support" page, one can 
find the first casual mention of add-on packages.

IMO this setup was a community decision at the time so I never bothered 
much.

Philip

Re: [OctDev] inputname and function(cell{:})

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

On 14.09.2012, at 15:46, Jordi Gutiérrez Hermoso <jo...@oc...> wrote:

> On 14 September 2012 09:30, Lukas Reichlin
> <luk...@gm...> wrote:
>> Currently, with
>> 
>>        ret1 = testfun (arg1, arg2, arg3)
>> 
>> nargin is 3 and inputname ranges from 1 to 3.
>> But with
>> 
>>        ret2 = testfun (args{:})
>> 
>> nargin is still 3 but only inputname(1) exists while inputname(2)
>> and inputname(3) give errors.
> 
> But if you're passing a cs-list, the cs-list itself doesn't have the
> variable names that you want, and inputname is working as documented,
> returning an empty string.
> 
>> Therefore I must find an alternative to inputname or an alternative
>> to nargin which counts input arguments the same way as inputname
>> does. Do you know how to circumvent this problem?
> 
> What exactly is your actual problem? nargin still counts arguments,
> but why do you want to know what the variables are called in the
> calling function? The calling function doesn't have this information
> when you use a cs-list. To me this seems like premature closure or an
> X-Y problem:
> 
>    http://www.perlmonks.org/index.pl?node_id=542341
> 
> Can you give broader context in order to be able to give you a better
> answer? There may be a completely differenty way to solve your broader
> problem.
> 
> - Jordi G. H.

Hi Jordi

Thanks for your quick reply! The broader context is given on line 92 of MDSSystem2.m [1]

	bode (G_per{:}, w)

G_per is a cell of LTI models to be plotted by bode. The bode function generates an automatic legend with the argument names given by the inputname function. On line 91 in bode.m [2]

	legend_args{k} = inputname(sys_idx(k));  # watch out for bode (lticell{:})

I'm trying to get the argument names. However, only inputname(1) and inputname(2) work because bode (G_per{:}, w) has only two arguments. But since G_per contains about a dozen LTI systems, nargin = numel (G_per) + 1 (+1 because of argument w). Here inputname(n) for n>2 is failing. Therefore I need a way to find out how many inputnames were given (nargin doesn't work) so I can stop before inputname(n) fails. (counting the inputs like inputname, instead of a try-catch block)

Best regards,
Lukas


[1] MDSSystem2.m
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/control/devel/MDSSystem2.m?revision=11015&view=markup


[2] bode.m
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/control/inst/bode.m?revision=11025&view=markup

Re: [OctDev] On the union of two communities - The GNU Octave atmosphere

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

On 09/14/2012 06:53 PM, Júlio Hoffimann wrote:
> Hi Daniel,
>
>     There are three, maybe four levels of Octave code:
>
>     1) Core Octave written in C++ (i.e., compiled code)
>     2) Commonly-used, moderately-general m-scripts (i.e., interpreted code)
>     3) Compiled or scripted code related to user interface, whether that
>     be a graphics engine, GUI/IDE, etc.
>     4) Voluminous packages of field-related m-scripts
>
>
> Thanks for your reply. These levels are familiar to me, i'm contributing
> with very little patches when i have time.
>
> This week i started to use Octave Forge, precisely the optimization
> package. I found some missing headers during the installation and wanted
> to submit another patch as usual, but then i realized i should clone
> another repository, find another bug track system, subscribe to another
> mailing list to discuss about it. I said to myself, this is wrong, let's
> make it better.

I understand that, and this confusion may have been one of the 
motivations for the conversation at OctConf 2012.  It stems from the 
choice of name Octave Forge, which is similar to the name SourceForge 
(whether that is the reason for the name, I'm not sure), and if I'm 
remembering correctly Octave development too may have been on 
SourceForge at one time.

Even though the web pages for Octave and OctaveForge are fairly well 
organized, they might not be so descriptive about the relationship 
between the two.  For example, on the main page

http://octave.sourceforge.net/

it states "Octave-Forge is a central location for the collaborative 
development of packages for GNU Octave."  Nothing there implies 
Octave-Forge is closely tied in with the Octave core code, but I realize 
those unfamiliar with the setup come to an introduction believe there 
is.  In the developers description is:

http://octave.sourceforge.net/developers.html

"To contribute your .m files, C++, C, or Fortran code to the GNU Octave 
Repository (octave-forge) you need to" which doesn't add clarity and 
slightly obfuscates because of the phrase "GNU Octave Repository". 
Maybe one concludes "repository for GNU Octave" in the sense that is 
were GNU Octave is.  A better phrasing might be "repository of packages 
that run under GNU Octave", or "repository for GNU Octave compatible 
packages".

Can you think of any way the initial introduction could have been made 
more straightforward?

Dan

Re: [OctDev] On the union of two communities - The GNU Octave atmosphere

[Júlio H. <jul...@gm...>]

Hi Daniel,


> There are three, maybe four levels of Octave code:
>
> 1) Core Octave written in C++ (i.e., compiled code)
> 2) Commonly-used, moderately-general m-scripts (i.e., interpreted code)
> 3) Compiled or scripted code related to user interface, whether that be a
> graphics engine, GUI/IDE, etc.
> 4) Voluminous packages of field-related m-scripts
>

Thanks for your reply. These levels are familiar to me, i'm contributing
with very little patches when i have time.

This week i started to use Octave Forge, precisely the optimization
package. I found some missing headers during the installation and wanted to
submit another patch as usual, but then i realized i should clone another
repository, find another bug track system, subscribe to another mailing
list to discuss about it. I said to myself, this is wrong, let's make it
better.

And now i'm here asking if we can do it.


A bit off topic, but on the matter of toxic gases, society can make urban
> centers that are livable, which helps preserve natural spaces.  It doesn't
> have to be one and the other.
>

I tried to refer to the culture around another software, a toxic software.
:)

Júlio.

[OctDev] problems uploading package

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

Hi,

I seem to be unable to use the new package release tracker referenced
by the developer section of the OF website.

First, it seems to accept only one attachment per post ... ?

Second, it requires splitting packages into files <= 256K.

Worse, even if thus splitted, or even into files <= 256000 bytes, it
still does not accept a single chunk and pretends the file is > 256K.

Olaf

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

Re: [OctDev] On the union of two communities - The GNU Octave atmosphere

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

On 09/14/2012 02:45 PM, Júlio Hoffimann wrote:
> Dear all,
>

> I'm here to purpose the union of these two important communities (Core
> and Forge), to eliminate this strong separation that makes devs/users
> lives much more difficult. We can make the GNU Octave atmosphere even
> richer and minimize the losses, as nature does.
>
> I don't see reasons to maintain two mailing lists, two disconnected
> repositories, two communities. After all, we're all doing our best to
> provide what we think is useful to us and to others.
>
> Being concrete, what do you think in gradually absorb Octave Forge
> packages into Octave main repo as subrepos? This would require an
> effective collaboration to review the packages, to purge redundancies
> (reimplementation) and i'm here to help, just to mention!
>
> People interested in contribute to the Forge packages would just do it
> inside the main Octave repo, inside a subdirectory. Forge maintainers
> would have total access to the subrepo contributing exactly the same way
> they contribute today, with the difference they would be closer to the
> core, which is great.
>
> The builds would be completely independent, we would just add targets to
> the packages (make forge, make forge-optim, ...).
>
> Please, put all the individual feelings aside and think as a community.
> I'm glad to be part of it.
>
> Best regards,
> Júlio.

Júlio,

The OctaveForge repositories was a discussion item at OctConf 2012. 
Opinions are varied, but I'll try summarizing.

First, I don't think there is the great divide that you are suggesting. 
  There is an OctaveForge repository separate from the core of Octave 
for a few reasons.  Probably the most salient reason is the fact the 
whole project becomes difficult to manage if the core of Octave and all 
the packages are combined into one.  I think there may have been a time 
when scripts were organized and combined with Octave, then it became too 
much and people thought a packaging system was needed.  Mailing lists 
re-arranged quite a bit as well, at first being narrow, then splitting 
into specific function which became irrelevant as some of the mailing 
lists got little traffic.  Development has sort of evolved into the 
current arrangement that seems to function well enough for the time being.

There are three, maybe four levels of Octave code:

1) Core Octave written in C++ (i.e., compiled code)
2) Commonly-used, moderately-general m-scripts (i.e., interpreted code)
3) Compiled or scripted code related to user interface, whether that be 
a graphics engine, GUI/IDE, etc.
4) Voluminous packages of field-related m-scripts

The first level needs to be extremely efficient and well organized code. 
  Being part of GNU software, it must also ensure that licenses are 
observed properly.  Up to this point, the main Octave maintainers (i.e., 
those most active and productive...and those most active has changed 
over the history of the project with people coming and going on the 
basis of available time) had to focus on levels 1 and 2 with blinders to 
levels 3 and 4, otherwise they wouldn't have been so productive.  If one 
were to look, I think they'd find that the most active people on the 
maintainers email list (emails and coding) are the least active on the 
OctDev list, aside from an occasional post to clear up some detail.

At level four the packages are associated with diverse fields with 
contributions from many.  Efficiency, correctness and such just doesn't 
get the robust scrutiny that the code maintained in the core does.


> Before entering the atmosphere, i want to thank you all from outside, as
> an external admirer. You all did a great job providing a free
> alternative (pick any interpretation) for scientists explore the
> boundaries of knowledge with no constraints on what they can or cannot
> do with the tools in hand. Thank you.
>
> Now let's dive in with the minds open, forget the past because it
> doesn't alter anything...
>
> I can smell two types of air. One is more dense, full in substratum, in
> fact it occurs in deeper layers, close to the core where we can find a
> rich environment with beautiful (parser) trees, birds, ... It's
> refreshing. The second can only be smelled on high mountains, and lucky
> are the ones who had the opportunity to feel this sensation.
>
> As a adventurer, i would like to share this sensation with my friends,
> but due to the altitude and faraway places they always give up in
> joining this journey. I insist to them the air found in the mountains is
> sublime, but it's hard to convince people when they are under the effect
> of toxic gases produced in urban centers.

A bit off topic, but on the matter of toxic gases, society can make 
urban centers that are livable, which helps preserve natural spaces.  It 
doesn't have to be one and the other.

Dan

Re: [OctDev] optim package on Windows doesn't install

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

On Fri, Sep 14, 2012 at 10:20:27AM -0700, gregid wrote:
> Thanks ninit,
> 
> Your patch did help. But being new to makefile it took me some time to
> figure out that "+" and "-" are not part of the makefile syntax but source
> control :D
> 
> Could this patch be applied to sourceforge or will it cause compatibility
> issues on other systems?

No, this patch can not be applied to the central repository. Instead,
the mingw built should be fixed to make mkoctfile return the correct
flags.

Olaf

> Thanks again guys
> 
> On 14 September 2012 07:53, nitnit [via Octave] <
> ml-...@n4...> wrote:
> 
> >  gregid wrote
> > I tried to install optim package downloaded from forge website, -forge,
> > and svn trunk download.
> > All with the same result. Any advice on how to fix it? Anyone else having
> > similar problem?
> >
> > octave:117> pkg install -forge optim
> > __disna_optim__.o: In function
> > `Z16F__disna_optim__RK17octave_value_listi':
> > C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:132:
> > undefined reference to `sdisna_'
> > C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:144:
> > undefined reference to `ddisna_'
> > collect2: ld returned 1 exit status
> >
> > For my recent mingw built of the optim pkg, I had to add the "-lliblapack"
> > implicitly since it has not been returned by mkoctfile -p. See following
> > patch.
> >
> > Regards
> > Nitzan
> >
> > --- optim-1.2.0.tar.gz\optim-1.2.0\src\Makefile Tue Jun 12 16:42:55 2012
> > +++ optim-1.2.0_patched.tar.gz\optim-1.2.0\src\Makefile Sat Aug 04
> > 11:27:03 2012
> > @@ -1,9 +1,11 @@
> >  MKOCTFILE ?= mkoctfile
> >
> >  ifndef LAPACK_LIBS
> > -LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
> > +# LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
> > +LAPACK_LIBS := -lliblapack
> >  endif
> > -OCTAVE_LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
> > +# OCTAVE_LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
> > +OCTAVE_LAPACK_LIBS := -lliblapack
> >  # reported necessary for Apple's VecLib framework by Carlo de Falco
> >  # <car...@gm...>
> >  ifndef BLAS_LIBS
> >
> >
> > ------------------------------
> >  If you reply to this email, your message will be added to the discussion
> > below:
> >
> > http://octave.1599824.n4.nabble.com/optim-package-on-Windows-doesn-t-install-tp4644095p4644100.html
> >  To unsubscribe from optim package on Windows doesn't install, click here<http://octave.1599824.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4644095&code=Z3RyemVjaWFrQGdtYWlsLmNvbXw0NjQ0MDk1fC0xMDY1ODEwNzQx>
> > .
> > NAML<http://octave.1599824.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >
> 
> 
> 
> 
> --
> View this message in context: http://octave.1599824.n4.nabble.com/optim-package-on-Windows-doesn-t-install-tp4644095p4644112.html
> Sent from the Octave - Dev mailing list archive at Nabble.com.

> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html

> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev


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

[OctDev] On the union of two communities - The GNU Octave atmosphere

[Júlio H. <jul...@gm...>]

Dear all,

Before entering the atmosphere, i want to thank you all from outside, as an
external admirer. You all did a great job providing a free alternative
(pick any interpretation) for scientists explore the boundaries of
knowledge with no constraints on what they can or cannot do with the tools
in hand. Thank you.

Now let's dive in with the minds open, forget the past because it doesn't
alter anything...

I can smell two types of air. One is more dense, full in substratum, in
fact it occurs in deeper layers, close to the core where we can find a rich
environment with beautiful (parser) trees, birds, ... It's refreshing. The
second can only be smelled on high mountains, and lucky are the ones who
had the opportunity to feel this sensation.

As a adventurer, i would like to share this sensation with my friends, but
due to the altitude and faraway places they always give up in joining this
journey. I insist to them the air found in the mountains is sublime, but
it's hard to convince people when they are under the effect of toxic gases
produced in urban centers.

I'm here to purpose the union of these two important communities (Core and
Forge), to eliminate this strong separation that makes devs/users lives
much more difficult. We can make the GNU Octave atmosphere even richer and
minimize the losses, as nature does.

I don't see reasons to maintain two mailing lists, two disconnected
repositories, two communities. After all, we're all doing our best to
provide what we think is useful to us and to others.

Being concrete, what do you think in gradually absorb Octave Forge packages
into Octave main repo as subrepos? This would require an effective
collaboration to review the packages, to purge redundancies
(reimplementation) and i'm here to help, just to mention!

People interested in contribute to the Forge packages would just do it
inside the main Octave repo, inside a subdirectory. Forge maintainers would
have total access to the subrepo contributing exactly the same way they
contribute today, with the difference they would be closer to the core,
which is great.

The builds would be completely independent, we would just add targets to
the packages (make forge, make forge-optim, ...).

Please, put all the individual feelings aside and think as a community. I'm
glad to be part of it.

Best regards,
Júlio.

Re: [OctDev] optim package on Windows doesn't install

[gregid <gtr...@gm...>]

Thanks ninit,

Your patch did help. But being new to makefile it took me some time to
figure out that "+" and "-" are not part of the makefile syntax but source
control :D

Could this patch be applied to sourceforge or will it cause compatibility
issues on other systems?

Thanks again guys

On 14 September 2012 07:53, nitnit [via Octave] <
ml-...@n4...> wrote:

>  gregid wrote
> I tried to install optim package downloaded from forge website, -forge,
> and svn trunk download.
> All with the same result. Any advice on how to fix it? Anyone else having
> similar problem?
>
> octave:117> pkg install -forge optim
> __disna_optim__.o: In function
> `Z16F__disna_optim__RK17octave_value_listi':
> C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:132:
> undefined reference to `sdisna_'
> C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:144:
> undefined reference to `ddisna_'
> collect2: ld returned 1 exit status
>
> For my recent mingw built of the optim pkg, I had to add the "-lliblapack"
> implicitly since it has not been returned by mkoctfile -p. See following
> patch.
>
> Regards
> Nitzan
>
> --- optim-1.2.0.tar.gz\optim-1.2.0\src\Makefile Tue Jun 12 16:42:55 2012
> +++ optim-1.2.0_patched.tar.gz\optim-1.2.0\src\Makefile Sat Aug 04
> 11:27:03 2012
> @@ -1,9 +1,11 @@
>  MKOCTFILE ?= mkoctfile
>
>  ifndef LAPACK_LIBS
> -LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
> +# LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
> +LAPACK_LIBS := -lliblapack
>  endif
> -OCTAVE_LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
> +# OCTAVE_LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
> +OCTAVE_LAPACK_LIBS := -lliblapack
>  # reported necessary for Apple's VecLib framework by Carlo de Falco
>  # <car...@gm...>
>  ifndef BLAS_LIBS
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://octave.1599824.n4.nabble.com/optim-package-on-Windows-doesn-t-install-tp4644095p4644100.html
>  To unsubscribe from optim package on Windows doesn't install, click here<http://octave.1599824.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4644095&code=Z3RyemVjaWFrQGdtYWlsLmNvbXw0NjQ0MDk1fC0xMDY1ODEwNzQx>
> .
> NAML<http://octave.1599824.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://octave.1599824.n4.nabble.com/optim-package-on-Windows-doesn-t-install-tp4644095p4644112.html
Sent from the Octave - Dev mailing list archive at Nabble.com.

Re: [OctDev] inputname and function(cell{:})

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

On 14 September 2012 09:30, Lukas Reichlin
<luk...@gm...> wrote:
> Currently, with
>
>         ret1 = testfun (arg1, arg2, arg3)
>
> nargin is 3 and inputname ranges from 1 to 3.
> But with
>
>         ret2 = testfun (args{:})
>
> nargin is still 3 but only inputname(1) exists while inputname(2)
> and inputname(3) give errors.

But if you're passing a cs-list, the cs-list itself doesn't have the
variable names that you want, and inputname is working as documented,
returning an empty string.

> Therefore I must find an alternative to inputname or an alternative
> to nargin which counts input arguments the same way as inputname
> does. Do you know how to circumvent this problem?

What exactly is your actual problem? nargin still counts arguments,
but why do you want to know what the variables are called in the
calling function? The calling function doesn't have this information
when you use a cs-list. To me this seems like premature closure or an
X-Y problem:

    http://www.perlmonks.org/index.pl?node_id=542341

Can you give broader context in order to be able to give you a better
answer? There may be a completely differenty way to solve your broader
problem.

- Jordi G. H.

[OctDev] inputname and function(cell{:})

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

Dear Octave Community

I'm preparing multiplot-capable plotting functions for the control package. I ran into a problem which boils down to the code in the attached example. I'd like to get the inputnames of all arguments of a function "testfun".

Currently, with

	ret1 = testfun (arg1, arg2, arg3)

nargin is 3 and inputname ranges from 1 to 3.
But with

	ret2 = testfun (args{:})

nargin is still 3 but only inputname(1) exists while inputname(2) and inputname(3) give errors. Therefore I must find an alternative to inputname or an alternative to nargin which counts input arguments the same way as inputname does. Do you know how to circumvent this problem?

Thanks for any help and best regards,
Lukas

Re: [OctDev] optim package on Windows doesn't install

[nitnit <ni...@gm...>]

gregid wrote
> 
> I tried to install optim package downloaded from forge website, -forge,
> and svn trunk download.
> All with the same result. Any advice on how to fix it? Anyone else having
> similar problem?
> 
> octave:117> pkg install -forge optim
> __disna_optim__.o: In function
> `Z16F__disna_optim__RK17octave_value_listi':
> C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:132:
> undefined reference to `sdisna_'
> C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:144:
> undefined reference to `ddisna_'
> collect2: ld returned 1 exit status
> 
> 

For my recent mingw built of the optim pkg, I had to add the "-lliblapack"
implicitly since it has not been returned by mkoctfile -p. See following
patch.

Regards
Nitzan

--- optim-1.2.0.tar.gz\optim-1.2.0\src\Makefile	Tue Jun 12 16:42:55 2012
+++ optim-1.2.0_patched.tar.gz\optim-1.2.0\src\Makefile	Sat Aug 04 11:27:03
2012
@@ -1,9 +1,11 @@
 MKOCTFILE ?= mkoctfile
 
 ifndef LAPACK_LIBS
-LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
+# LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
+LAPACK_LIBS := -lliblapack
 endif
-OCTAVE_LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
+# OCTAVE_LAPACK_LIBS := $(shell $(MKOCTFILE) -p LAPACK_LIBS)
+OCTAVE_LAPACK_LIBS := -lliblapack
 # reported necessary for Apple's VecLib framework by Carlo de Falco
 # <car...@gm...>
 ifndef BLAS_LIBS




--
View this message in context: http://octave.1599824.n4.nabble.com/optim-package-on-Windows-doesn-t-install-tp4644095p4644100.html
Sent from the Octave - Dev mailing list archive at Nabble.com.

Re: [OctDev] optim package on Windows doesn't install

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

On 13 September 2012 19:15, gregid <gtr...@gm...> wrote:
> I tried to install optim package downloaded from forge website, -forge, and
> svn trunk download.
> All with the same result. Any advice on how to fix it? Anyone else having
> similar problem?

You don't need to compile the package yourself. It's already been compiled:

http://sourceforge.net/projects/octave/files/Octave%20Windows%20binaries/Octave%203.6.2%20for%20Windows%20MinGW%20installer/

Get the one that says "pkgs".

HTH,
- Jordi G. H.

Re: [OctDev] optim package on Windows doesn't install

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

On 09/13/2012 06:15 PM, gregid wrote:
> I tried to install optim package downloaded from forge website, -forge, and
> svn trunk download.
> All with the same result. Any advice on how to fix it? Anyone else having
> similar problem?

The optim package appears to not have been touched for 3 months, so I 
doubt it is something in the package.  I notice that the globals that 
are being complained about are F77 routines.  See the code here:

http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/optim/src/__disna_optim__.cc?revision=10116&view=markup

and that they are in the LAPACK.

/*
48 	Interface to DDISNA and SDISNA of LAPACK.
52 	*/

Do you have LAPACK available?  The module appears to be trying to piece 
things together.

Dan


>
> octave:117>  pkg install -forge optim
> __disna_optim__.o: In function `Z16F__disna_optim__RK17octave_value_listi':
> C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:132:
> undefined reference to `sdisna_'
> C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:144:
> undefined reference to `ddisna_'
> collect2: ld returned 1 exit status
> strip: '__disna_optim__.oct': No such file
> make: *** [__disna_optim__.oct] Error 1
> 'make' returned the following error: make: Entering directory
> `/tmp/oct-24/optim-1.2.0/src'
> LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
> -Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
> 3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s __bfgsmin.cc
> LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
> -Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
> 3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s numgradient.cc
> LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
> -Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
> 3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s numhessian.cc
> LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
> -Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
> 3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s samin.cc
> LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
> -Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
> 3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s __disna_optim__.cc
> make: Leaving directory `/tmp/oct-24/optim-1.2.0/src'
> error: called from `pkg>configure_make' in file
> C:\Octave\Octave3.6.2_gcc4.6.2\share\octave\3.6.2\m\pkg\pkg.m near line
> 1385, column 9
> error: called from:
> error:   C:\Octave\Octave3.6.2_gcc4.6.2\share\octave\3.6.2\m\pkg\pkg.m at
> line 827, column 5
> error:   C:\Octave\Octave3.6.2_gcc4.6.2\share\octave\3.6.2\m\pkg\pkg.m at
> line 383, column 9
>
>
>
> --
> View this message in context: http://octave.1599824.n4.nabble.com/optim-package-on-Windows-doesn-t-install-tp4644095.html
> Sent from the Octave - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://ad.doubleclick.net/clk;258768047;13503038;j?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
>

-- 

Dan Sebald
email: daniel(DOT)sebald(AT)ieee(DOT)org
URL: http://www(DOT)dansebald(DOT)com

[OctDev] optim package on Windows doesn't install

[gregid <gtr...@gm...>]

I tried to install optim package downloaded from forge website, -forge, and
svn trunk download.
All with the same result. Any advice on how to fix it? Anyone else having
similar problem?

octave:117> pkg install -forge optim
__disna_optim__.o: In function `Z16F__disna_optim__RK17octave_value_listi':
C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:132:
undefined reference to `sdisna_'
C:\Users\Me\AppData\Local\Temp\oct-24\optim-1.2.0\src/__disna_optim__.cc:144:
undefined reference to `ddisna_'
collect2: ld returned 1 exit status
strip: '__disna_optim__.oct': No such file
make: *** [__disna_optim__.oct] Error 1
'make' returned the following error: make: Entering directory
`/tmp/oct-24/optim-1.2.0/src'
LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s __bfgsmin.cc
LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s numgradient.cc
LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s numhessian.cc
LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s samin.cc
LFLAGS="-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib\octave\3.6.2
-Lc:\Octave\Octave3.6.2_gcc4.6.2\lib  -lblas" C:/Octave/Octave
3.6.2_gcc4.6.2/bin/mkoctfile-3.6.2 -s __disna_optim__.cc
make: Leaving directory `/tmp/oct-24/optim-1.2.0/src'
error: called from `pkg>configure_make' in file
C:\Octave\Octave3.6.2_gcc4.6.2\share\octave\3.6.2\m\pkg\pkg.m near line
1385, column 9
error: called from:
error:   C:\Octave\Octave3.6.2_gcc4.6.2\share\octave\3.6.2\m\pkg\pkg.m at
line 827, column 5
error:   C:\Octave\Octave3.6.2_gcc4.6.2\share\octave\3.6.2\m\pkg\pkg.m at
line 383, column 9



--
View this message in context: http://octave.1599824.n4.nabble.com/optim-package-on-Windows-doesn-t-install-tp4644095.html
Sent from the Octave - Dev mailing list archive at Nabble.com.

Re: [OctDev] Dicom package / isdicom function

[Andy B. <and...@gm...>]

On 13 September 2012 12:24, adam aitkenhead <ada...@ho...> wrote:
>
> Hi,
>
> I've written isdicom (as an .m file), a function which is currently missing
> from the Dicom package.  If it's likely to be useful then I'm happy to
> submit it to Octave-forge (is there a different mailing list for
> Octave-forge?), or I could forward the code to the maintainer of the package
> if that's more helpful.
>
> Adam

If you email to me, I will take a look, and commit it to the svn repo.
Are you OK with GPL V3 or higher? Do you want your name in the
comments at the top of the file?

Thanks,

Andy (dicom package maintainer)

[OctDev] Dicom package / isdicom function

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

Hi,

I've written isdicom (as an .m file), a function which is currently missing from the Dicom package.  If it's likely to be useful then I'm happy to submit it to Octave-forge (is there a different mailing list for Octave-forge?), or I could forward the code to the maintainer of the package if that's more helpful.

Adam