search for: ipars

Dear all, The following code is inspired by the help file for the relist() function (see?relist), which explicitly details how you can use a relistable object in conjunction with optim to pass and reconstruct complex parameter structures/groupings. The idea is that the optim() function can only work with vectors, but in many cases you would like to use a complex structure inside the objective

Hi Peter, I've fwded your info to the list, as other people might be interested in. I've also logged a patch tracker so that you can follow its inclusion: https://alioth.debian.org/tracker/index.php?func=detail&aid=302882&group_id=30602&atid=411544 As a side note, there is a work underway to merge the similar driver (mustek, powermust, ...) into one named megatec. This one

I think the optim() example in the Details section of relist()'s help page is not totally correct. In particular, in the current form it is not taken into account that vcov should be a symmetric matrix and only the parameters in the lower (or upper) triangular part should be optimized. A possible fix is: ipar <- list(mean = c(0, 1), vcov = c(1, 1, 0)) initial.param <-

Hi All, ? I am trying to use the lordif package in R and can't figure out the reason for the above error when I try to run the calctheta() function. ################## # read data using foreign package - must be Stata 11 or earlier racedata<- read.dta("race.dta")??? # item responses resp.data<-racedata[,-c(1:2)] # grouping variable is in the second column

There are a few typos in the documentation for relist(). I've also made a few other changes to the file which I believe are improvements. I've attached a patch against the version under the 'trunk' branch on the svn server checked out today. It was produced by diff -u /usr/local/src/R/R-svn-trunk/src/library/utils/man/relist.Rd ~/relist-new.Rd I'd also suggest identical()

Arnaud Quette <aquette.dev at gmail.com> va escriure (2011-02-28 14:48): > > 2011/2/14 Ernest Sales <ersaloz at gmail.com> > > > Arjen de Korte <nut+users at de-korte.org> va escriure: > > > This is a known problem in nut-2.4.3 and should be solved in > > > nut-2.6.0. We have also dropped the megatec and > megatec_usb drivers, > > >

Greetings I am running SMB on OS X Server 10.5.6, it's not clear what version of SMB they use. I have a Windows XP box that mounts a network drive on the server. This mount disappears from time to time for no apparent reason: [2009/03/12 08:35:54, 2, pid=23189] /SourceCache/samba/samba-187.8/ samba/source/smbd/process.c:timeout_processing(1371) Closing idle connection [2009/03/12

I would like to report a working device to add to the hardware compatibility list, but cannot find a way on the website. Would this list be OK for that purpose? Best regards, Ernest

On Fri, Jul 8, 2016 at 9:47 AM, Lawrence, Peter <c_plawre at qca.qualcomm.com> wrote: > Vivek, > > I am looking into these function attributes in the clang docs > > Preserve_most > > Preserve_all > > They are not available in the 3.6.2 that I am currently using, but I hope > they exist in 3.8 > > > >

Vivek, IIUC it seems that we need two pieces of information to do IPRA, 1. what registers the callee clobbers 2. what the callee does to the call-graph And it is #2 that we are missing when we define an external function, Even when we declare it with a preserves or a regmask attribute, So what I / we need is another attribute that says this is a leaf function, At least in my case all

Vivek, Here’s the way I see it, let me know if you agree or disagree, You cannot optimize a function’s calling convention (register-usage) unless You can see and change every caller, and you only know this for non-static functions if you know that all calls to external functions cannot call back into the current compilation unit. #1 gives you the info necessary to change the call-site

Mehdi, I’m compiling embedded applications which are small enough to do whole-program-compilation. There’s no advantage in breaking them up into separate compilation pieces and linking them, even though in source form they are composed of a couple of separate source files. So for me the compilation unit is always the entire program (and includes main()) Except for some

Hello Peter, Thanks to pointing out this interesting case. > Vivek, > I have an application where many of the leaf functions are > Hand-coded assembly language, because they use special IO instructions > That only the assembler knows about. These functions typically don't > Use any registers besides the incoming argument registers, IE they don't > Need to

Mehdi, I am looking for an understanding of 1) IPRA in general, 2) IPRA in LLVM. Whether I want to use LTO or not is a separate issue. 1) I currently believe it is a true statement that: If all external functions are known to not call back into the “whole-program” Being compiled, then IPRA is free to do anything at all to the functions being

The following series implement a way to generate the help messages and the btrfs man page from the sources comments for the "btrfs" commanda . The syntax and the detailed help of every subcommand are stored in the comments before the function which implements the subcommand. The fact that the help messages and the man page are generated from the same source should help to avoid

As soon as the application starts, a window pops up that (normally under windows) would say "this is a trial version demo, click okay to start the trial", or something along those lines. The window is blank and clicking randomly on it (to find the "ok") does not work either. The following output from wine during this test is as follows : err:iphlpapi:getRouteTable Received