dolfin team mailing list archive

[Andre Massing <massing@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I have implemented
https://blueprints.launchpad.net/dolfin/+spec/bbtree-all-codim

including some unittests, but there remain some questions.

1. The name IntersectionOperator is kind of unfortunate and cryptic.
In the end it is just a wrapper for a bounding box tree so I was
thinking about renaming it to something more descriptive, e.g.
BoundingVolumeTree or BVTree...Any suggestions, wishes, feelings about
that? That brings me to another point.

2. Since a bbtree is available for all
entity dimension it might be nice to have specialized, ready to use name
for them (especially with the python interface in mind and similar to
what we have for MeshEntity already)?
For instance CellBVTree, FacetBVTree are names popping up in my mind.
Are they any suggestions or preferences regarding this?

3. Johan suggested at some point to expose the distance functions
available in CGAL AABBTree

http://www.cgal.org/Manual/latest/doc_html/cgal_manual/AABB_tree_ref/Class_AABB_tree.html#Cross_link_anchor_1724

which I think is a good idea.  Any objections for adding that to
DOLFIN? As far as I know of intersection related operations haven't
been mentioned in the book,
so an interface renaming plus some small  localized interface changes
won't effect code examples in the book.

Cheers,
Andre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOut2dAAoJEA79ggnbq9dmpHgIAMXlI7QVEdfs3jKTzOG096sg
8cN4SWZbYin+KZYBrlwPh6e3X4V2+nS+/WTgljfbA0uoM/Ut4i+GK7feZQMKn9B+
kIJPYn7dOQBOqalIBoTilLIkwrQ5Kx7kYK3tKS1cGlRoU9gTGCcsElAx06sau5yA
JwVY+CTJYQMHXXirWjHiumhvdTuisEzWnDG14+3dfnMY59aDD3aQ8M0WvaNdZptj
/vcpIcZ751Cq9EIPuuOrcjbeR+K/nieZDLqL48DDajIhOxUnavkpRBtmLFYAjqL8
Nc5YF474SkfRtFhlNH8PknAI/1rV5vrI291xv24Z/D9nwBkahSISoYeoaVjqOos=
=EUCI
-----END PGP SIGNATURE-----