Thanks for the answer. > I can't right away see what the issue may be, but to help debug this: > * Change your code in such a way that just before serialization, you set > all entries of the solution vector to one. This way, you know exactly > what you have. What you get back should match this exactly.
I actually was already doing that. I also tried set the entries of the of the vector to a fixed values before the loading and the deserialization to see if the entries for the node at the process boundary are actually written; and they are set to zero anyway. > * Check the following: Is sol_u a vector that has ghost elements before > serialization? Is sol_u a vector that has ghost elements after > serialization? Because if these vectors don't have ghost elements, then > what you see visually may not be what you actually have. > > The vectors used for the serialization and deserialization are of the same type and the output of the vector should be correct because is the same routine that I usually use to visualize the the solution. > As always, you should run your program in debug mode to make sure as > many bugs are found automatically as possible. > > Best > W. > > Best D. > -- > ------------------------------------------------------------------------ > Wolfgang Bangerth email: [email protected] > <javascript:> > www: http://www.math.colostate.edu/~bangerth/ > -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
