similar to: Joining two files

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,

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]]

All, I have the attached dataset which I read from SPSS and transformed a little bit using the attached script. I am trying to run a logistic regression using glm() on a subset of my data. When I run the logistic regression on the whle dataset, it runs OK. As soon as I try to run on the subset, I get an error message related to different lengths of variables. Any idea why this might be so? Thanks

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

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]]

Dear, I have a dataset with 4 subjects (see ID in example), and 4 treatment (see TRT in example) which are tested on 2 locations and in 3 blocs. By using Lattice dotplot, I made a graph that shows the raw data per location and per bloc. In that graph, I would like to have a reference line per bloc that refers to the first treatment (T1). However, I can not find how to do that. I can make

Hello everybody, I''m playing with Xen and trying to extend DomU disk space. My Configuration: Dom0: all Xen machine are HVM. They''re installed on LVM. I''ve one VG (XEN) on Dom0 and created a LV (here, xps.101.disk) per DomU. disk configuration in xen conf is as follow: disk = [ ''phy:/dev/XEN/xps.%d.disk,ioemu:hda,w'' % (vmid)

Hello All, How can I keep track of the different basic blocks of a program executed over time? Or in other words, how can I annotate the block name (block_a) and the time/cycle at which that blocs (block_a) was executed, and do this for all the blocks on a reasonable simple program? Regards, Raul. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Dear List, Sorry for the dublicated email but I couldn''t get any answer. I am trying to limit some IP blocs with tc with following three step. # interface tc qdisc add dev eth0 root handle 1: cbq avpkt 1000 bandwidth 256kbit # class tc class add dev eth0 parent 1: classid 1:1 cbq rate 64kbit \ allot 1500 prio 5 bounded isolated # rules # download tc filter add dev eth0 parent 1:

Why some transformation passes insert basic blocs with only a label and a terminator instrucion? -- *Rafael Parizi* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121029/71e644d4/attachment.html>

hello everybody , I''ve a new problem !!!!! When i create a new DOMU, the installer can''t format the Virtual Disk... however, the qemu disk is reconize by the OS (etch stable) but it blocs during the ext3 creation... It ''s the same thing when i use automatic or custum formating partition.... I create my disk img like this: dd if=/dev/zero of=/../../../debian.img

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

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

Hi Reid Reid Spencer wrote: > > Interesting project. I wish you could talk about it at the Developer's > Meeting (http://llvm.org/DevMtgMay2007.html :) > > I wish I could! Unfortunately there is very little chance I get the fundings to go to the US in May. > > I have signed up to implemented this (PR1269) just as Chris' note > states. HLVM needs it for much

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

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

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

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

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

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