From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Fwd: interval trees
Date: Thu, 16 Feb 2012 11:32:20 +0900 [thread overview]
Message-ID: <4F3C6AB4.6090100@riken.jp> (raw)
In-Reply-To: <87mx8kruk1.fsf@frosties.localnet>
On 02/16/2012 12:21 AM, Goswin von Brederlow wrote:
> Francois Berenger<berenger@riken.jp> writes:
>
>> Hello,
>>
>> I did a naive implementation of interval trees for float intervals.
>>
>> It is available here:
>> https://github.com/HappyCrow/interval-tree
>>
>> I wonder if it is possible to construct the trees in a tail recursive
>> fashion. Maybe I knew how to do this when I was still at university.
>>
>> Regards,
>> Francois.
>
> | Node of
> (* x_mid left_list right_list left_tree right_tree *)
> float * interval list * interval list * interval_tree * interval_tree
>
> Why interval list? You only need a single interval in leafes and none in
> other nodes (although it can help to store min and max in each node).
Not in my case, there is a payload associated with each interval in my
application so I need to keep track of the individual intervals.
> You are also missing insert and remove operations,
I don't miss anything: I don't need these operations in my application.
> which is the actually
> hard part in this. Inserting an interval might require merging the
> rightmost interval left of the root and the leftmost interval right of
> the root. So you would have 2 removals and one insertion of a combined
> interval, which complicates balancing the whole thing efficiently.
I hope you have a good book on this.
By the way, the one I refer to in my code is quite nice.
At first I thought it was too theoretical for me, but in fact
they give algorithms in recursive form so the book can become pretty handy.
> That is the part I'm struggling with.
You might be intersted into having a look at
the Computational Geometry Algorithms Library: http://www.cgal.org/
It's open source and it's also an INRIA product,
which makes two good points. ;)
You might want to bind your code to this library (they introduced
some framework recently, SWIG if I remember well, so that it should be
easy to do wrappers for any language).
It's heavily templated C++ code, good luck if you read their code.
They have a lot of crazily useful data structures (interval skip lists,
k-d trees, segment trees, range trees, AABB trees), and their
code is impossible to crash when using some specific math kernels.
Regards,
F.
next prev parent reply other threads:[~2012-02-16 2:32 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 [this message]
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
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=4F3C6AB4.6090100@riken.jp \
--to=berenger@riken.jp \
--cc=caml-list@inria.fr \
/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