Todo List

Member DataOut::build_patches (const Mapping< DH::dimension, DH::space_dimension > &mapping, const unsigned int n_subdivisions=0, const unsigned int n_threads=multithread_info.n_default_threads, const CurvedCellRegion curved_region=curved_boundary)
The mapping argument should be replaced by a hp::MappingCollection in case of a hp::DoFHandler.

Class FE_ABF< dim >

Even if this element is implemented for two and three space dimensions, the definition of the node values relies on consistently oriented faces in 3D. Therefore, care should be taken on complicated meshes.

Class FE_RaviartThomas< dim >

Even if this element is implemented for two and three space dimensions, the definition of the node values relies on consistently oriented faces in 3D. Therefore, care should be taken on complicated meshes.

Class FE_RaviartThomasNodal< dim >

The current implementation is for Cartesian meshes only. You must use MappingCartesian.

Even if this element is implemented for two and three space dimensions, the definition of the node values relies on consistently oriented faces in 3D. Therefore, care should be taken on complicated meshes.

Class FESubfaceValues< dim, spacedim >::ExcFaceHasNoSubfaces

Document this

Class FESubfaceValues< dim, spacedim >::ExcReinitCalledWithBoundaryFace

Document this

Member FETools::compute_block_renumbering (const FiniteElement< dim, spacedim > &fe, std::vector< unsigned int > &renumbering, std::vector< unsigned int > &start_indices)
Which way does this vector map the numbers?

Class FEValuesBase< dim, spacedim >::ExcCannotInitializeField

Document this

Class FEValuesBase< dim, spacedim >::ExcFEDontMatch

Document this

Class FEValuesBase< dim, spacedim >::ExcFENotPrimitive

Document this

Class FEValuesBase< dim, spacedim >::ExcInvalidUpdateFlag

Document this

Class FEValuesBase< dim, spacedim >::ExcShapeFunctionNotPrimitive

Document this

Class Functions::FEFieldFunction< dim, DH, VECTOR >
Add hp functionality

Member MatrixCreator::create_boundary_mass_matrix (const Mapping< dim, spacedim > &mapping, const DoFHandler< dim, spacedim > &dof, const Quadrature< dim-1 > &q, SparseMatrix< double > &matrix, const typename FunctionMap< spacedim >::type &boundary_functions, Vector< double > &rhs_vector, std::vector< unsigned int > &dof_to_boundary_mapping, const Function< spacedim > *const weight=0, std::vector< unsigned int > component_mapping=stdvector< unsigned int >())
This function does not work for finite elements with cell-dependent shape functions.

Class MGTransferBase< VECTOR >

update the following documentation, since it does not reflect the latest changes in structure.

Class PathSearch

Add support for environment variables like in kpathsea.

Member Threads::this_thread_id ()
As of now, none of our systems seems to support gettid, so that part of the code is untested yet.

Member VectorTools::interpolate (const Mapping< DH::dimension, DH::space_dimension > &mapping, const DH &dof, const Function< DH::space_dimension > &function, VECTOR &vec)
The mapping argument should be replaced by a hp::MappingCollection in case of a hp::DoFHandler.

deal.II documentation generated on Mon Nov 23 22:57:24 2009 by doxygen 1.6.1