Output discrepancy between SAS and R -

-

i have coded same program in r , in sas (university edition running on oracle virtualbox on mac) , i'm noticing discrepancy - means messed up.

the first discrepancy appears in principal component analysis run , believe has options intrinsic functions available in 2 programs. diligently working on looking on documentation grateful assistance of brilliant experts on site.

i have been using file - https://drive.google.com/file/d/0b9oqam9ykac3bepicestrw8wuzg/view?usp=sharing - test 2 programs.

in r, code pca simple:

pca1=prcomp(predictor_matrix, scale.=true)

and first observation transformed following 

<1.01,  -0.79,  -0.03,  -1.08,  1.86,    -0.13,  0.04,   -0.03,  0.02,   -0.01>

in sas, code pca looks like:

proc factor data=regressors      simple corr     mineigen=0 /*retain eigenfunctions*/     nfactors=10      /*print optional data*/     out=newdata /*get transformed data*/      ; run;

and first observation transformed following

<0.55,  -0.53,  -0.02,  -0.89,  1.96,    1.45,   0.89    ,    1.18,  1.15,   1.46>

now - eigenvector matrices identical in both programs eigenvalues different, i'm thinking problem has scaling. brand new sas , use pointers on how results of these 2 programs converge.

the sas proc pca proc princomp, not proc factor. try

proc princomp data=regressors n=10 out=newdata; run;

Comments

Post a Comment

Popular posts from this blog

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co
Read more

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall
Read more

java - Cannot secure connection using TLS -

-
i'm trying establish secure socket connection between java client applet (built jdk 1.7.0_75-b13) , vc++ server application. as test vehicle, used vc++ client/server sample found in msdn forums, modified use schannel , able establish socket using cipher suite tls_rsa_with_aes_128_cbc_sha. works of tls 1.0/1.1/1.2. when try opening socket java applet same server application, connection rejected server reporting following: tls 1.0 acceptsecuritycontext failed: 0x80090327 tls 1.1 acceptsecuritycontext failed: 0x80090331 tls 1.2 acceptsecuritycontext failed: 0x80090331 this java code used create socket: debugprint("setting secure connection"); sslsocketfactory sslsocketfactory = (sslsocketfactory) sslsocketfactory.getdefault(); sslsocket sslsocket = (sslsocket) sslsocketfactory.createsocket("127.0.0.1", socketnumber); debugprint("starting handshake"); sslsocket.settcpnodelay(true); sslsocket.setsolinger(false, 0); sslsocket.s
Read more