I tried the procedure from step-40 and these are the results: *DEAL.II:*
<https://lh3.googleusercontent.com/-ZwWP5Xfoe6U/WJdmEMU4v8I/AAAAAAAAAFs/5hR3YA0RkeoYiSGZCDbEiHWH_I_pJJYWwCLcB/s1600/dealii_result.png> *C++ CODE:* <https://lh3.googleusercontent.com/-MnonNmQiobQ/WJdlxPUSPDI/AAAAAAAAAFk/aKBykIr6vmk98aCzEuUPzpa9IGybtLswQCLcB/s1600/cpp_result.png> I already tried some *interpolate_boundary_values* approach, but I don't think it is something related to boundaries since I just have boundary conditions at the bottom and upper boundary. We still have bad results at the left and right boundary though. Any ideas what could cause such a behavior? Is it even correct to initialize a global MPI vector within the setup_system() function using the locally_owned_dofs and locally_relevant_dofs information before assembly and solution of the system and fill this vector then after the system has been solved? Finally, passing it then to the output_results() function? Kind regards, Seyed Ali -- 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 dealii+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
