dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #22053
Mesh questions
-
To:
DOLFIN Mailing List <dolfin@xxxxxxxxxxxxxxxxxxx>
-
From:
"Garth N. Wells" <gnw20@xxxxxxxxx>
-
Date:
Tue, 15 Mar 2011 19:49:51 +0000
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
The number of Mesh members functions is getting pretty large, as too is
the number of classes in the dolfin/mesh directory. This is likely to
grow as more search, parallel and refinement features are added. Is it
therefore sensible to:
- Move mesh algorithms (search, refine, generate, etc) to a separate
directory?
- Remove 'algorithmic' functions from Mesh, and make them members of
static classes or free functions (as we've done for refine)? Mesh would
then be just a data structure.
The names of some search-related Mesh member functions are a bit
complex. Can we simplify them, e.g.
void all_intersected_entities(const Point& point,
uint_set& ids_result) const;
to
void intersected_cells(const Point& point,
uint_set& ids_result) const;
and
int any_intersected_entity(const Point& point) const;
to
int intersected_cell(const Point& point) const;
(or int isupport_cell(const Point& point) const;).
Garth
Follow ups