Re: [deal.II] project_boundary_values for components

On 4/9/19 2:23 AM, Anton wrote: > > Thank you for the help.  I think I have it working in the non-distributed > case, but project_boundary_values segfaults on me without any explanations > (compiled in debug mode) when run with a distributed triangulation.  Is this > "normal"? Ah, good point.

Re: [deal.II] project_boundary_values for components

Wolfgang, Thank you for the help. I think I have it working in the non-distributed case, but project_boundary_values segfaults on me without any explanations (compiled in debug mode) when run with a distributed triangulation. Is this "normal"? /Anton On Monday, April 8, 2019 at 12:11:19 A

Re: [deal.II] project_boundary_values for components

On 4/6/19 12:29 PM, Anton wrote: > > Basically if I interpolate a step function (which can be exactly presented in > for example DGQ1 space if the discontinuity is at the node) I get a 1-element > wide transition.  In ASCII pictures, I expect  ___  but I get ___/--- > instead :) Ah, yes -

Re: [deal.II] project_boundary_values for components

Thank you Wolfgang. Basically if I interpolate a step function (which can be exactly presented in for example DGQ1 space if the discontinuity is at the node) I get a 1-element wide transition. In ASCII pictures, I expect ___ but I get ___/--- instead :) So if I understand you correctly

Re: [deal.II] project_boundary_values for components

On 4/5/19 11:25 AM, Anton wrote: > I need to apply a boundary condition (discontinuous function) to a few > components of a dof_handler only.  I am currently using > > | > voidVectorTools::interpolate_boundary_values >

[deal.II] project_boundary_values for components

Hello, I need to apply a boundary condition (discontinuous function) to a few components of a dof_handler only. I am currently using void VectorTools::interpolate_boundary_values (const Do