From: Philippe Veber <philippe.veber@gmail.com>
To: Edgar Friendly <thelema314@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Fwd: interval trees
Date: Sun, 12 Feb 2012 00:54:35 +0100 [thread overview]
Message-ID: <CAOOOohQmcTye+A1LnNgfOwQmTyPO23YYoNqxaUo=yoDkKz6C+g@mail.gmail.com> (raw)
In-Reply-To: <4F36D469.6070604@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
2012/2/11 Edgar Friendly <thelema314@gmail.com>
> On 02/11/2012 12:38 PM, Goswin von Brederlow wrote:
>
>> On Fri, Feb 10, 2012 at 10:07:05AM +0900, Francois Berenger wrote:
>>>
>>>> I need to use an interval tree.
>>>>
>>>> Biocaml has one, batteries have imap/iset, nice!
>>>>
>>>> Anyone have something like this but for non-overlapping intervals and
>> allowing interval insertion and removal with merging and spliting of the
>> internaly used intervals?
>>
>
> Yes, IMap / ISet (borrowed from camomile and improved) do this. I assume
> biocaml's is the same.
Actually no, biocaml_intervalTree keeps the inserted intervals untouched,
it is in fact pretty similar to an interval multimap, with some specialized
operations. In cases when we want to describe a set of integers (vs a set
of intervals), we use ISet from Batteries. With these two structures we can
describe an interesting range of genome annotations.
>
>
> E.
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/**wws/info/caml-list<https://sympa-roc.inria.fr/wws/info/caml-list>
> Beginner's list: http://groups.yahoo.com/group/**ocaml_beginners<http://groups.yahoo.com/group/ocaml_beginners>
> Bug reports: http://caml.inria.fr/bin/caml-**bugs<http://caml.inria.fr/bin/caml-bugs>
>
>
[-- Attachment #2: Type: text/html, Size: 2391 bytes --]
next prev parent reply other threads:[~2012-02-11 23:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 1:07 Francois Berenger
2012-02-10 18:29 ` Richard W.M. Jones
2012-02-11 17:38 ` Goswin von Brederlow
2012-02-11 17:49 ` Eliot Handelman
2012-02-13 9:13 ` Sebastien Ferre
2012-02-15 1:28 ` Francois Berenger
2012-02-15 15:21 ` Goswin von Brederlow
2012-02-15 17:22 ` Edgar Friendly
2012-02-16 2:48 ` Francois Berenger
2012-02-16 2:32 ` Francois Berenger
2012-02-16 2:42 ` Francois Berenger
2012-02-16 8:34 ` Goswin von Brederlow
2012-02-16 12:20 ` John Carr
2012-02-16 10:21 ` Gabriel Scherer
2012-02-17 0:59 ` Francois Berenger
2012-02-17 8:11 ` Christophe Raffalli
2012-02-11 20:49 ` Edgar Friendly
2012-02-11 23:54 ` Philippe Veber [this message]
2012-02-11 10:54 ` Philippe Veber
2012-02-11 17:33 ` Goswin von Brederlow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOOOohQmcTye+A1LnNgfOwQmTyPO23YYoNqxaUo=yoDkKz6C+g@mail.gmail.com' \
--to=philippe.veber@gmail.com \
--cc=caml-list@inria.fr \
--cc=thelema314@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).