I have found my problem. A boundary condition in my mesh was ill-defined
and this lead to my error.
Sorry for the confusion.
Thanks
On Monday, 19 February 2018 13:41:35 UTC-5, Bruno Blais wrote:
>
> Hello,
> Sorry I feel I have not explained myself correctly. Here is a drawing of
> the case:
>
Hi Wolfgang, thanks so much for getting back to me
1. I was wondering re dimensions because I could find a component mask
function or something similar to fe_values[velocities], eg, when using
fe_face_values which you need to apply the neumann conditions.
2. This is my fault. I meant working
Stephen,
I looked at the source code and it looks to me like the documentation
is correct: component_map is just to remap components and can not be
used to do what you want. It is just passed to
create_boundary_mass_matrix().
On Wed, Feb 21, 2018 at 7:03 PM, Stephen Shannon
Hi IIiya,
On Thursday, February 22, 2018 at 11:55:33 AM UTC+1, Bryukhanov Ilya wrote:
>
> Denis, thanks a lot for the answer!
>
> I think that on the first step I can use usual
> "interpolate_boundary_values + apply_boundary_values" functions,
>
the outline I gave above is agnostic to "first
Denis, thanks a lot for the answer!
I think that on the first step I can use usual "interpolate_boundary_values
+ apply_boundary_values" functions,
that transform the global matrix: columns of the constrained nodes become
zero columns with diagonal non-zero entries.
In a time loop I have to
Denis, thanks a lot for the answer!
I think that on the first step I can use usual "interpolate_boundary_values
+ apply_boundary_values" functions,
that transform the global matrix: columns of the constrained nodes become
zero columns with diagonal non-zero entries.
In a time loop I have to
Denis, thanks a lot for the answer! I think that on the first step I can
use usual "interpolate_boundary_values + apply_boundary_values" functions,
and this procedures transform the global matrix so that the columns of
constrained nodes become zero columns with diagonal non-zero entries.
In a
