Don't use this StatConn R Program, it is really poorly written software.
Instead, use RDotNet, it is much easier to get up and running, and very
simple to use:
http://rdotnet.codeplex.com/
--
View this message in context:
http://r.789695.n4.nabble.com/Use-of-R-in-C-tp2165189p4589776.html
Sent
I ended up getting around this issue by running installstatconnDCOM() - not
the exact name, but something very similar to that in RStudio instead of
downloading from their site. This resolved the 80040013 error. I
subsequently ran into a few issues regarding an 800706BE error. I resolved
this by de
Hello all,
I would like to relate this behaviour of: plot.table & plot.TukeyHSD.
They don't work with some graphical parameters.
Thanks for your attetion.
Cleber
> ### example:
> plot( table(1:10), cex.axis=0.6)
> plot( table(1:10), las=2)
>
> tukaov <- TukeyHSD( aov(breaks ~ wool + tension, da
yangleicq writes:
> Hi, all.
> I want to write some functions like glm() so i studied it.
> In glm.fit(), it calls a fortran subroutine named "dqrfit" to compute least
> squares solutions
> to the system
> x * b = y
>
> To learn how "dqrfit" works, I just follow how glm() calls "d
Of course, what you could do is Google dqrls and get the source and
documentation. That is because it is in the publically available linpack.
If it were not publically available that would not work. Theoretically,
all FORTRAN or C code in R should be publically available.
Dave
From:
To:
On 12-04-27 8:56 AM, David L Lorenz wrote:
Of course, what you could do is Google dqrls and get the source and
documentation. That is because it is in the publically available linpack.
If it were not publically available that would not work. Theoretically,
all FORTRAN or C code in R should be
On 27-04-2012, at 14:56, David L Lorenz wrote:
> Of course, what you could do is Google dqrls and get the source and
> documentation. That is because it is in the publically available linpack.
> If it were not publically available that would not work. Theoretically,
> all FORTRAN or C code in
There have been several threads on this list about the Notes generated
in the check process regarding "global variables" with no visible
definition. These can be useful but false positives tend to obscure
valid notes.
The function globalVariables() has been added to the utils package, in
the
