level_set(4rheolef) [debian man page]

level_set(4rheolef)						    rheolef-6.1 					       level_set(4rheolef)

NAME

       level_set - compute a level set from a function

SYNOPSYS

       geo level_set (const field& fh);

DESCRIPTION

       Given  a  function fh defined in a domain Lambda, compute the level set defined by {x in Lambda, fh(x) = 0}.  This level set is represented
       by the geo class.

OPTIONS

       The option class leve_set_option_type controls the slit of quadrilaterals into triangles for tridimensional intersected	surface  and  also
       the zero machine precision, epsilon.

IMPLEMENTATION

       struct level_set_option_type {
	   bool split_to_triangle;
	   Float epsilon;
	   level_set_option_type()
	    : split_to_triangle(true),
	      epsilon(100*std::numeric_limits<Float>::epsilon())
	      {}
       };
       template <class T, class M>
       geo_basic<T,M> level_set (
	 const field_basic<T,M>& fh,
	 const level_set_option_type& opt = level_set_option_type());

rheolef-6.1							    rheolef-6.1 					       level_set(4rheolef)

geo_domain_indirect(7rheolef)					    rheolef-6.1 				     geo_domain_indirect(7rheolef)

NAME

       geo_domain_indirect_rep - a named part of a finite element mesh

DESCRIPTION

       The  geo_domain_indirect_rep  class  defines  a container for a part of a finite element mesh.  This describes the connectivity of edges or
       faces.  This class is usefull for boundary condition setting.

IMPLEMENTATION NOTE

       The geo_domain_indirect_rep class is splitted into two parts.  The first one is the domain_indirect class, that contains the main renumber-
       ing features: it acts as an indirection on a geo class(see geo(2)).  The second one is the geo class itself, named here the background geo.
       Thus, the geo_domain_indirect class develops a complete geo-like interface, via the geo_abstract_rep pure virtual class derivation, and can
       be used by the space class (see space(2)).

       The  split between domain_indirect and geo_domain_indirect is necessary, because the geo class contains a list of domain_indirect.  The geo
       class cannot contains a list of geo_domain_indirect classes, that refers to the geo class itself: a loop in reference counting leads  to  a
       blocking situation in the automatic deallocation.

SEE ALSO

       geo(2), space(2)

rheolef-6.1							    rheolef-6.1 				     geo_domain_indirect(7rheolef)