On Thu, 10 Jul 2008, Maxime Debon wrote: > Using a 1000 elements mesh, I made the computation with : > - HIERARCHIC Order 1 - Edge2 :: Success > - HIERARCHIC Order 2 - Edge3 :: Success > - HIERARCHIC Order 3 - Edge3 :: Success > - HIERARCHIC Order 4 - Edge3 :: Success > - BERNSTEIN Order 2 - Edge3 :: Success > - BERNSTEIN Order 3 - Edge3 :: Success > - BERNSTEIN Order 4 - Edge3 :: Success > - BERNSTEIN Order 5 - Edge3 :: Success > - BERNSTEIN Order 6 - Edge3 :: Success > - CLOUGH Order 2 - Edge3 :: Success > - HERMITE Order 3 - Edge3 :: Success > - LAGRANGE Order 1 - Edge2 :: Success > > The results are quite good with all these elements. The incredible behaviour > only happens with : > > - LAGRANGE Order 2 - Edge3 :: Problem > - LAGRANGE Order 3 - Edge4 :: Problem > > The problem seems to generate a solution whose node values are slightly > (really ) diminishing when the number of elements goes beyond 50 (80).
Very strange. And it's going to be very hard to debug if it can't be triggered on simple meshes. How much simplification can you do and still see this behavior? You're running a nonlinear transient problem at the moment, right? --- Roy ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
