Hi, With regard to the approach which was recently discussed in: https://groups.google.com/d/msg/dealii/25C57MYvfpg/JFB8aXKoAgAJ
There is a little problem when computing the material forces in a parallel setting. <https://lh3.googleusercontent.com/-MDeWgMu6a7w/WJMlqFOthhI/AAAAAAAAAFA/yLnZUQ0tM4wBTX7pxatbZXyT4KqwyDl4QCLcB/s1600/cf1.png> <https://lh3.googleusercontent.com/-J9v-E1vDMWs/WJMlrjKzbEI/AAAAAAAAAFE/wtS4-9KIALsX5tegQRMA1wTaffe0oXBowCLcB/s1600/cf2.png> I assume it has something to do with the synchronization. The computation of material forces is done similar to the system_rhs vector. Vector<double> cell_cf(dofs_per_cell); // Cell Configurational forces typename DoFHandler<dim>::active_cell_iterator cell = dof_handler.begin_active(), endc = dof_handler.end(); for (; cell != endc; ++cell) { if ( cell->is_locally_owned() ) { fe_values.reinit(cell); cell_cf = 0; ... // Configurational force computation ... ... cell->get_dof_indices(local_dof_indices); constraints.distribute_local_to_global(cell_cf, local_dof_indices, configurational_forces); } } configurational_forces.compress(VectorOperation::add); For a single core computation it is validated and correct. What could be possibly wrong when going to parallel? Best regards, Seyed Ali Mohseni -- 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.
