January 26, 2017 Code R functions special intrval

An update (v 0.1-1) of the **intrval** package was recently published on CRAN. The package simplifies interval related logical operations (read more about the motivation in this post).
So what is new in this version? Some of the inconsistencies in the 1st CRAN release have been cleaned up, and I have been pushed hard (see GitHub issue to implement all the 16
interval-to-interval operators.
These operators define the open/closed nature of the lower/upper
limits of the intervals on the left and right hand side of the `o`

in the middle as in `c(a1, b1) %[]o[]% c(a2, b2)`

.

Interval 1: | Interval 2: `[]` |
`[)` |
`(]` |
`()` |
---|---|---|---|---|

`[]` |
`%[]o[]%` |
`%[]o[)%` |
`%[]o(]%` |
`%[]o()%` |

`[)` |
`%[)o[]%` |
`%[)o[)%` |
`%[)o(]%` |
`%[)o()%` |

`(]` |
`%(]o[]%` |
`%(]o[)%` |
`%(]o(]%` |
`%(]o()%` |

`()` |
`%()o[]%` |
`%()o[)%` |
`%()o(]%` |
`%()o()%` |

The overlap of two closed intervals, [a1, b1] and [a2, b2],
is evaluated by the `%[]o[]%`

(`%[o]%`

is an alias)
operator (`a1 <= b1`

, `a2 <= b2`

).
Endpoints can be defined as a vector with two values
(`c(a1, b1)`

) or can be stored in matrix-like objects or a lists
in which case comparisons are made element-wise.

If lengths do not match, shorter objects are recycled.
These value-to-interval operators work for numeric (integer, real)
and ordered vectors, and object types which are measured at
least on ordinal scale (e.g. dates).
Note that interval endpoints
are sorted internally thus ensuring the conditions
`a1 <= b1`

and `a2 <= b2`

is not necessary.

```
c(2, 3) %[]o[]% c(0, 1)
list(0:4, 1:5) %[]o[]% c(2, 3)
cbind(0:4, 1:5) %[]o[]% c(2, 3)
data.frame(a=0:4, b=1:5) %[]o[]% c(2, 3)
```

If lengths do not match, shorter objects are recycled. These value-to-interval operators work for numeric (integer, real) and ordered vectors, and object types which are measured at least on ordinal scale (e.g. dates).

`%)o(%`

is used for the negation of two closed interval overlap (`%[o]%`

),
directional evaluation is done via the operators
`%[<o]%`

and `%[o>]%`

.
The overlap of two open intervals
is evaluated by the `%(o)%`

(alias for `%()o()%`

).
`%]o[%`

is used for the negation of two open interval overlap,
directional evaluation is done via the operators
`%(<o)%`

and `%(o>)%`

.
Overlap operators with mixed endpoint do not have
negation and directional counterparts.

Equal | Not equal | Less than | Greater than |
---|---|---|---|

`%[o]%` |
`%)o(%` |
`%[<o]%` |
`%[o>]%` |

`%(o)%` |
`%]o[%` |
`%(<o)%` |
`%(o>)%` |

Thanks for all the feedback so far and please keepâ€™em coming: leave a comment below or use the issue tracker to provide feedback or report a problem.

I moved to Canada in 2008 to start a postdoctoral fellowship with Prof. Subhash Lele at the stats department of the University of Alberta. Subhash at the time just published a paper about a statistical technique called data cloning. Data cloning is a way to use Bayesian MCMC algorithms to do frequentist inference. Yes, you read that right.

- Fitting removal models with the detect R package
- Shiny slider examples with the intrval R package
- Phylogeny and species traits predict bird detectability
- PVA: Publication Viability Analysis, round 3
- The progress bar just got a lot cheaper

ABMI (7) ARU (1) Alberta (1) BAM (1) C (1) CRAN (1) Hungary (2) JOSM (2) MCMC (1) PVA (2) PVAClone (1) QPAD (3) R (20) R packages (1) abundance (1) bioacoustics (1) biodiversity (1) birds (2) course (2) data (1) data cloning (4) datacloning (1) dclone (3) density (1) dependencies (1) detect (3) detectability (3) footprint (3) forecasting (1) functions (3) intrval (4) lhreg (1) mefa4 (1) monitoring (2) pbapply (5) phylogeny (1) plyr (1) poster (2) processing time (2) progress bar (4) publications (2) report (1) sector effects (1) shiny (1) single visit (1) site (1) slider (1) slides (2) special (3) species (1) trend (1) tutorials (2) video (4) workshop (1)