similar to: how to use plot.lda included in MASS package?

Displaying 20 results from an estimated 1000 matches similar to: "how to use plot.lda included in MASS package?"

2011 Jun 09
1
what is the mistake?? the coding still not function. no result display
# lda.r > # > # Author: Amsha Nahid, Jairus Bowne, Gerard Murray > # Purpose: Perform Linear Discriminant Analysis (LDA) > # > # Input: Data matrix as specified in Data-matrix-format.pdf > # Output: LDA plot > # > # Notes: Missing values (if any) are replaced by the half of the lowest > # value in the entire data matrix. >
2011 Jun 21
1
(no subject)
hello, i already include the error in blue color word. i hope it can help you to understand my question. if not burden you, please give me a guide how to correct the error or maybe you can correct the coding cause error. thank you. > # lda.r > # > # Author: Amsha Nahid, Jairus Bowne, Gerard Murray > # Purpose: Perform Linear Discriminant Analysis (LDA) > # > #
2017 Nov 21
2
mystery "158"
This is a simple problem, but a mystery to me. I'm trying to grab $Family "Scelionidae" from one dataframe and put it into another dataframe occupied with NA in $Family. The result is a "158" ends up there instead of Scelionidae. Simply put fam$Family[1] <- least$Family[1] If I have made a mistake here, can somebody point it out. I've included the simple
2017 Nov 21
0
mystery "158"
Your data frame fam contains factors. Turn it into character strings using fam$Family = as.character(fam$Family) and try again. It may be helpful if you read up on R's factors, see ?factor. HTH, Peter On Tue, Nov 21, 2017 at 2:14 PM, Glen Forister <gforister at gmail.com> wrote: > This is a simple problem, but a mystery to me. > I'm trying to grab $Family
2004 May 24
1
discriminant analysis
Hi, I have done different discriminant function analysis of multivariat data. With the CV=True option I was not able to perform the predict() call. What do I have to do? Or is there no possibility at all? You also need the predicted values to produce a plot of the analysis, as far as I know. Here my code: pcor.lda2<-lda(pcor~habarea+hcom+isol+flowcov+herbh+inclin+windprot+shrubcov+baregr,
2017 Nov 22
1
mystery "158"
Well, ?factor does not say anything about this behaviour (assigning numeric code instead of level of factor). And actually if you do assignment for whole vector the result is different (vector in data frame is changed to factor). > temp2$fff[1]<-vec[1] > head(temp2,2) pokus minuty fff 1 T42 240 3 2 T42 300 <NA> > temp2$fff<-vec > head(temp2,2) pokus
2004 Nov 02
2
lda
Hi !! I am trying to analyze some of my data using linear discriminant analysis. I worked out the following example code in Venables and Ripley It does not seem to be happy with it. ============================ library(MASS) library(stats) data(iris3) ir<-rbind(iris3[,,1],iris3[,,2],iris3[,,3]) ir.species<-factor(c(rep("s",50),rep("c",50),rep("v",50)))
2009 Aug 05
1
Decision boundaries for lda function?
Hi, I am using the lda function from the MASS library. I would to find the decision boundaries of each class and subsequently plot them. I wonder if anybody can offer any help on this topic? Below I applied the lda function on a small dataset of mine. Any help will be much appreciated. > library(MASS) >
2001 Aug 30
1
imagenrgb: Function to display RGB images in R
I've writen this function (imagenrgb) to display a (m,n,3) array as a RGB image with ngris^3 colors and,optionally, stretching. If option ver=F, it does not display but saves a pseudocolor version of the image as a list (so that subsequent displays are faster). I'd appreciate feedback and improvements and hope that it's useful for others. Example of use: > dim(imatest) [1] 100
2011 Dec 16
1
kmeans and plot labels
Hi, Thanks Sarah. Unfortunately I did not get a step further. My question, perhaps a bit clearer, is how to display the case control status (or any other arbitrary point label) after clustering in a plot: With a bit of pseudo code, where dataset is a data.frame, parameters are those column names where we find numerical values (no NAs) and nclasses is the desired number of classes. fit <-
2007 Jun 18
0
discriminant analysis with lda(MASS)
I use Widows, R version 2.4.1 I have 4 questions on lda (MASS) (code is pasted below): 1st. How can I obtain the statistics and p-value associated with discriminant analysis? Am I supposed to calculate that manually by squaring the svd value and looking the p value up in a table? I am writing the following code: training.mx<-read.table('C:\\Documents and Settings\\silvia\\My
2011 Jun 09
0
(no subject)
> # >> # Generate the figures (on screen) >> # >> # Image generation - function definition >> pic_onscr<-function(matrix, title, cex_val=1) > + {x11() + par(mgp=c(5,2,0), # axis margins + # (title, > labels, line) + mar=c(7,4,4,2), # plot margins (b,l,t,r) + > las=1) # horizontal labels + plot(matrix, # data to plot + >
2017 Apr 19
2
[PATCH] daemon: Move the useful 'is_zero' function into common code.
This is largely a simple refactoring, but it combines another definition of this function from virt-builder which had a slightly different prototype. --- builder/pxzcat-c.c | 20 +------------------- daemon/daemon.h | 18 ------------------ lib/guestfs-internal-all.h | 18 ++++++++++++++++++ 3 files changed, 19 insertions(+), 37 deletions(-) diff --git a/builder/pxzcat-c.c
2002 Jun 04
4
"X11 font at size 16 could not be loaded"
Hi, I'm using plot.lda (R1.4.0 on linux) and, if dimen > 2, I get the error: Error in text.default(x, y, txt, cex = cex, font = font) : X11 font at size 16 could not be loaded The traceback indicates that the problem comes from pairs(). I've tried several cex and font values, always with the same error. The same command works fine with pdf() If I'm missing fonts, how
2016 Mar 23
1
Clang/LLVM producing incomplete & erroneous debug information
Hi everyone, I'm trying to get debug information for a C/pthreads application, but it seems like clang/LLVM are producing limited & erroneous debugging information. I've attached a simple test example to reproduce the problem -- I'm using clang/LLVM 3.7.1 built from source on Ubuntu 14.04. I compile the attached file with: $ clang -O1 -g test.c -lpthread If I run: $ readelf
2015 Aug 18
3
[RFC PATCH 1/2] [clang]: Add AuxAttr support
This patch adds EmitTypeAuxAttribute() function to CGDebugInfo, which allows other parts of clang issue auxiliary information through an enumeration type in Dwarf information. For example, by calling DI->EmitTypeAuxAttribute(type, "ID", 1234); We can get following information in dwarf: <1><3f>: Abbrev Number: 3 (DW_TAG_structure_type) <40> DW_AT_name
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
Sorry, this is the attachment. 2014-02-19 15:08 GMT+08:00 杨勇勇 <triple.yang at gmail.com>: > Thank you. > > Here is an example and the attchment contains extra files including object > file and executable file. > I want to print for example the value of "a", but lldb command "frame > variable a" displays "0" and so does "b", and
2006 Mar 06
2
Cookies & gsub ?
I''m looking to store the current params into a/some cookie(s). This works: @params.each_pair do |this_index, this_param| cookies[this_index] = this_param end Except, I get session-only cookies. This doesn''t work: @params.each_pair do |this_index, this_param| cookies[this_index] = { :value => this_param, :expires => 30.days.from_now } end
2014 Feb 18
1
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
All of this information is contained in the DWARF debug info that you must generate. Are you generating DWARF? If not, you will need to. If so, please attach an example program that contains DWARF and specify which function you are having trouble getting variable information for. Greg Clayton On Feb 18, 2014, at 12:44 AM, 杨勇勇 <triple.yang at gmail.com> wrote: > Hi, all > > I
2014 Feb 18
4
[LLVMdev] How is variable info retrieved in debugging for executables generated by llvm backend?
Hi, all I ported llvm backend and lldb recently. Both tools can basically work. lldb is able to debug programs in asm style and frame unwinding is OK. But "frame variable XX" does not work because lldb is not able to determine the address of XX from debug info. Can someone give any clue? Thanks in advance. -- 杨勇勇 (Yang Yong-Yong) -------------- next part -------------- An HTML