#723 method order on basis
Metadata
| Property | Value |
|---|---|
| Reported by | Andreas Dedner (A.S.Dedner@warwick.ac.uk) |
| Reported at | Jan 24, 2010 19:41 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Jul 9, 2012 20:27 |
Description
What is the exact semantics of order()?
We would suggest to have two methods:
k=interpolationOrder(): P_k subset span<b_i>
K=maxOrder(): span<b_i> subset P_K
Example: RT_0 would have k=0, K=1
Q_p would have k=p, K=2p
P_p would have k=K=pNote that the maxOrder is only meaningful for polynomial
basis functions (e.g. a sin/cos basis would have to have
k=0, K=infinity).
A third value which might be even more practical, is a bit difficult to define and has something to do with the required quadrature order. Assuming e.g. that a tensor product quadrature is used on cubes then the quadrature order for Q_p would be p=interpolationOrder(); but for RT_0 on simplex elements we need order 1=maxOrder(). Of course maxOrder always works but in the case of Q_p it is much to large.
At the moment the order seems not consistently implemented:
Q1LocalBasis::order returns 1 (interpolation order)
RT0LocalBasis::order returns 1 (max order)Our basis function return the ''quadrature order''.