> These are then used as input for constructing the fe_values and pulling out
> the local velocity values. It is precisely when using the
> fe_values.get_function_values(velocity_model->get_velocity(),
> local_velocity_values)
>
> that the error
>
> fe_values.get_function_values() on the velocity
On Sunday, February 12, 2017 at 8:49:34 AM UTC-6, Timo Heister wrote:
>
> >>
> >> > fe_values.get_function_values() on the velocity vector.
> >> > ExcIndexNotPresent (n)
> >>
> >> get_function_values() needs to see the ghost values of your vector
> >> (all DoFs on a cell).
> >
> >
> >
>>
>> > fe_values.get_function_values() on the velocity vector.
>> > ExcIndexNotPresent (n)
>>
>> get_function_values() needs to see the ghost values of your vector
>> (all DoFs on a cell).
>
>
> yes, that is what is being passed to it. I use the post flags _lo and _lr
> for my vector names t
On Friday, February 10, 2017 at 12:15:10 PM UTC-6, Timo Heister wrote:
>
> I wanted to give you some info on your original question in case your
> want to still use PETSc.
>
> > It appears that for petsc, the assumption that the locally owned dofs
> Index
> > Sets are contiguous is really thr
I wanted to give you some info on your original question in case your
want to still use PETSc.
> It appears that for petsc, the assumption that the locally owned dofs Index
> Sets are contiguous is really throwing a wrench in our plans for the non
> block system approach. I have seen the other di
A problem I am working on results in a non symmetric 4x4 block matrix
system with the first block representing a vector valued velocity and the
remaining 3 blocks scalar quantities that are all coupled.
The fe system is represented as
FESystem (FESystem(FE_Q
(parameters.degree_of_fe_veloci
