dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #20394
Re: [Branch ~dolfin-core/dolfin/main] Rev 5354: Work on not exposing eval_data in Python interface.
On Fri, Dec 03, 2010 at 02:24:52PM +0100, Marie E. Rognes wrote:
> On 03. des. 2010 14:14, noreply@xxxxxxxxxxxxx wrote:
>
> ------------------------------------------------------------
> revno: 5354
> committer: Garth N. Wells <gnw20@xxxxxxxxx>
> branch nick: dolfin-all
> timestamp: Fri 2010-12-03 13:11:44 +0000
> message:
> Work on not exposing eval_data in Python interface.
>
> adaptivity module has been disabled for now since it does something funny with eval_data.
>
>
>
> Feel free to keep it disabled. It will be replaced by new implementation (cf
> branch dolfin/error-control)
>
> However, the "funny" thing is does with eval_data is there for a reason. So,
> what is the best way of implementing the following with the new interface?
>
> void SpecialFacetFunction::eval(Array<double>& values, const Data& data)
> const
> {
> values[0] = 0.0;
> if (data.on_facet())
> _f_e[data.facet()]->eval(values, data);
> }
>
>
> Here _f_e is a vector of Functions (each corresponding to a local facet
> number).
if (local_facet >= 0) <--> if (data.on_facet())
--
Anders
Follow ups
References