Sorry, the previous had a bug and was quite ugly. This is a bit better:
--
function (x, y = NULL, type = p, xlim = NULL, ylim = NULL,
log = , main = NULL, sub = NULL, xlab = NULL, ylab = NULL,
ann = par(ann), axes = TRUE, frame.plot = axes, panel.first = NULL,
panel.last = NULL,
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 dqrfit by my
own example, my codes are
Jeff Abrams jeffab at microsoft.com writes:
I have a C# program that requires the run of a logistic regression. I have
downloaded the R 2.11 package, and
have added the following references to my code:
STATCONNECTORCLNTLib;
StatConnectorCommonLib;
STATCONNECTORSRVLib;
In my code I
I cleaner alternative would be to use Rserve. You can use IKVM to compile
the Rserve java API to a .NET assembly. Alternatively you can implement
the protocol in C# (as I did).
On Wed, Apr 25, 2012 at 6:50 AM, Joel j.nyb...@gmail.com wrote:
Jeff Abrams jeffab at microsoft.com writes:
I
For the amusement of the listserver:
Making use of the counter-intuitive assignment properties of delayedAssign, a
co-worked challenged me to construct a delayedAssign of 'x' that causes 'x' to
change its value _every_ time it is evaluated. The example below does this;
each time 'x' is
On Apr 25, 2012, at 5:18 PM, McGehee, Robert wrote:
I'm not sure if this is a known peculiarity or a bug, but I stumbled across
what I think is very odd behavior from delayedAssign. In the below example x
switches values the first two times it is evaluated.
delayedAssign(x, {x - 2; x+3})
On 25.04.2012 10:58, ONKELINX, Thierry wrote:
Dear all,
I get a bug in the examples of my AFLP package on R-forge
(https://r-forge.r-project.org/R/?group_id=1027) but only on the Linux version.
The windows version compiles. The Mac version skips the examples and compiles.
The strange thing
It is really strange that the delayedAssign is evaluated in the environment
it is called from, and thus can have side effects.
so
x=2
y=3
delayedAssign(x, {y - 7; y+3})
gives
x
[1] 10
y
[1] 7
Both x and y changed.
More intuitive would have been the behavior
x=2
y=3
delayedAssign(x, local({y -
On Apr 26, 2012, at 11:59 AM, ghostwheel wrote:
It is really strange that the delayedAssign is evaluated in the environment
it is called from,
Not quite, it is evaluated in the environment you specify - and you have
control over both environments ... see ?delayedAssign
and thus can have
Simon Urbanek wrote
More intuitive would have been the behavior
delayedAssign(x, local({y - 7; y+3}) )
which only changes x.
That is questionable - I think it is more logical for both environments to
be the same as default. Just think if it -- the point here is to access
lazy
On Apr 27, 2012, at 00:10 , ghostwheel wrote:
Simon Urbanek wrote
More intuitive would have been the behavior
delayedAssign(x, local({y - 7; y+3}) )
which only changes x.
That is questionable - I think it is more logical for both environments to
be the same as default. Just think if
11 matches
Mail list logo
