similar to: Best way to implement optional functions?

On 10/22/2015 03:55 PM, Duncan Murdoch wrote: > I'm planning on adding some new WebGL functionality to the rgl package, > but it will pull in a very large number of dependencies. Since many > people won't need it, I'd like to make the new parts optional. > > The general idea I'm thinking of is to put the new stuff into a separate > package, and have rgl

On Thu, 2015-10-22 at 15:55 -0400, Duncan Murdoch wrote: > I'm planning on adding some new WebGL functionality to the rgl package, > but it will pull in a very large number of dependencies. Since many > people won't need it, I'd like to make the new parts optional. > > The general idea I'm thinking of is to put the new stuff into a separate > package, and have

On 16/11/2015 4:00 AM, Richard Cotton wrote: > On 22 October 2015 at 22:55, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> I'm planning on adding some new WebGL functionality to the rgl package, but >> it will pull in a very large number of dependencies. Since many people won't >> need it, I'd like to make the new parts optional. > >> Can

I'm planning on adding some new WebGL functionality to the rgl package, but it will pull in a very large number of dependencies. Since many people won't need it, I'd like to make the new parts optional. The general idea I'm thinking of is to put the new stuff into a separate package, and have rgl "Suggest" it. But I'm not sure whether these functions should

On 22 October 2015 at 22:55, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > I'm planning on adding some new WebGL functionality to the rgl package, but > it will pull in a very large number of dependencies. Since many people won't > need it, I'd like to make the new parts optional. > Can people suggest other packages that solve this kind of problem in a good

On 01/02/2016 4:26 AM, Martin Maechler wrote: >>>>>> "BH" == Bryan Hanson <hanson at depauw.edu> >>>>>> on Sun, 31 Jan 2016 09:50:46 -0500 writes: > > BH> I think the 2nd option will be more palatable to > BH> inexperienced users, but both do state the important > BH> detail. Bryan > > >>

I think the 2nd option will be more palatable to inexperienced users, but both do state the important detail. Bryan > On Jan 30, 2016, at 4:11 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > On OSX and Linux, the rgl package currently requires X11 libs to be available for linking. Recent versions of OSX don't include them by default, so I'd like rgl to fail

Prof Nash, Prof Galanos Is it possible to use a generic code stub in front of packages that use optimx to improve optimx use or curtail it according to the requirements? Best Regards Amit +91 7899381263 ________________________________________________________________________ Please request Skype as available 5th Year FPM (Ph.D.) in Finance and Accounting Area Indian Institute

If I recall it correctly, at least on Linux, rgl only needs X11 when rgl.useNULL(FALSE). Is that correct? If so, I would say dependency on X11 is optional and therefore you should be able to load the package even without X11. Or is it that it still requires X11 libs but not an X11 server? My $.02 /Henrik On Mon, Feb 1, 2016 at 1:44 AM, Duncan Murdoch <murdoch.duncan at gmail.com>

>>>>> "BH" == Bryan Hanson <hanson at depauw.edu> >>>>> on Sun, 31 Jan 2016 09:50:46 -0500 writes: BH> I think the 2nd option will be more palatable to BH> inexperienced users, but both do state the important BH> detail. Bryan >> On Jan 30, 2016, at 4:11 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote:

On OSX and Linux, the rgl package currently requires X11 libs to be available for linking. Recent versions of OSX don't include them by default, so I'd like rgl to fail nicely. Ideally, it will load a library that doesn't need to link to the X11 libs but will still allow WebGL code to work, but that's complicated, so I'd like a stopgap. I can detect that the failure is

Thanks for the pointers and the quick fix. Perhaps the generated HTML code should issue a message like "Javascript load problem" instead of "You must enable Javascript to view this page properly," because the latter can be misleading. On Sat, Sep 12, 2015 at 12:42 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 12/09/2015 7:37 AM, Duncan Murdoch wrote:

FYI, one platform where I have not been able to get interactive rgl working is iOS 8. iOS 8 is supposed to support WebGL, and Javascript is enabled. On Sat, Sep 12, 2015 at 4:33 PM, Dominick Samperi <djsamperi at gmail.com> wrote: > Thanks for the pointers and the quick fix. > > Perhaps the generated HTML code should issue a > message like "Javascript load problem"

On 12/09/2015 7:37 AM, Duncan Murdoch wrote: > On 11/09/2015 10:14 PM, Dominick Samperi wrote: >> Hello, >> >> The recently created online "rgl Overview" at >> https://cran.r-project.org/web/packages/rgl/vignettes/rgl.html >> illustrates a problem that I am trying to resolve. >> >> At the bottom of each image block on that page appears the

Ben Bolker pointed out in a response about max. likelihood estimation that parameter scaling is not available in nlminb On 02/03/2012 06:00 AM, r-help-request at r-project.org wrote: > * if you were using one of the optimizing methods from optim() (rather > than nlminb), e.g. L-BFGS-B, I would suggest you try using parscale to > rescale the parameters to have approximately equal

On 11/09/2015 10:14 PM, Dominick Samperi wrote: > Hello, > > The recently created online "rgl Overview" at > https://cran.r-project.org/web/packages/rgl/vignettes/rgl.html > illustrates a problem that I am trying to resolve. > > At the bottom of each image block on that page appears the > advisory: You must enable Javascript to view this page properly. >

I'll not copy all the previous material on this thread to avoid overload. The summary is that all the methods Spencer has tried have some issues. The bad news: This is not uncommon with optimization methods, in part because the problems are "hard", in part because getting them implemented and linked to an interfacing approach like R is very tedious and prone to omissions and

This is mainly a reminder to others developing R packages to be careful not to supply control list items that are not used by the called package. Optimx is a wrapper package that aims to provide a common syntax to a number of existing optimization packages. Recently in extending optimx package I inadvertently introduced a new control for optimx which is NOT in any of the wrapped optimization

With some chagrin after spending a couple of hours trying to debug a script, I realized I had typed in something like ans<-optimx(start, myfn, mygr, lower<-lo, upper=up) that is, the "<-" rather than "=". The outcome on my machine was a non-obvious error several layers deep in the call stack. For info, optim() seems to stop much more quickly. The error is

Hello, The recently created online "rgl Overview" at https://cran.r-project.org/web/packages/rgl/vignettes/rgl.html illustrates a problem that I am trying to resolve. At the bottom of each image block on that page appears the advisory: You must enable Javascript to view this page properly. I am using Safari under MacOS with Javascript and WebGL both enabled, so it must be the