On Sat, 03 Mar 2012 00:12:21 -0500, Soon Hoe Lim <[email protected]> wrote: > Thank you so much. I will do that. > > I have another question. If I want to refine/coarsen my grid every few time > step based on certain error estimator/refinement indicator, does deal.II > provide any robust refinement indicator for that purpose? Or is it best to > develop our own indicators, tailored specifically to our problem? If it is > best to create our own indicators, then what do we look for in order to get > a reasonably good grid and results? > > I tried to use KellyErrorEstimator to refine the grid every time step to > see how it works but I get compiler errors like: > > An error occurred in ... > Number& dealii::Vector<number>::operator()(unsigned int) [with Number = > double] > > The violated condition was: > i<vec_size > The name and call sequence of the exception was: > ExcIndexRange(i,0,vec_size) > Additional Information: > Index 4225 is not in [0,4225[ > > Stacktrace: > ----------- > #0 ./step-3: dealii::Vector<double>::operator()(unsigned int) > #1 ./step-3: Model::compute_term_old() > #2 ./step-3: Model::assemble_term() > #3 ./step-3: Model::run() > #4 ./step-3: main > > Do you have any ideas? > > Soon Hoe > > On Fri, 2 Mar 2012 23:00:58 -0600, Timo Heister <[email protected]> > wrote: >>> I did not use hanging node constraint for this problem. >> >> You need to apply hanging node constraints if you want to refine your >> mesh adaptively. >> >>> I did use SolutionTransfer class to transfer the old mesh to the new > one. >> >> Write that function to file and check that it looks correct on the new >> mesh to be sure.
-- Regards, Soon Hoe Lim Mathematics and Physics University of Michigan, Ann Arbor [email protected] _______________________________________________ dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
