> When compiling on a cluster that offers pathscale compilers (which use
> a GCC 3.3.3 front end) I run into an error:
> In file included from source/fe/fe_system.cc:21:
> /CHPC/home/mrapson/lib/gcc/deal.II-6.2.1/deal.II/include/fe/fe_system.h:
>85: error: syntax error before `{' token
> /CHPC/home/mrapson/lib/gcc/deal.II-6.2.1/deal.II/include/fe/fe_system.h:
>692: error: use of enum `enum dealii::CellSimilarity::Similarity' without
> previous declaration
This is weird: fe_system.h includes fe.h which includes fe_base.h which
includes fe_update_flags.h which has the necessary declaration. But I
think that's just a follow-up error, the problem is the first error that
says that there is a syntax error in the statement
template <int dim, int spacedim=dim>
class FESystem : public FiniteElement<dim,spacedim>
-> {
Can you try to find out why that is the case?
> On another system which uses gcc 4.1.2 and mpich2 the above problem
> does not occur, however the Epetra_MpiComm.h header file is needed for
> liblac.so and it does not seem to be copied to the trilinos install
> path by default.
But only if you configure deal.II with MPI and Trilinos without. You need
to be consistent.
> Final comment on compiling the library, when using mpich2 I need to
> set my CXXFLAGS=-DMPICH_IGNORE_CXX_SEEK to avoid a bug in the MPI 2
> standard (SEEK_SET, SEEK_END and SEEK_CUR defined in two places).
You mean you have to set these flags with deal.II? What does this do, and
why is it necessary?
> do something similar. Basically the idea is to provide a time plot of
> specific points in the mesh. The constructor takes the dof_handler and
> FiniteElement as parameters. The user specifies a number of Point
> <dim> in mesh that they want to plot and the class finds the closest
> actual mesh nodes to the requested Point and works out its global dof
> index. For each time step the user passes the class as many solution
> and post processed VECTORS as they want to store and the class saves
> data from the VECTORS at the desired grid locations. Once the
> simulation is complete the user can export the plots to gnuplot
> (currently).
A better solution may be to not just use the closest mesh node but evaluate
the solution at this point (e.g. using VectorTools::point_value of
FEFieldFunction). But in general, yes, such a class may quite well be of
interest to others as well. We'd be happy if you'd finish up your code,
wrote a little bit of documentation, and submitted it!
Best
Wolfgang
-------------------------------------------------------------------------
Wolfgang Bangerth email: [email protected]
www: http://www.math.tamu.edu/~bangerth/
_______________________________________________
dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
