Physically, the problem is scalar per direction (radiation transport).
So you are suggesting I don't need to use FE_Nothing in the FESystem?
I don't think it's become completely clear what you are doing, but from
what I infer is that your problem is *not* in fact scalar -- but a
system of
在 2017年6月14日星期三 UTC-7下午5:44:37，Wolfgang Bangerth写道：
>
> On 06/13/2017 06:16 PM, Weixiong Zheng wrote:
> > |
> >
> > |
> >
> > As the problem is a scalar problem, fv.shape_value and shape_grad work
> as they
> > are supposed to, but not the get_function_values.
>
> It is a coincidence
On 06/13/2017 06:16 PM, Weixiong Zheng wrote:
|
|
As the problem is a scalar problem, fv.shape_value and shape_grad work as they
are supposed to, but not the get_function_values.
It is a coincidence that the former two work -- they return the one non-zero
component of a vector valued
Thanks, Daniel,
I used FESystem to wrap the scalar FiniteElement and the FE_Nothing
together. Here are the hp-relevant variables:
FESystem fe_continuous;
FESystem fe_discontinuous;
hp::FECollection fe_c;
hp::QCollection q_c;
hp::QCollection q_face_c;
This is how I do initialization
Weixiong,
[...]
>
Then I got confused:
> 1. I used hp class a year ago or so, fv.get_function_values works
> directly. Now I have to use the above change. Did I do something wrong?
> 2. Then why fv.shape_value still works as it did? Isn't fv still a
> FESystem object?
>
How did you initialize
All right, my understanding is that fv now is a FESystem object and have to
be used correspondingly. So I tried and it worked.
hp::FEValue hp_fv(fe_c,q_c,update_values | update_quadrature_points);
for(cells)
{
const FEValues = hp_fv.get_present_fe_values();
FEValuesExtractors::Scalar
