On 19/03/2012 17:01, Terry Therneau wrote:
R version 2.14.0, started with --vanilla
> table(c(1,2,3,4,NA), exclude=2, useNA='ifany')
1 3 4
1 1 1 2
This came from a local user who wanted to remove one particular response
from some tables, but also wants to have NA always reported for data
chec
Good morning,
I'm trying to draw a graph, and I'm using the following code.
test.matrix<-read.table("~/Desktop/Results/testgephi.csv", header = T,
sep=",")
colnames(test.matrix) <- gsub("X", "", colnames(test.matrix))
#drop first column
drops <- c("")
test.matrix<-test.matrix[,!(names(test.mat
if you don't mind going outside of R to create it, then check out
Graphviz: http://www.graphviz.org/Gallery.php
you may have to reformat your data a little, but this tool is great
for drawing graphs.
-Whit
On Tue, Mar 27, 2012 at 5:14 AM, MSousa wrote:
> Good morning,
>
>
> I'm trying to draw
CRAN has for some time had a policies page at
http://cran.r-project.org/web/packages/policies.html
and we would like to draw this to the attention of package maintainers.
In particular, please
- always send a submission email to c...@r-project.org with the package
name and version on the subje
> R Michael Weylandt
> on Mon, 26 Mar 2012 14:29:31 -0400 writes:
> In the source section of ?rlogis, we see:
> Source:
> ‘[dpr]logis’ are calculated directly from the definitions.
> ‘rlogis’ uses inversion.
> Should that read "[dpq]logis" instead?
yes, indeed;
Hi,
your code does not run in a fresh R environment:
Error in getClass(Class, where = topenv(parent.frame())) :
"graphAM" is not a defined class
If you don't provide working code, it's (too) much effort to help.
There are some graph packages arround.
Which you need depends on what you wa
On 03/27/2012 02:05 AM, Prof Brian Ripley wrote:
n 19/03/2012 17:01, Terry Therneau wrote:
R version 2.14.0, started with --vanilla
> table(c(1,2,3,4,NA), exclude=2, useNA='ifany')
1 3 4
1 1 1 2
This came from a local user who wanted to remove one particular response
from some tables, but als
I received the following note this AM. The problem is, I'm not quite
sure how to fix it.
Can one use PROTECT(coxlist(eval(PROTECT , do I create an
intermediate variable, or otherwise?
I'm willing to update the code if someone will give me a pointer to the
right documentation. This partic
On 27/03/2012 14:22, Terry Therneau wrote:
I received the following note this AM. The problem is, I'm not quite
sure how to fix it.
Can one use PROTECT(coxlist(eval(PROTECT , do I create an
intermediate variable, or otherwise?
You can, but I find it easiest to follow if you create an interm
On 12-03-27 9:22 AM, Terry Therneau wrote:
I received the following note this AM. The problem is, I'm not quite
sure how to fix it.
Can one use PROTECT(coxlist(eval(PROTECT , do I create an
intermediate variable, or otherwise?
I think both would work. The usual style in R sources is to us
Brian & Duncan:
Thanks. This was exactly what I needed to know.
Terry
On 03/27/2012 08:41 AM, Prof Brian Ripley wrote:
On 27/03/2012 14:22, Terry Therneau wrote:
I received the following note this AM. The problem is, I'm not quite
sure how to fix it.
Can one use PROTECT(coxlist(eval(PROTEC
One of the things I have noticed with the R 2.15.0 RC and --as-cran is
that the I have to bump the version number of the working copy of my
packages immediately after putting a version on CRAN, or I get an
message about version suitability. This is probably a good thing for
packages that I have
On 27.03.2012 16:17, Paul Gilbert wrote:
One of the things I have noticed with the R 2.15.0 RC and --as-cran is
that the I have to bump the version number of the working copy of my
packages immediately after putting a version on CRAN, or I get an
message about version suitability. This is proba
On Tue, Mar 27, 2012 at 7:52 AM, Prof Brian Ripley
wrote:
> CRAN has for some time had a policies page at
> http://cran.r-project.org/web/packages/policies.html
> and we would like to draw this to the attention of package maintainers. In
> particular, please
>
> - always send a submission email t
On 12-03-27 10:59 AM, Uwe Ligges wrote:
On 27.03.2012 16:17, Paul Gilbert wrote:
One of the things I have noticed with the R 2.15.0 RC and --as-cran is
that the I have to bump the version number of the working copy of my
packages immediately after putting a version on CRAN, or I get an
messa
On 27.03.2012 17:22, Paul Gilbert wrote:
On 12-03-27 10:59 AM, Uwe Ligges wrote:
On 27.03.2012 16:17, Paul Gilbert wrote:
One of the things I have noticed with the R 2.15.0 RC and --as-cran is
that the I have to bump the version number of the working copy of my
packages immediately after
On 27.03.2012 17:09, Gabor Grothendieck wrote:
On Tue, Mar 27, 2012 at 7:52 AM, Prof Brian Ripley
wrote:
CRAN has for some time had a policies page at
http://cran.r-project.org/web/packages/policies.html
and we would like to draw this to the attention of package maintainers. In
particular,
On 27/03/2012 15:17, Paul Gilbert wrote:
One of the things I have noticed with the R 2.15.0 RC and --as-cran is
that the I have to bump the version number of the working copy of my
packages immediately after putting a version on CRAN, or I get an
message about version suitability. This is probabl
2012/3/27 Uwe Ligges :
>
>
> On 27.03.2012 17:09, Gabor Grothendieck wrote:
>>
>> On Tue, Mar 27, 2012 at 7:52 AM, Prof Brian Ripley
>> wrote:
>>>
>>> CRAN has for some time had a policies page at
>>> http://cran.r-project.org/web/packages/policies.html
>>> and we would like to draw this to the a
On Mar 27, 2012, at 12:03 PM, Terry Therneau wrote:
> On 03/23/2012 10:58 AM, Simon Urbanek wrote:
>> This is my shot at a cheat sheet.
>> comments are welcome.
>>
>> Simon
>>
>>
> I was looking through the cheat sheet. It's nice. There are a few things in
> it that I can't find in the docu
FWIW: I have put the (slightly updated) sheet at
http://r.research.att.com/man/R-API-cheat-sheet.pdf
Note that it is certainly incomplete - but that is intentional to a) to fit the
space constraints and b) to show only the most basic things since we are
talking about starting with .Call -- adva
On Sat, Mar 24, 2012 at 1:07 PM, Duncan Murdoch
wrote:
> On 12-03-24 2:31 PM, Simon Urbanek wrote:
>>
>>
>> On Mar 24, 2012, at 12:43 PM, Duncan Murdoch wrote:
>>
>>> On 12-03-24 10:53 AM, Uwe Ligges wrote:
On 24.03.2012 06:58, Daniel Nordlund wrote:
>>
>> -Original
there's also Rgraphviz, although with 30,000+ edges it may not survive
*this* graph :-)
On Tue, Mar 27, 2012 at 4:11 AM, Whit Armstrong wrote:
> if you don't mind going outside of R to create it, then check out
> Graphviz: http://www.graphviz.org/Gallery.php
>
> you may have to reformat your dat
Is there a distinction as to NOTE vs. WARNING that is documented? I've
always assumed (wrongly?) that NOTES weren't an issue with publishing on
CRAN, but that they may change to WARNINGS at some point.
Is the process by which this happens documented somewhere?
Jeff
On 3/27/12 11:09 AM, "Gabor G
You should be capable of building R on Windows from the SVN sources or
daily source tarballs.
After all, when (as often happens) BioC has an inconsistent set of
source or binaries (like released packages depending on unreleased
packages, on unreleased versions), the BioC core team tell me to g
On Tue, Mar 27, 2012 at 10:30 AM, Prof Brian Ripley
wrote:
> You should be capable of building R on Windows from the SVN sources or daily
> source tarballs.
>
We are.
> After all, when (as often happens) BioC has an inconsistent set of source or
> binaries (like released packages depending on u
On 27.03.2012 19:10, Jeffrey Ryan wrote:
Is there a distinction as to NOTE vs. WARNING that is documented? I've
always assumed (wrongly?) that NOTES weren't an issue with publishing on
CRAN, but that they may change to WARNINGS at some point.
We won't kick packages off CRAN for Notes (but we
Thanks Uwe for the clarification on what goes and what stays.
Still fuzzy on the notion of "significant" though. Do you have an example
or two for the list?
Jeff
P.S.
I meant to also thank all of CRAN volunteers for the momentous efforts
involved, and it is nice to see some explanation of how w
2012/3/27 Uwe Ligges :
>
>
> On 27.03.2012 19:10, Jeffrey Ryan wrote:
>>
>> Is there a distinction as to NOTE vs. WARNING that is documented? I've
>> always assumed (wrongly?) that NOTES weren't an issue with publishing on
>> CRAN, but that they may change to WARNINGS at some point.
>
>
> We won't
An associated problem, for the wish list, is that it would be nice for
package developers to have a way to automatically distinguish between
NOTEs that can usually be ignored (e.g. a package suggests a package
that is not available for cross reference checks - I have several case
where the sugg
In case anyone is concerned that this regression will affect them, the
code was reverted to the 2.14.x behavior by
r58842 | ripley | 2012-03-26 08:12:43 -0400 (Mon, 26 Mar 2012) | 1 line
Changed paths:
M /branches/R-2-15-b
I have been wondering if it is possible to automate the checking
process to reduce human efforts, e.g. automatically check the packages
submitted to FTP, and send the package maintainer an email in case of
warnings or errors (otherwise just move it to CRAN); package
maintainers can appeal for a man
> I have been wondering if it is possible to automate the checking
> process to reduce human efforts, e.g. automatically check the packages
> submitted to FTP, and send the package maintainer an email in case of
> warnings or errors (otherwise just move it to CRAN); package
> maintainers can appeal
On Tue, Mar 27, 2012 at 6:52 AM, Prof Brian Ripley
wrote:
> CRAN has for some time had a policies page at
> http://cran.r-project.org/web/packages/policies.html
> and we would like to draw this to the attention of package maintainers. In
> particular, please
Thanks for the pointer - I did not kn
Lots of very sensible policies here. I have one request as someone
who has in several cases had to involve company lawyers over
intellectual property issues with packages on CRAN -- the first bullet
point on ownership of copyright and intellectual property rights could
be strengthened further.
To
On 27/03/2012 22:01, Ben Goodrich wrote:
In case anyone is concerned that this regression will affect them, the
code was reverted to the 2.14.x behavior by
r58842 | ripley | 2012-03-26 08:12:43 -0400 (Mon, 26 Mar 2012) | 1
36 matches
Mail list logo
