Mihai,
the rationale for introducing MeshWorker was simplifying integration
loops over cells and faces. Now, currently we do not have faces in 1D,
therefore it did not work. Even if Wolfgang removed part of the code in
1D, I never bothered about the implications of using MeshWorker in 1D,
since most of the reason for its existence vanishes in 1D. I could
imagine, that some typedefs and class definitions might fail in 1D. So,
I fear, for the moment, you might be better off coding the loop yourself.
Best,
Guido
mihai alexe wrote:
Hi,
I am trying to adapt step-12 (2D advection with DG) to a
time-dependent 1D advection problem. I'm having issues at link time -
the linker is unable to find references like
dealii::MeshWorker::DoFInfo<1, 1, double>::DoFInfo()
dealii::MeshWorker::IntegrationInfo<1, 1>::IntegrationInfo()
dealii::MeshWorker::IntegrationInfo<1,
1>::reinit(dealii::MeshWorker::DoFInfo<1, 1, double> const&)'
dealii::MeshWorker::IntegrationInfoBox<1,
1>::initialize_gauss_quadrature(unsigned int, unsigned int, unsigned int)'
(.. and so on)
in the deal.ii 1D (debug) library. Is the MeshWorker framework coded
for 2D/3D problems only? Or what am I doing wrong?
Thanks,
Mihai
------------------------------------------------------------------------
_______________________________________________
dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
_______________________________________________
dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
