[deal.II] Using LinearAlgebraTrilinos::MPI::Vector.l2_norm leads to an MPI_error for multiple nodes

I tried to implement the example from step 15, but using MPI, so that I can get a better grasp on how to write such programs. My residual calculation looks quite similar to the original: const QGauss quadrature_formula(fe.degree+1); FEValues fe_values (fe, quadrature_formula,

Re: [deal.II] Output nodal scalar

Hi Jean-Paul Thanks for explaining it. Now I got both StrainPostprocessor and StressPostprocessor working! But it seems a little wasteful to have two separate classes because we are not reusing the gradient of displacement computed in StrainPostprocessor. Although it is tolerable, but it'll be

Re: [deal.II] Regarding distributed meshes with p4est and trilinios

> Thanks for great tipp. That was rather easy. > But should I use the locally_relevant_index_set as the second argument or > locally_relevant_dofs.subtract_set(locally_owned_dofs)? > Both versions work for me so far. Great! That doesn't matter (we actually subtract that set to get the ghost

Re: [deal.II] Regarding distributed meshes with p4est and trilinios

Korinna, > 1) Maybe I found a wrong assertion in the FETools. > I have trouble with FETools while working in the debug mode. I cannot > use the provided FETools::interpolation for the higher order reconstruction, It might be that we haven't been testing this function enough, so a bug like

[deal.II] combine error estimates from two different solutions

Dear All, I am solving a system of Maxwell's equations for geophysical application. For my application I need to compute two solutions for two different polarizations of the source field. In other words, I am solving the system twice with different right-hand-sides. And for each polarization, I

Re: [deal.II] Output nodal scalar

Dear Jie, Your query relates to this FAQ post . You’ll likely find that DataOut is holding a pointer to the DataPostprocessorTensor, and the

Re: [deal.II] Speeding up characteristic interpolation

Hi Praveen, - At this point, the performance depends on the transform_real_to_unit_cell (which might be slow due to Newton iterations) and the polynomial evaluation of fe.shape_value and to some extent the virtual function call of the latter. It depends on your polynomial space whether this

Re: [deal.II] Wrong solution at the boundary in restarting the solution

Thanks. Best D. On Wednesday, September 6, 2017 at 3:33:34 PM UTC+2, Wolfgang Bangerth wrote: > > > > * 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