like UTC).
Cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
function that was used
instead.
cheers, Jari Oksanen
On 23 Aug 2018, at 23:46 pm, Duncan Murdoch
mailto:murdoch.dun...@gmail.com>> wrote:
First, some general comments:
This sounds like a useful package.
I would guess it has very little impact on runtime efficiency except when
attaching
:
"R_DEFAULT_PACKAGES=utils,grDevices,graphics,stats"
So these pass R CMD check and are an "industrial standard". Changing
this will be break half of CRAN packages.
Cheers, Jari Oksanen
On 13/03/18 13:47, Martin Maechler wrote:
Adrian Dușa
on Tue, 13 Mar 2018 09:17:08 +0200 wri
This is exactly the instruction given in https://xkcd.com/1597/
cheers, J.O.
On 25/01/18 14:48, Mario Emmenlauer wrote:
Hi Duncan!
I think there are many users whose first experiences with git where frustrating,
and trust me, many people here can relate to your pain. I can certainly say that
It is not about "really arge total number of observations", but:
set.seed(4711);tabs <- r2dtable(1e6, c(2, 2), c(2, 2)); A11 <- vapply(tabs,
function(x) x[1, 1], numeric(1));table(A11)
A11
0 1 2
166483 666853 14
There are three possible matrices, and these come out in propo
Have you tried using tools:::package_native_routine_registration_skeleton()? If
you don't like its output, you can easily edit its results and still avoid most
pitfalls.
Cheers, Jari Oksanen
From: R-devel on behalf of Berend Hasselman
Sent: 1
ot
yet implemented for multivariate lm()" which of course is a natural and correct
solution to the problems.
Cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
); /* not really the rank,
but no. of columns */
SET_VECTOR_ELT(qr, 2, qraux);
SET_VECTOR_ELT(qr, 3, pivot);
UNPROTECT(4); /* qr, x, pivot, qraux */
return qr;
}
cheers, Jari Oksanen
From: R-devel
> On 25 Mar 2016, at 11:45 am, peter dalgaard wrote:
>
>>
>> On 25 Mar 2016, at 10:08 , Jari Oksanen wrote:
>>
>>>
>>> On 25 Mar 2016, at 10:41 am, peter dalgaard wrote:
>>>
>>> As I see it, the display showing the first p <
magnitude of
> the noise is important information.
>
But then you should use Factor Analysis which has that concept of “noise”
(unlike PCA).
Cheers, Jari Oksanen
>> On 25 Mar 2016, at 00:02 , Steve Bronder wrote:
>>
>> I agree with Kasper, this is a 'big'
have seen it. I
don’t know how this is interpreted currently, but you may ask the current
owner, Nokia.
Cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
switches only when configure is overwritten. Normal
compilation with ./configure works OK and finds Tcl/Tk, but a couple of times
per year the configure seems to change so much that I need to use these
switches. I have had this problem a couple of years.
If I need to guess, I do something wron
Dear R-Devels,
My apologies for using a wrong list. Please ignore my messages. I would undo
this if I only could, but what's done can't be undone (not the the first time
in my life when I've learnt this).
Cheers, Jari Oksanen
On 13/09/2014, at 08:13 AM, Jari Oksanen wrote:
&g
changes are small and isolated
bug fixes, I have pushed them directly to the vegan upstream, though. I have
found this pretty good way of working in github.
Cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
See ?format.pval
cheers, jari oksanen
From: r-devel-boun...@r-project.org [r-devel-boun...@r-project.org] on behalf
of Michael Friendly [frien...@yorku.ca]
Sent: 07 May 2014 17:02
To: r-devel
Subject: [Rd] historical significance of Pr(>Chisq) < 2
he code
really should be reproducible, but they often are the hardest to reproduce.
Nothing CRAN people do can help with sloppy code scientists write for
publications. You know, they are scientists -- not engineers.
Cheers, Jari Oksanen
>
> Leaving the issue of compilation out, a package whic
pted
because it fits the current CRAN policy, and probably would need to change if
CRAN policy changes.
Cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
then build old R and then get the old versions of packages. It is nice if the
last step is made easier.
Cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
erprets/renders it
> differently shows that normality and strangeness is quite relative
> though.
>
As a user DEC LA120 terminal I expect the following:
> cat("a\b^\n")
â
>
Everything else feels like a bug.
Cheers, Jari Oksanen
__
Henrik,
On 14/10/2013, at 00:35 AM, Henrik Bengtsson wrote:
> In R 3.1.0 (~April 2014), support for vignettes in inst/doc/ will go
> away (and probably much sooner for CRAN submission), e.g.
>
> I've been sticking with inst/doc/ for backward compatible reasons so
> that I can use a "fallback" ins
e with the thought that the developers can’t go on forever,
so eventually lme4 will become stable when the machine precision forces it to
be rounded up to 1.0"
Cheers, Jari Oksanen
From: r-devel-boun...@r-project.org [r-devel-boun...@r-project.org] on be
"What we've got here is failure to communicate. Some men you just can't reach.
So you get what we had here last week, which is the way he wants it. Well, he
gets it. I don't like it any more than you men." (from "Cool hand Luke" -- but
whose fault?)
Cheers,
stock R of my system (which still runs in 2.14
series) with stable packages, or experimental R with experimental versions of
packages.
I think the rule is that you can do anything as long as you don't complain. If
you want to complain, you must follow the instructions.
Chee
This should be FAQ 0.0. No other thing is asked as frequently as this. This is
the FAQest of all FAQs, and a mother of all FAQs. At least this should be in R
posting guide: "Read FAQ 7.31 before posting!"
Cheers, Jari Oksanen
On 07/02/2013, at 12:13 PM, R. Michael Weylandt wrote:
&g
Gav,
This is off-list since I only wonder what you are trying to do. It seems to me
that you're trying something much too elegant and complicated. One thing that I
have learnt to avoid is muck up with environments: that is calling trouble. One
day they will change R and you will get errors that
t;) else scale.
I trust you find an elegant solution (if you think this is worth fixing).
Cheers, Jari Oksanen
PS. Sorry for the top posting: cannot help with the email system I have in my
work desktop.
From: r-devel-boun...@r-project.org [r-devel-boun...@
finds the 'scale' directly instead of looking at the
attributes of the input data, and works like expected:
sol <- princomp(x)
all.equal(predict(sol), predict(sol, newdata=x))
## [1] TRUE
I don't have any nifty solution to this -- only
) it really exports only those files that really are under version
control. More often than once I have had some non-svn files in my svn directory
so that *my* version of the package works, but the one actually in subversion
fails.
Cheers, Jari Oksanen
--
Jari Oksanen, Dept Biology, Univ Oulu, 90014
in 2.12.2 and R-to-be-2.15.0 in Linux, and I expect the release version to
pass all these. The development version can fail in older R, but then we
(the team) must judge if we merge such failing features to the release.
Cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
On 14/10/11 19:00 PM, "Uwe Ligges" wrote:
>
>
> On 14.10.2011 16:15, Duncan Murdoch wrote:
>> On 14/10/2011 10:10 AM, Jari Oksanen wrote:
>>> On 14/10/11 16:26 PM, "Duncan Murdoch" wrote:
>>>
>>>> On 14/10/2011 9:18 AM, Jari Ok
On 14/10/11 16:26 PM, "Duncan Murdoch" wrote:
> On 14/10/2011 9:18 AM, Jari Oksanen wrote:
>>>
>> Uwe& others,
>>
>> This is OK if you want to identify the cause of the problems. However,
>> the basic problem was that checking required someth
ithout
these packages, but it may have some extra options or functionality with
those packages. This sounds like a suggestion to me, but in R language
suggestions cannot be refused.
Cheers, jari oksanen
>
> On 13.10.2011 03:00, Yihui Xie wrote:
> > You have this in Jevons.Rd:
> >
hing that he felt was missing, so that's at least two people who
>> will be happy to see this added.
>>
>
> And of course, I was teaching a course based on Agresti & Franklin:
> "Statistics, The Art and Science of Learning from Data", when I realiz
-- oldtukeyplot.ps2010-12-14 12:06:07.0 +0200
+++ /Volumes/TIKKU/tukeyplot.ps2010-12-14 12:13:32.0 +0200
@@ -172,5 +172,5 @@
0 setgray
0.00 setlinewidth
-[ 3.00 5.00] 0 setdash
+[ 0.00 0.00] 0 setdash
np
660.06 91.44 m
So 0.00 setlinewidth worked, but [0.00 0.00] 0 setdash f
ged
since r51093 in trunk and never in R-2-12-branch). I know nothing about
PostScript so that I cannot say anything more (and I know viewers can fail
with standard conforming PostScript but it is a bit disconcerting that two
viewers fail when they worked earlier).
Cheers, Jari Oksanen
he main subject,
and it seems that my installation of Ubuntu 10.04 is not affected by the
problem but has quite regular fonts -- no Wine today. Better that I shut
up).
Cheers, Jari Oksanen
> It is also not using pango, and so not selecting fonts the same way as
> on Linux.
>
r with the default X11() which has type = 'Xlib' (unlike
documented in ?X11: 'cairo' is available but 'Xlib' still used).
What ever this is worth of (if this is worthless, I'll surely hear about
it).
Cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
On 25/05/10 23:25 PM, "Ben Bolker" wrote:
>
Just curious: is there a particular reason why install.packages()
gives a
> warning in normal use when 'lib' is not specified (e.g. argument
'lib' is
> missing: using '/usr/local/lib/R/site-library' )? It would
seem to me that
> this is normal behav
5). There has been no response to either of these
report. A News message of April 29 in R-Forge front page predicts that
browser functionality will follow "soon". So there is hope...
Cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
On 06/02/2010 18:10, "Duncan Murdoch" wrote:
> On 06/02/2010 10:39 AM, Christophe Genolini wrote:
>> Hi the list,
>>
>> According to what I know, the Canberra distance between X et Y is : sum[
>> (|x_i - y_i|) / (|x_i|+|y_i|) ] (with | | denoting the function
>> 'absolute value')
>> In the so
a long time and people have adapted. The
window of opportunity for another interpretation was when the checks for
undefined request() was added to the R CMD check routines in 2005, but
then it was decided that "suggests" should be near equivalent to
"depends", and this w
hat does the 'rename' has a switch to overturn
the standard 'rename' system call, and prompt for the removal of the 'new'
file. However, this switch is usually not the default in unixy systems,
unless defined so in the shell start up script of the user.
Cheers, Jari O
. I also installed R 2.9.1 for
MacOS to see that there neither is a change in 'eurodist' in the Mac
distribution. My virgin eurodist in Mac was clean, with all its errors. All
this hints that you have a local copy of malformed eurodist in your
computer. Perhaps
rm(eurodist)
eurodist
will he
ues[-n]
+evalus <- e$values
list(points = points, eig = if(eig) ev, x = if(x.ret) x,
ac = if(add) add.c else 0,
- GOF = sum(ev)/c(sum(abs(evalus)), sum(evalus[evalus > 0])))
+ GOF = sum(ev)/c(sum(evalus), sum(evalus[evalus > 0])))
t;- function(object, ...) NULL
or a function that returns NULL if there are no weights. In R 2.6.2 the
operation was this de facto, since NULL was returned anyway.
Is there a way to circumvent this feature? (It is a "feature" because it
is designed to work like this).
cheers, jari ok
orge.r-project.org/tracker/index.php?func=detail&aid=139&group_id=34&atid=194
Thomas Petzold even posted there the probable cure. I hope the issue
will be solved some day soon.
cheers, jari oksanen
--
Jari Oksanen <[EMAIL PROTECTED]>
__
R
Full_Name: Jari Oksanen
Version: 2.6.2 RC (2008-02-07 r44369)
OS: Linux
Submission from: (NULL) (130.231.102.145)
Even if function xspline() is called with argument draw=FALSE, it requires a
graphics device (that it won't use since it was draw=FALSE). I run into this
because I intended t
a
bug as a duplicate of # and mark it as resolved without generating
awfully lot of mail. Then it would be humanly possible to adopt a more
neutral way of answering to people who reported bugs in latest releases.
Probably that won't happen in the current environment.
Cheers, Jari Oksanen
g in a function or a bug in the documentation (usually the
latter).
cheers, jari oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
is very sensible I think:
>
> If you have a longish boxplot() or bxp() command,
> and you just want to go from vertical to horizontal or vice
> versa, it makes most sense just to have to change the
> 'horizontal' flag and not having to see if there are other 'x*'
> and or 'y*' arguments that all need to be changed as well.
>
Except that you must change xaxt/yaxt and log="x"/log="y" which do not
follow the "along the box" logic, and behave differently than
xlim/ylim.
Nothing of this is fatal, but this probably needs more than one
iteration to find which way each of the x* and y* arguments works.
cheers, jari oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
gt;
> which looks reasonable. Would this become
>
>> p <- as.character(NA)
>> paste("the value of p is", p)
> [1] NA
>
> under your proposal? (In a quick search I was unable to find a real
> example where this would happen, but it would worry me...)
At least stop() seems to include such a case:
message <- paste(args, collapse = "")
and we may expect there are NAs sometimes in stop().
cheers, jazza
--
Jari Oksanen, Oulu, Finland
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
but I don't know any trick for Sweave
(and it's a nuisance in sink() as well).
cheers, jari oksanen
--
Jari Oksanen -- Dept Biology, Univ Oulu, FI-90014 Oulu, Finland
Ph. +358 85531526, cell +358 405136529, fax +358 85531061, skype jhoksane
email [EMAIL PROTECTED], homepage http://cc.ou
more relaxed dependence checking allowing calls to other
packages in functions. I've been a Linux user since Red Hat 5.1 and I
know what is a dependence hell (package depending on package
depending ... depending on broken package). There already are some signs
of that in R, in particular in u
already
> installed pages untouched. So you end up with mixed man pages from
> different versions of the package :-/
>
I have observed this, too.
cheers, Jari Oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
ce. For the sake of Sweave and
sink, I'd prefer the one place to be stdout instead of stderr.
Best wishes, Jari Oksanen
--
Jari Oksanen <[EMAIL PROTECTED]>
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
ertain entry. It seems that "Requires" means that a package
is always required, "Suggests" means that the package is required in
check (with a threat of error), but only suggested for normal use, and
"Enhances" means that the package only is suggested. It does not matt
hing the limits of reason.
However, in general this is "easy" to solve: scale() before the
analysis and replace NaN with 0 (prcomp handles zeros). For instance,
x <- scale(x)
x[is.nan(x)] <- 0
prcomp(x)
(and a friendly prcomp() would do this internally.)
cheers, jari oksanen
-
0 1
It seems that "marginal" towns (Athens, Lisbon, Stockholm, Copenhagen)
have largest discrepancies.
It also seems that the names are not 'localized', but weird English
forms are used for places like København and Wien so dear to the R core
developers.
cheers, jari
y
packages. Therefore agian the ERROR.
This was not a complaint nor a suggestion to change the tools, but only
an observation. I'm quite willing to work with this set of rules and
I'll comply with them. Again, the grammar confused me, since I didn't
know that suggestions are so absolu
use \dontrun{} for a
non-recommended package, the check would fail and I would get the needed
information: so why should the check fail already when checking
DESCRIPTION?
cheers, jari oksanen
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
it would be up to the user to get
those extra packages needed without requiring them in R CMD check?
I stumbled on this with earlier versions of R, and then my solution was
to suggest nothing.
cheers, jari oksanen
--
Jari Oksanen -- Dept Biology, Univ Oulu, 90014 Oulu, Finland
Ph. +358 8 55
like Warning with",
"\\section{Warning }{} ~"),
- ""),
+ "}"),
seealso = paste("\\seealso{ ~~objects to See Also as",
- "\\code{\\link{~~fun~~}}, ~~~ }"),
+ &
with a
reference to function help.
I'm sorry for the formatting of the diff file: my emacs/ESS is cleverer
than I and changes indentation and line breaks against my will.
cheers, jari oksanen
--
Jari Oksanen -- Dept Biology, Univ Oulu, 90014 Oulu, Finland
Ph. +358 8 5531526, cell +358 40 513652
eplaces rep.octonion with \method{rep}{octonion}, removes __
from description (these cause latex errors), remove a hanging top level
text "Make other sections...", and removes a link to non-existent
~~fun~~ (I'm not sure if adding a real keyword is necessar
fails in R CMD check unless you add "..." in all
specific functions...). The real work is always done in coca.matrix (or
coca.default), and the others just chew your data into suitable form
for your workhorse.
If then somebody thinks that they need all possible variables as
'explanatory' variables (or perhaps constraints in your case), they
just call the function as
coca(matx, maty, matz)
And if you have coca.data.frame they don't need 'quacking' with extra
steps:
coca.data.frame <- function(dfx, dfy dfz) coca(as.matrix(dfx),
as.matrix(dfy), as.matrix(dfz)).
This you call as coca(dfx, dfy, dfz) and there you go.
The essential feature in formula is the ability to define the model.
Don't give it away.
cheers, jazza
--
Jari Oksanen, Oulu, Finland
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
65 matches
Mail list logo
