Anyone see a problem with calling reinit() right after init? It seems to be decimating my initial condition if I do that (the one that is projected in init()) when used in combination with initial uniform refinement.
I'm attaching a hacked up example10 so you can see what I'm talking about. Compare the solutions written out to the exodus file (out.e) with the equations_systems.reinit() call on line 253 either commented or uncommented. With the reinit() call happening you get a "wrong" projection of the initial condition in out.e... it looks like it's a coarsened version. I was definitely not expecting this behavior (basically it seems like a call to reinit() should be safe as long as the mesh isn't changing). Why am I doing this at all? Because I need to monkey with the send_list... which means I need to call reinit() to reset the ghosted vectors. That code is working BTW.... it's only when there is some initial uniform refinement that this weird initial condition projection stuff goes wonky. Derek
ex10.C
Description: Binary data
------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev
_______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
