Displaying 20 results from an estimated 200 matches similar to: "Semantics of sequences in R"
2015 Aug 21
2
[PATCH 2/2] core/graphics: fix lss16 parsing
getnybble() needs to return four bits at a time from every byte.
During rle decode, rows are rounded to an integer number of bytes.
The rle length needs to be able to hold values > 255.
Signed-off-by: Chas Williams <3chas3 at gmail.com>
---
core/graphics.c | 35 +++++++++++++++++++++--------------
1 file changed, 21 insertions(+), 14 deletions(-)
diff --git a/core/graphics.c
2015 Aug 20
4
boot logo via boot.txt
We recently have upgraded syslinux and have noticed that the boot logo
code via boot.txt no longer works. I have a couple patches that get it
close to working but I appear to be having trouble with color maps. Is
there someone would want to help me finish figuring this out?
Any interest in the patches I have to fix the rle decoder?
2009 Oct 27
1
Detection Times and Poisson Distribution
Dear All,
Apologies if my questions are too basic for this list.
I am given a set of data corresponding to list of detection times (real,
non-integer numbers in general) for some events, let us say nuclear
decays to fix the ideas.
It is a small dataset, corresponding to about 400 nuclear decay times.
I would like to test the hypothesis that these decay times are
Poissonian-distributed.
What is
2012 Jul 06
3
Compare date Oracle with Sys.time
I would like to import only datas of my table where DATE>today-7days.
But my datas in Oracle are 'dates' and in R are 'characters'.
now_7<-format(Sys.time()-(7*60*60*24), "%Y-%m-%d 00:00:00")
How to do?
--
View this message in context: http://r.789695.n4.nabble.com/Compare-date-Oracle-with-Sys-time-tp4635624.html
Sent from the R help mailing list archive at
2011 Apr 14
1
Possible bug in 'relist()' and/or 'as.relistable()'
Dear list,
I think I just stumbled across a bug in either 'relist()' and/or
'as.relistable()'. It seems that 'pairlists' can only be un- and relisted as
long as they're not nested:
Good:
a <- as.relistable(as.pairlist(list(a=1, b=2)))
a <- unlist(a)
relist(a)# Works
Bad:
a <- as.relistable(as.pairlist(list(a=1, b=2, c=list(c.1=1, c.2=2))))
a <- unlist(a)
2016 Oct 10
0
aVirtualTwins available on CRAN
[markdown format]
I'm glad to introduce you the new package aVirtualTwins. This package is an adaptation of VirtualTwins method of subgroup identification from [Foster, J. C., Taylor, J. M.G. and Ruberg, S. J. (2011)](http://onlinelibrary.wiley.com/doi/10.1002/sim.4322/abstract).
### Explanation
Virtual Twins has been created to find subgroup of patients in a random clinical trial with
2016 Oct 10
0
aVirtualTwins available on CRAN
[markdown format]
I'm glad to introduce you the new package aVirtualTwins. This package is an adaptation of VirtualTwins method of subgroup identification from [Foster, J. C., Taylor, J. M.G. and Ruberg, S. J. (2011)](http://onlinelibrary.wiley.com/doi/10.1002/sim.4322/abstract).
### Explanation
Virtual Twins has been created to find subgroup of patients in a random clinical trial with
2009 Mar 20
2
struggling with pairlists
I would like to create a vector of pairlist (flag, binary_value) like:
(variable ="TrendOff", value = 0)
(variable ="MOdwt", value = 1)
(variable ? "ZeroPadding", value =1)
................................................
I tried the following syntax but the emcompassing list (that I called "flags") is not made up of pairlists. Instead it
2003 Feb 14
1
pairlists (was: data manipulation function descriptions)
> -----Original Message-----
> From: Luke Tierney [mailto:luke at stat.uiowa.edu]
> R does not provide a pairlist data structure. This creates a dilemma
> when translating some list-based xlispstat code, or, more
> importantly, when implementing an algorithm for which parilists are
> the natural data structure to use.
> ...
> Pairlists were and still are used internally
2016 Oct 12
2
How to assign NULL value to pairlist element while keeping it a pairlist?
Thanks, this was what I expected. There is a desire to eliminate the
usage of pairlist from user code, which suggests the alternative of
allowing for function arguments to be stored in lists. That's a much
deeper change though.
On Wed, Oct 12, 2016 at 12:31 PM, Henrik Bengtsson
<henrik.bengtsson at gmail.com> wrote:
> Michael, thanks for this info.
>
> I've stumbled upon
2012 Jul 26
3
rep fails on pairlist
This code which has worked for years in R but fails under R-devel:
> R.version.string
[1] "R Under development (unstable) (2012-07-25 r59963)"
>
> n <- 3
> f <- function(x) {}
> formals(f) <- rep(formals(f), n) ##
Error in rep(formals(f), n) : replication of pairlists is defunct
The message suggests that the change was intentional.
Why was this functionality
2016 Oct 19
2
How to assign NULL value to pairlist element while keeping it a pairlist?
On Sat, Oct 15, 2016 at 2:00 AM, Martin Maechler
<maechler at stat.math.ethz.ch> wrote:
>>>>>> Michael Lawrence <lawrence.michael at gene.com>
>>>>>> on Wed, 12 Oct 2016 15:21:13 -0700 writes:
>
> > Thanks, this was what I expected. There is a desire to
> > eliminate the usage of pairlist from user code, which
> >
2011 May 04
4
Recursive objects
Hi all,
Does anyone have a comprehensive list of recursive-type objects in R?
is.recursive defines them as by exclusion: "most types of objects are
regarded as recursive, except for vector types, ?NULL? and symbols
(as given by ?as.name?)." I think this that means recursive objects
are:
* lists
* pairlists
* calls
* expressions
Did I miss anything?
Hadley
--
Assistant
2020 Mar 17
3
new bquote feature splice does not address a common LISP @ use case?
Dear R-devel,
There is a new feature in R-devel, which explicitly refers to LISP @
operator for splicing.
> The backquote function bquote() has a new argument splice to enable splicing a computed list of values into an expression, like ,@ in LISP's backquote.
Although the most upvoted SO question asking for exactly LISP's @
functionality in R doesn't seems to be addressed by this
2016 Oct 12
2
How to assign NULL value to pairlist element while keeping it a pairlist?
Hi Henrik,
It would help to understand your use case for pairlists.
Thanks,
Michael
On Wed, Oct 12, 2016 at 9:40 AM, Michael Lawrence <michafla at gene.com> wrote:
> The coercion is probably the most viable workaround for now, as it's
> consistent with what happens internally for calls. All pairlists/calls
> are converted to list for subassignment, but only calls are
2016 Oct 12
2
How to assign NULL value to pairlist element while keeping it a pairlist?
Hi, I seem to not be able to assign NULL to an element of a pairlist
without causing it to be coerced to a plain list. For example:
> x <- pairlist(1, 2)
> class(x)
[1] "pairlist"
> x[1] <- list(NULL)
> class(x)
[1] "list"
This actually true for all [()<- assignments regardless of list value, e.g.
> x <- pairlist(1, 2)
> x[1] <- list(0)
[1]
2007 Oct 02
2
pairlist objects
Hi,
?pairlist gives no explanation about what exactly is the difference
between a pairlist and a list (except that a pairlist of length 0
is 'NULL'). So, what's a pairlist?
class(.Options)
[1] "pairlist"
Some strange things about the "pairlist" type:
> showClass("pairlist")
Error in getClass(Class) : "pairlist" is not a defined class
2009 Jun 17
2
list of data.frames?
I'm trying to build up a list of data.frames by "appending" one by one.
If x,y,z are data.frames, I can do
somelist <- list(x, y, z) (or even somelist <- list(x=x, y=y, z=z) to get
names)
But if I start with
somelist <- list(x,y) and now want to go from this to list(x,y,z) I'm stuck.
I've tried
append(somelist, z)
c(somelist, z)
list(somelist, z)
Each gives
2024 Apr 27
1
Should c(..., recursive = TRUE) and unlist(x, recursive = TRUE) recurse into expression vectors?
Reading the body of function 'AnswerType' in bind.c, called from 'do_c'
and 'do_unlist', I notice that EXPRSXP and VECSXP are handled identically
in the recurse = TRUE case.
A corollary is that c(recursive = TRUE) and unlist(recursive = TRUE)
treat expression vectors like expression(a, b) as lists of symbols and
calls. And since they treat symbols and calls as
2024 Jul 05
2
API for converting LANGSXP to LISTSXP?
Hi,
A common idiom in the R sources is to convert objects between LANGSXP
and LISTSXP by using SET_TYPEOF. However, this is soon going to be
disallowed in packages. From what I can see, there isn't currently a
direct way to convert between these two object types using the
available API. At the R level, one can convert calls to pairlists
with:
>