From: Andrea Hawkins <andjhawkins@gm...>  20100112 16:36:47

Hello I'm wondering if someone could give me a quick tutorial on how the storage works for current_local_solution... I understand that current_local_solution is supposed to carry only the information necessary for the computations on a specific processor. And in the documentation, there is a comment in regards to the current_local_solution "All the values I need to compute my contribution to the simulation at hand. Think of this as the current solution with any ghost values needed from other processors. This vector is necessarily larger than the solution vector in the case of a parallel simulation" But... in the update function there is a line libmesh_assert (current_local_solution <http://libmesh.sourceforge.net/doxygen/classSystem.php#47b00cd00684aebe3c095aba010626e5>>size() == solution <http://libmesh.sourceforge.net/doxygen/classSystem.php#d679ef41b83fdefc3fe649e99672a941>>size()); which implies that they are the same size... =) So, I thought perhaps this is just the global size, maybe it is the local size that should be different. But, I checked that (at least on a 2 processor run) and they had the same local size as well. So, what exactly is the current_local_solution? It appears to have the same parallel structure of solution. Does it just fill in zeros wherever there is an unneeded value? Thanks! Andrea 