search for: psuedo

Displaying 20 results from an estimated 186 matches for "psuedo".

2009 Jun 08
1
Random Forest % Variation vs Psuedo-R^2?
...1996 | 0.04605 130.43 | 1997 | 0.04606 130.44 | 1998 | 0.04607 130.47 | 1999 | 0.04606 130.46 | 2000 | 0.04605 130.42 | With the first column representing the iteration, the second column representing the OOB MSE, and the last column representing the %Var(y). If I calculate a "Psuedo-R^2" from these numbers, I would get; 1-(.04605/1.3042) = 0.965 Here's the question, if I look at the summary of forest.rf (this same run), I get the following; randomForest(formula = Prev ~ ., data = plas, ntree = 2000, importance = TRUE, do.trace = T) Type of random for...
2010 Aug 26
3
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
Also there is a typo: it probably should read pseudo. Yuri
2010 Aug 26
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
...llvm, but it does not correspond directly to a real instruction in the target architecture. Before emitting the final compiled code, all the pseudo instructions must be expanded to real instructions. If you're seeing that error, it means that something was not expanded. I fixed all the "psuedo" misspellings in svn 112202. I didn't see the error message, so that must have been changed already.
2002 Apr 02
1
Extract psuedo model matrix from nls?
Hi R-list, I'd like to extract the psuedo model matrix (derivative of fitted values wrt the parameters) from an nls object. Any suggestions? Thanks, Murray Jorgensen Dr Murray Jorgensen on leave from: Mathematics and Statistics Department of Statistics University of Victoria University of Waikato PO BOX...
2010 Aug 26
3
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On 08/26/2010 11:11, Bob Wilson wrote: > A pseudo instruction is used internally without llvm, but it does not correspond directly to a real instruction in the target architecture. Before emitting the final compiled code, all the pseudo instructions must be expanded to real instructions. If you're seeing that error, it means that something was not expanded. > So what is likely to
2010 Aug 26
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On Aug 26, 2010, at 11:47 AM, Yuri wrote: > On 08/26/2010 11:11, Bob Wilson wrote: >> A pseudo instruction is used internally without llvm, but it does not correspond directly to a real instruction in the target architecture. Before emitting the final compiled code, all the pseudo instructions must be expanded to real instructions. If you're seeing that error, it means that
2010 Aug 26
2
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On 08/26/2010 11:53, Eric Christopher wrote: > It basically means that a pseudo wasn't lowered to something that the jit can output before the jit was run. Is this on ToT? > I don't know what is ToT. 42 meanings listed here http://acronyms.thefreedictionary.com/TOT don't seem to apply. Yuri
2010 Aug 26
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On Aug 26, 2010, at 12:41 PM, Yuri wrote: > On 08/26/2010 11:53, Eric Christopher wrote: >> It basically means that a pseudo wasn't lowered to something that the jit can output before the jit was run. Is this on ToT? >> > > I don't know what is ToT. 42 meanings listed here http://acronyms.thefreedictionary.com/TOT don't seem to apply.\ ToT = "top of
2010 Aug 26
2
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On 08/26/2010 11:53, Eric Christopher wrote: > Could you get it to print out the instruction when it happens? (just change the line above the error message to print it out to errs()). > > It basically means that a pseudo wasn't lowered to something that the jit can output before the jit was run. Is this on ToT? > Insn before the error: TCRETURNri64 %RAX<kill>, 0,
2010 Aug 26
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On Aug 26, 2010, at 12:25 PM, Yuri wrote: > On 08/26/2010 11:53, Eric Christopher wrote: >> Could you get it to print out the instruction when it happens? (just change the line above the error message to print it out to errs()). >> >> It basically means that a pseudo wasn't lowered to something that the jit can output before the jit was run. Is this on ToT? >>
2010 Aug 27
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On Aug 27, 2010, at 3:43 PMPDT, Yuri wrote: > On 08/27/2010 12:13, Dale Johannesen wrote: > Here's what happens: > The first instruction created is RET. > SelectBasicBlock is called. > TCRETURNri64 is created from within it. > HasTailCall is set to true as you mentioned. > Cycle in SelectionDAGISel::SelectBasicBlock skips the rest. > > All like you described. But
2010 Aug 27
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On Aug 27, 2010, at 10:49 AM, Dale Johannesen wrote: > > On Aug 26, 2010, at 11:34 PMPDT, Yuri wrote: > >> On 08/26/2010 13:17, Dale Johannesen wrote: >>>>> Insn before the error: TCRETURNri64 %RAX<kill>, 0, %RDI<kill>, %RAX<imp-def,dead>, %RDI<imp-def,dead>, %RSP<imp-use>, ... >>>> >>>> Odd. I thought
2010 Aug 27
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On 08/26/2010 13:17, Dale Johannesen wrote: >>> Insn before the error: TCRETURNri64 %RAX<kill>, 0, %RDI<kill>, >>> %RAX<imp-def,dead>, %RDI<imp-def,dead>, %RSP<imp-use>, ... >> >> Odd. I thought TCReturn was being lowered. At any rate can you file >> a bug with the .ll file that causes this? > > It should be getting
2004 Jun 07
2
strange apparently data-dependent crash with large data (PR#6955)
...make this clear, three different versions of the same data consistently produce very different behavior: (1) original data read with read.table: memory error; fail to allocate 164062 Kb (2) original data through save()/load() cycle: memory error; fail to allocate 82031 Kb, followed by crash (3) psuedo-random data of same size and similar characteristics: works without problem This is with R-1.9.0 under Windows 2000. I'm not loading any optional packages. I get the same crash behavior with R-1.9.0 patched, and R-2.0.0 alpha, but I didn't test success with the psuedo-random data unde...
2006 Apr 30
1
Number of Clusters
Dear R users, I am interested in clustering in R. In SAS we have some criteria for determining the number of clusters using the PROC CLUSTER procedure, which are "CCC" cubic clustering criterion (Sarl 1981), Psuedo F (PSF), and Psuedo T square (PST). My question is do thsese criterion exists in R, I tried to search and got one hit (BIC) in Mclust, which I am aware of, any input is greatly appreciated. Ahmed Albatineh, PhD Nova Southeastern University FL, USA --------------------------------- [...
2010 Aug 26
2
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On Aug 26, 2010, at 12:59 PMPDT, Eric Christopher wrote: > On Aug 26, 2010, at 12:25 PM, Yuri wrote: >> On 08/26/2010 11:53, Eric Christopher wrote: >>> Could you get it to print out the instruction when it happens? >>> (just change the line above the error message to print it out to >>> errs()). >>> >>> It basically means that a pseudo
2004 Jun 10
0
lsoda with arbitrary zero thresholds (with psuedo-solution)
Dear Hank, Last question first: really, only you can say for sure if 4e-281 and 5e-11 are small enough; it depends on the units you measure your state variables in. However, this strategy cannot get the state variables to exactly 0. Obviously, you could get closer to 0.0 faster by setting the derivatives even larger in absolute value. You may run into problems with the solver when the
2010 Aug 27
2
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On Aug 26, 2010, at 11:34 PMPDT, Yuri wrote: > On 08/26/2010 13:17, Dale Johannesen wrote: >>>> Insn before the error: TCRETURNri64 %RAX<kill>, 0, %RDI<kill>, >>>> %RAX<imp-def,dead>, %RDI<imp-def,dead>, %RSP<imp-use>, ... >>> >>> Odd. I thought TCReturn was being lowered. At any rate can you >>> file a bug
2009 Jan 13
9
Updating multiple databases at the same time
...what I am trying to do. I want to update the name of a product on my website. Here is the controller: def update_product_name product = Product.find(params[:id]) product.name = params[:name] product.save #Say I want to save this to 3 other databases #can I do this with activerecord? #PSUEDO CODE... I know it cant do this product.save(mysql_host2) product.save(mysql_host3) product.save(mysql_host4) end Any ideas? Alternative ways to do this? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you ar...
2010 Aug 27
0
[LLVMdev] What does this error mean: psuedo instructions should be removed before code emission?
On Aug 27, 2010, at 11:53 AMPDT, Yuri wrote: > On 08/27/2010 11:32, Yuri wrote: >> As I understand only one of TCRETURNri64 and RET should be created. >> I have sources of rev.112200. >> >> Here is the stack when TCRETURNri64 instruction is created: >> #1 0x0000000802c8b4e2 in llvm::MachineFunction::CreateMachineInstr >> (this=0x30eb000, TID=@0x803a78940,