ffc team mailing list archive

[Kristian Oelgaard <k.b.oelgaard@xxxxxxxxxx>]

Quoting "Garth N. Wells" <gnw20@xxxxxxxxx>:

>
>
> Kristian Oelgaard wrote:
> > Quoting kent-and@xxxxxxxxx:
> >
> >>> Quoting "Garth N. Wells" <gnw20@xxxxxxxxx>:
> >>>
> >>>>
> >>>> FFC wrote:
> >>>>> One or more new changesets pushed to the primary ffc repository.
> >>>>> A short summary of the last three changesets is included below.
> >>>>>
> >>>>> changeset:   1612:de211a9d88bce134c4abc2b128283ad35415a529
> >>>>> tag:         tip
> >>>>> user:        "Kristian Oelgaard <k.b.oelgaard@xxxxxxxxxx>"
> >>>>> date:        Tue Aug 18 17:57:36 2009 +0100
> >>>>> files:       ffc/fem/finiteelement.py
> >>>>> description:
> >>>>> Restrictions appears to be working for the Poisson demo.
> >>>>>
> >>>> Nice. What does the UFL syntax look like?
> >>> scalar  = FiniteElement("CG", triangle, 3)
> >>> vector  = VectorElement("CG", triangle, 3)
> >>>
> >>> #element = scalar
> >>> #element = scalar["interval"]
> >>> #element = scalar[interval] + scalar
> >>> element = vector[interval]
> >> What does this mean ?
> >
> > It's related to this thread
> >
> > http://www.fenics.org/pipermail/ffc-dev/2009-July/002726.html
> >
> > the 'scalar' element will have 10 dofs, 3 at the vertices 6 on the edges
> and 1
> > inside the cell.
> >
> > element = scalar[interval]
> >
>
> Do we have point, edge, face and facet as well?

No, only interval, triangle, tetrahedron, quadrilateral and hexahedron

is predefined in UFL. I assume simplices and restrictions currently only
supports a restriction to one topological dimension lower i.e.,
tetrahedron -> triangle
triangle -> interval

Kristian


> Garth
>
> > will not have the dof which is inside the cell, it is restricted to the
> facets
> > (which is interval in this case).
> >
> > Kristian
> >
> >> Kent
> >>
> >>> v = TestFunction(element)
> >>> u = TrialFunction(element)
> >>>
> >>> a = inner(grad(v), grad(u))*dx
> >>>
> >>> They should all work.
> >>>
> >>> evaluate_basis and evaluate_basis_derivatives is not implemented for
> >>> restricted
> >>> elements. The reason is that I'm not sure about what should happen when I
> >>> throw
> >>> away basisfunctions.
> >>>
> >>> Kristian
> >>>
> >>>> Garth
> >>>>
> >>>>> changeset:   1611:283c1799fe643b297668dfa5347a7de50fee8555
> >>>>> user:        "Kristian Oelgaard <k.b.oelgaard@xxxxxxxxxx>"
> >>>>> date:        Tue Aug 18 17:40:05 2009 +0100
> >>>>> files:       ffc/fem/finiteelement.py ffc/fem/quadratureelement.py
> >>>>> description:
> >>>>> Bug fix to make buildbot happy.
> >>>>>
> >>>>>
> >>>>> changeset:   1610:2d95d63e8281e4f06cb9a24f1895b6e70563d1c5
> >>>>> user:        "Kristian Oelgaard <k.b.oelgaard@xxxxxxxxxx>"
> >>>>> date:        Tue Aug 18 17:09:17 2009 +0100
> >>>>> files:       ffc/compiler/evaluatebasis.py
> >>>> ffc/compiler/finiteelement.py
> >>>> ffc/fem/createelement.py ffc/fem/finiteelement.py
> >>>>> description:
> >>>>> A first implementation of restrictions work for FiniteElements.
> >>>>>
> >>>>> ----------------------------------------------------------------------
> >>>>> For more details, visit http://www.fenics.org/hg/ffc
> >>>>> _______________________________________________
> >>>>> FFC-dev mailing list
> >>>>> FFC-dev@xxxxxxxxxx
> >>>>> http://www.fenics.org/mailman/listinfo/ffc-dev
> >>>> _______________________________________________
> >>>> FFC-dev mailing list
> >>>> FFC-dev@xxxxxxxxxx
> >>>> http://www.fenics.org/mailman/listinfo/ffc-dev
> >>>>
> >>>
> >>> _______________________________________________
> >>> FFC-dev mailing list
> >>> FFC-dev@xxxxxxxxxx
> >>> http://www.fenics.org/mailman/listinfo/ffc-dev
> >>>
> >>
> >
> >
>