Dear Listers,
I got this message when compiling a package:
* creating pgirmess-manual.tex ... OK
* checking pgirmess-manual.text ... ERROR
LaTex errors when creating DVI version.
This typically indicates Rd problems.
The message is quite explicit but I struggled a lot before understanding
that
On Sat, 29 Oct 2005, Patrick Giraudoux wrote:
Dear Listers,
I got this message when compiling a package:
* creating pgirmess-manual.tex ... OK
* checking pgirmess-manual.text ... ERROR
LaTex errors when creating DVI version.
This typically indicates Rd problems.
The message is quite
Thanks both Explanations perfectly clear. Also you make me discover
there was a 'pgirmess-manual.log', with error lines detected and
commented, indeed... (shame on me!!!) which would have been of great
help during the past decade... The misuse of _ should be the origin.
I should manage
Hi,
I was wondering, if it is possible to print out the
values of variables while you are in a for/while loop?
Like this for example:
for (i in 1:5) {
i
}
So what I want is this as output in the console:
1
2
3
4
5
Thanks in advance,
Martin
__
Eduardo Klein wrote:
Hi,
I'm looking for the way to make vector plot over a time line. This plot,
similar to the feather plot in Matlab, is a line in which every thick
(a time value) one vector is drawn with its length proportional to one
variable (wind speed, for example) and its
for (i in 1:5) {
+ cat(paste(i,\n))
+ }
1
2
3
4
5
for (i in 1:5) {
+ print(i)
+ }
[1] 1
[1] 2
[1] 3
[1] 4
[1] 5
=== 2005-10-29 18:03:13 您在来信中写道:===
Hi,
I was wondering, if it is possible to print out the
values of variables while you are in a for/while loop?
Like this
R-helpers,
Is there an easy way to call an external (C) program using .C or .Call
without including the code in a package. I know how to do it using
system(), but that doesn't seem to be a permanent or portable solution.
Initially I tried:
.Call('filepath.to.c.function', arg1)
and got this
Hi Walton.
.C/.Call are interfaces to _compiled_ C routines in a dynamically
loaded library (DLL or DSO - shared object). A progra
A program is often created from compiling C code into an executable.
We can call the executable via system, but we cannot access its routines
via .C/.Call.
So, if
Here is one additional solution:
read.table(textConnection(sub(abc, , B)), fill = TRUE)
It also works if there are more than 2 fields. If there can
be spaces in the lines then the sub should be modified to
translate abc to some unique character not appearing in
the lines and sep= should be
Dear r-help list members,
I'm experiencing problems getting type=b (or o or c) to work in
llines(). Try, e.g., the following scaled-down example:
x - factor(c(a, b, a, b))
y - c(1,2,1,2)
z - factor(c(A, A, B, B))
symbols - 1:2
lines - 1:2
colors - 1:2
zvals - levels(z)
xyplot(y~x|z, panel =
Hello,
I'm using R 2.2.0 on a Mac and attempting to use the RODBC package to
connect to a PostgreSQL server on the local network. I can't tell
whether my problem is in R, or in ODBC setup.
I got drivers from OpenLink, created a dsn and tested it using the
iODBC application. then I load
On 10/29/05, John Fox [EMAIL PROTECTED] wrote:
Dear r-help list members,
I'm experiencing problems getting type=b (or o or c) to work in
llines(). Try, e.g., the following scaled-down example:
x - factor(c(a, b, a, b))
y - c(1,2,1,2)
z - factor(c(A, A, B, B))
symbols - 1:2
lines - 1:2
One other comment. A for loop would seem to be
appropriate here since you are not using the result
of sapply anyways:
par.or - par(mfrow = c(3,3))
for(n in colnames(temp)) {
qqnorm(temp[,n], main = n)
qqline(temp[,n], col = red)
}
par(par.or)
On 10/28/05, Gabor Grothendieck [EMAIL
I am trying to do a forecasting exercise for a series, x. My forecast
model consists of the following
I first regress log(x) on time and dummy variables for each month.
lm(log(x) ~ time + monthly dummies)
I then use predict() to obtain a prediction for the next year.
I then fit an AR(6)/AR(12)
14 matches
Mail list logo