Displaying 20 results from an estimated 23 matches for "corers".
Did you mean:
coreos
2019 Nov 15
2
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
> > And indeed I think you are right on spot and this would mean
> > that indeed the implicit class
> > "matrix" should rather become c("matrix", "array").
>
> I've made up my mind (and not been contradicted by my fellow R
> corers) to try go there for R 4.0.0 next April.
I'm not enthusiastic about matrices extending arrays.
If a matrix is an array, then shouldn't all vectors in R, be arrays too?
> #mockup
> class (1)
[1] "numeric" "array"
Which is a bad idea.
It contradicts the central...
2019 Dec 26
3
best way to build from Git
...ry is the
>> same as the source directory.
(I have not tried, as I as R-corer do work with svn, but) If
this is true, then that is a pity indeed.
I have stopped of *ever* building in the source directory many
years ago, and I'm pretty sure that is the case for the vast
majority of R-corers.
>> Makefile.in has some odd stuff that might be related,
>> like why is it checking for "$(srcdir)/doc/FAQ" rather
>> than "$(top_builddir)/doc/FAQ"? Conversely, there is a
>> check for "$(top_builddir)/.git" which I would expe...
2019 Nov 10
2
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
.......
>>
>> And indeed I think you are right on spot and this would mean
>> that indeed the implicit class
>> "matrix" should rather become c("matrix", "array").
>
> I've made up my mind (and not been contradicted by my fellow R
> corers) to try go there for R 4.0.0 next April.
>
> I've found the few places in base R that needed a change (to
> pass 'make check-all' in the R sources) and found that indeed a
> overzealous check in 'Matrix' needed also a change (a place
> where the checking code...
2019 Nov 14
2
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
......
> >
> > And indeed I think you are right on spot and this would mean
> > that indeed the implicit class
> > "matrix" should rather become c("matrix", "array").
>
> I've made up my mind (and not been contradicted by my fellow R
> corers) to try go there for R 4.0.0 next April.
I can't seem to find the previous thread, so would you mind being a
bit more explicit here? Do you mean adding "array" to the implicit
class? Or adding it to the explicit class? Or adding it to inherits?
i.e. which of the following results...
2019 Nov 11
2
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...spot and this would mean
>>>> that indeed the implicit class
>>>> "matrix" should rather become c("matrix", "array").
>>>
>>> I've made up my mind (and not been contradicted by my fellow R
>>> corers) to try go there for R 4.0.0 next April.
>>>
>>> I've found the few places in base R that needed a change (to
>>> pass 'make check-all' in the R sources) and found that indeed a
>>> overzealous check in 'Matrix' needed also...
2019 Nov 02
6
head.matrix can return 1000s of columns -- limit to n or add new argument?
Thanks Martin and Peter,
I agree that we can be careful and narrow and still see a nice improvement
in behavior. While Herve's point is valid and I understand his frustration,
I think staying within the matrix vs c(matrix, array) space is the right
scope for this work in terms of fiddling with inheritance.
As another point, I don't know off the top of my head of any other classes
which
2019 Dec 26
3
best way to build from Git
Dear R-devel,
I checked out a recent copy of R via Subversion and made a few changes to the code. I wanted to commit them locally to my repo, just to stay organized and keep them separate from other changes I plan to make. However, I was not able to commit them because I don't think SVN allows this?
Plan B, check out a Git mirror of R, https://github.com/wch/r-source/
It has some
2024 Apr 11
1
[External] Re: Repeated library() of one package with different include.only= entries
> I would assume that
> library(Matrix, include.only="isDiagonal")
> implies that only `isDiagonal` ends up on the search path
This could also be a reasonable behavior, but neither does that happen
today.
> I think a far better approach to solve Michael's problem is simply to use
> fac2sparse <- Matrix::fac2sparse
This does not fully simulate attachment, e.g.
2019 Nov 10
0
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...should be slightly
> changed ....
>
> And indeed I think you are right on spot and this would mean
> that indeed the implicit class
> "matrix" should rather become c("matrix", "array").
I've made up my mind (and not been contradicted by my fellow R
corers) to try go there for R 4.0.0 next April.
I've found the few places in base R that needed a change (to
pass 'make check-all' in the R sources) and found that indeed a
overzealous check in 'Matrix' needed also a change (a place
where the checking code assume class(<matrix&...
2007 Nov 30
1
Trivial formatting typo in summary(lm()) (PR#10480)
Full_Name: Jeffrey Racine
Version: 2.6.1 and previous...
OS: FreeBSD
Submission from: (NULL) (130.113.139.86)
Hi.
I almost feel bad reporting this, but here goes.
The summary() for lm() (and possibly others?) uses a capitalized `S' in Multiple
R-Squared but a lowercase `s' in Adjusted R-squared. For instance,
Residual standard error: 0.5608 on 202 degrees of freedom
Multiple
2024 Apr 15
1
[External] Re: Repeated library() of one package with different include.only= entries
I think we should try to advance and hopefully finalize this
thread before we forget about it ..
>>>>> Michael Chirico n Thu, 11 Apr 2024 09:10:11 -0700 writes:
>> I would assume that
>> library(Matrix, include.only="isDiagonal")
>> implies that only `isDiagonal` ends up on the search path
> This could also be a reasonable
2019 Nov 10
0
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...;> And indeed I think you are right on spot and this would mean
>>> that indeed the implicit class
>>> "matrix" should rather become c("matrix", "array").
>>
>> I've made up my mind (and not been contradicted by my fellow R
>> corers) to try go there for R 4.0.0 next April.
>>
>> I've found the few places in base R that needed a change (to
>> pass 'make check-all' in the R sources) and found that indeed a
>> overzealous check in 'Matrix' needed also a change (a place
>> where...
2019 Nov 14
0
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...;> And indeed I think you are right on spot and this would mean
>>> that indeed the implicit class
>>> "matrix" should rather become c("matrix", "array").
>>
>> I've made up my mind (and not been contradicted by my fellow R
>> corers) to try go there for R 4.0.0 next April.
>
> I can't seem to find the previous thread, so would you mind being a
> bit more explicit here? Do you mean adding "array" to the implicit
> class?
It's late in Europe ;-)
That's my understanding. I think the plan is...
2009 Apr 21
8
incorrect output and segfaults from sprintf with %*d (PR#13667)
Full_Name: Wacek Kusnierczyk
Version: 2.10.0 r48365
OS: Ubuntu 8.04 Linux 32bit
Submission from: (NULL) (129.241.110.141)
sprintf has a documented limit on strings included in the output using the
format '%s'. It appears that there is a limit on the length of strings included
with, e.g., the format '%d' beyond which surprising things happen (output
modified for conciseness):
2008 Jan 22
3
gctorture and proc.time (PR#10600)
In R version 2.6.1 (2007-11-26)
and R version 2.6.1 Patched (2008-01-19 r44061)
on openSUSE 10.2 (X86-64)
> gctorture()
> proc.time()
Error: protect(): protection stack overflow
The problem with this is that then
R CMD check --use-gct foo
ALWAYS FAILS with
> cat("Time elapsed: ", proc.time() - get("ptime", pos = 'CheckExEnv'),"\n")
Error in
2014 Feb 27
1
R and LANGUAGE
Diverted from ESS-help.
It is really about R's LANGUAGE, locales and
then a wish for sessionInfo() :
>>>>> Sparapani, Rodney <rsparapa at mcw.edu>
>>>>> on Thu, 20 Feb 2014 19:39:33 +0000 writes:
>> Just guessing: perhaps this is something that is set when
>> R is initialized and not queried every time something is
>>
2019 Nov 12
0
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...; >>>> that indeed the implicit class
> >>>> "matrix" should rather become c("matrix", "array").
> >>>
> >>> I've made up my mind (and not been contradicted by my fellow R
> >>> corers) to try go there for R 4.0.0 next April.
> >>>
> >>> I've found the few places in base R that needed a change (to
> >>> pass 'make check-all' in the R sources) and found that indeed a
> >>> overzealous check in '...
2003 Aug 16
4
unclass
Have I been sleeping in class?
rw1071 from CRAN, windows XP
incidencia is made by a call to tapply
> class(incidencia)
[1] "array"
> incidencia <- unclass(incidencia)
> class(incidencia)
[1] "array"
Kjetil Halvorsen
2019 Nov 15
5
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...spot and this would mean
>>>> that indeed the implicit class
>>>> "matrix" should rather become c("matrix", "array").
>>>
>>> I've made up my mind (and not been contradicted by my fellow R
>>> corers) to try go there for R 4.0.0 next April.
>>
>> I can't seem to find the previous thread, so would you mind being a
>> bit more explicit here? Do you mean adding "array" to the implicit
>> class?
> It's late in Europe ;-)
>...
2020 Jan 21
2
class(<matrix>) |--> c("matrix", "arrary") -- and S3 dispatch
...gt;> that indeed the implicit class
> >>>>> "matrix" should rather become c("matrix", "array").
> >>>>
> >>>> I've made up my mind (and not been contradicted by my fellow R
> >>>> corers) to try go there for R 4.0.0 next April.
>
> >>> I can't seem to find the previous thread, so would you mind being a
> >>> bit more explicit here? Do you mean adding "array" to the implicit
> >>> class?
>
> >>...