similar to: Troubles with subset()

Displaying 20 results from an estimated 3000 matches similar to: "Troubles with subset()"

2012 Nov 20
5
Using if
Dear R users, As a new comer to R, I would like to create a new variable using if statements but don't know how to do it. Basically, I have two variables (EvHint and MinTex). I want to create a third variable called RiskTest. In SPSS, my syntax would look like Compute RiskTest=0. if (EvHint=1 & MinTex=1) RiskTest=1. Question: How do I do this with R? My Data EvHint<-c(0, 0, 0, 1,
2013 Jan 09
1
weighted factor analysis
hello there, I am trying to use a weight variable in a factor analysis but apparently the factanal command does not have a weight option. Any way to this? Thanks for your suggestions, V [[alternative HTML version deleted]]
2012 Nov 23
1
Joining two files
Hello all, I al trying to join (ADD FILES in SPSS) two files using the rbind() function. However, with rbind() R does not behave the same way as SPSS. I mean, it just concatenates the two blocs with no consideration for same variables if these are not in the same position in the two files. Anyone knows a function that performs the SPSS ADD FILES task? Thanks, V [[alternative HTML version
2013 Feb 11
1
Simple frequencies using svy design
Hello, excuse me if this is trivial. I have some survey data with the following design MyDesign<-(id=ident, weights=~fwgt, fcp=~nval1+nval2, data=hh_data1) I would like to run simple frequency tables such as those provided by the freq() function of rgrs to check the impact of the sampling design on my Ns. Anyway I can do this? thanks, V [[alternative HTML version deleted]]
2013 Jan 02
1
Extracting factors from "factanal"
Dear R users Happy New year to all for a start. Below is some data that I ran a factor analysis on. Using $score prints the scores for each of the three factors. However, I would like to access those factors as variable for new computations. How do I do that? In SPSS we just call fact1_1, fact2_1 etc.. Thanks for your suggestions. V ============ v1 <- c(1,1,1,1,1,1,1,1,1,1,3,3,3,3,3,4,5,6) v2
2006 May 15
2
Error creating controllers in InstantRails-1.3a
Hi, I was able to successfully Install InstantRails-1.3a and run cookbook throgh Apache and WEBrick , however when I try to create my own app. cookbook2 following tutorial ( http://instantrails.rubyforge.org/tutorial/index.html) , it gives me below error whle creating MyTest controller Cannot find gem for Rails =1.1.2: Install the missing gem with ''gem install -v=1.1.2
2013 Aug 29
3
[LLVMdev] COFF.h and windows.h conflict
It was happening in a few files using COFF.h in LLDB for the windows branch (Windows.h is required for some typedef over Mutex, thread, socket, etc...). As said before, I am currently checking if it could be avoided (probably some refactoring will be needed). However I was wondering if it might not be easier to just avoid this clash at all by avoiding it in LLVM. Alternatively I could #undef
2013 Aug 29
2
[LLVMdev] COFF.h and windows.h conflict
Right now, we have: In COFF.h: class COFF { enum MachineTypes { IMAGE_FILE_MACHINE_UNKNOWN = 0x0, ... }; }; In windows.h: #define IMAGE_FILE_MACHINE_UNKNOWN 0 * If you first include COFF.h and then windows.h, COFF::IMAGE_FILE_MACHINE_UNKNOWN will be preprocessed into COFF:0. * If you first include Windows.h and then COFF.h, COFF.h won't work because it's enum will
2009 Dec 09
2
Memory leak on Icecast 2.3.2 / Debian ?
On 08/12/09 20:44, Jussi Kukkonen wrote: > I'm not a icecast developer so I have very little idea what the code in > question does or how to test it. As a matter of fact I don't even have a > build environment (or time) available here, this is why I didn't send a > patch. > > But since you asked, attached are the missing frees for icecast2_2.3.2-4 > in a totally
2013 Aug 28
3
[LLVMdev] COFF.h and windows.h conflict
Hello, I noticed that if include\llvm\Support is included alongside Windows.h, there will be many define conflict leading to compilation errors, such as: COFF.h (enum): enum MachineTypes { IMAGE_FILE_MACHINE_UNKNOWN = 0x0, ... }; and winnt.h (same but define): #define IMAGE_FILE_MACHINE_UNKNOWN 0 Of course I could try to avoid to include both (but it's rather difficult and would require
2013 Aug 29
0
[LLVMdev] COFF.h and windows.h conflict
On Aug 28, 2013, at 7:05 PM, Virgile Bello <virgile.bello at gmail.com> wrote: > Right now, we have: > In COFF.h: > class COFF { enum MachineTypes { IMAGE_FILE_MACHINE_UNKNOWN = 0x0, ... }; }; > In windows.h: > #define IMAGE_FILE_MACHINE_UNKNOWN 0 > > * If you first include COFF.h and then windows.h, > COFF::IMAGE_FILE_MACHINE_UNKNOWN > will be
2013 Aug 29
0
[LLVMdev] COFF.h and windows.h conflict
In the Windows SDK headers, is the IMAGE_* defines in a separate file (e.g. winint.h)? Does the file have a guard against multiple inclusion? If so (and the guard was named _WINNT_H_), perhaps you can do something like: #define _WINNT_H_ #include <windows.h> So you would get everything except those file format defines. Of course, this would fail if other parts of the windows header rely
2005 Dec 20
3
CVS compilation and EVC++ 4.0
Hi all, I'd like you to know i'm not able to build Speex library anymore from CVS without modfing the code in mdf.c. This is due to the fact that EVC++ compiler doesn't like memory allocations in this form: spx_word16_t w[N]; where N is not a constant. I know this is not an error for gcc compiler and ANSI standard but it is in VS2005 and EVC++ 4.0 If someone knows how to compile
2013 Aug 28
2
[LLVMdev] COFF.h and windows.h conflict
Yes of course I understand it was done on purpose. It's just that it makes it impossible to include COFF.h and Windows.h side by side (which probably wasn't necessary until now). On Wed, Aug 28, 2013 at 9:52 AM, Reid Kleckner <rnk at google.com> wrote: > IMO the fact that it uses the standard names from the COFF documentation > is a feature, not a bug. > > The elf and
2013 Aug 29
1
[LLVMdev] COFF.h and windows.h conflict
The odds of #define _WINNT_H working are incredibly slim :) You can't include the separate headers (winbase.h etc), you have to just include windows.h Windows defines IMAGE_* whether we like it or not, we can't stop it doing it, so the only reasonable solution is to change LLVM to have it's own set of constant names. Nick Kledzik wrote: > In the Windows SDK headers, is the
2013 Aug 28
0
[LLVMdev] COFF.h and windows.h conflict
IMO the fact that it uses the standard names from the COFF documentation is a feature, not a bug. The elf and macho headers in the same directory use the standard enumeration names, correct? On Tue, Aug 27, 2013 at 5:41 PM, Virgile Bello <virgile.bello at gmail.com>wrote: > Hello, > > I noticed that if include\llvm\Support is included alongside Windows.h, > there will be many
2005 Dec 05
2
wbinfo and user group
Hello, I have a problem with to obtain an user group. My config is : Redhat server 3.0 update 1 samba-3.0.20b my smb.conf is : **************************** [global] workgroup = domxxx password server = xxxx, xxxx security = ads winbind uid = 10000-20000 winbind gid = 10000-20000 winbind use default domain = yes winbind enum users =
2002 Dec 03
2
Samba SWAT 2.2.7 Doesn't Work in Redhat8.0?
Hello All Samba-list Members, I have installed a Samba 2.2.7, the samba-latest.tar.gz, as a PDC on a Redhat8.0 GNU/Linux server. ( Of course, I first uninstalled the original samba that came with the Redhat installation CDs by rpm -e samba*.) The installation was successful. Then I modified /etc/services and /etc/xinetd.d/swat as suggested in the installation document uncompressed from
2014 Dec 31
3
[LLVMdev] First class aggregates of small size: split when used in function call
Hello, In my LLVM frontend (CLR/MSIL), I am currently using first-class aggregates to represent loaded value types on the "CLR stack". However, I noticed that when calling external method taking those aggregate by value, they were not passed as I expected: %COLORREF = type { i8, i8, i8, i8 } declare i32 @SetLayeredWindowAttributes(i8*, %COLORREF, i8, i32) I call this function with
2013 Aug 28
0
[LLVMdev] COFF.h and windows.h conflict
On Aug 27, 2013, at 5:56 PM, Virgile Bello <virgile.bello at gmail.com> wrote: > Yes of course I understand it was done on purpose. > It's just that it makes it impossible to include COFF.h and Windows.h side by side (which probably wasn't necessary until now). I too am in the camp that it is a feature to use the standard names. For instance doing a search it google or