dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #09496
Re: XML format for Higher Order meshes
You can't since you don't have write permission (takes a little while
to get) but just post the hg bundle here.
--
Anders
On Thu, Sep 04, 2008 at 11:23:56AM -0400, Shawn Walker wrote:
> Actually, I did not PUSH this changeset. I was afraid to do this.
> Should I just do that?
>
> - Shawn
>
> On Thu, 4 Sep 2008, Anders Logg wrote:
>
>> On Wed, Sep 03, 2008 at 11:01:12AM -0400, Shawn Walker wrote:
>>> I created a bundle:
>>>
>>> dolfin-walker-2008-09-03.hg
>>>
>>> whose description is:
>>>
>>> "This patch adds in support for reading in an additional 'coordinates'
>>> tag in the mesh.xml file, and uses this information to create a Function*
>>> called mesh_coordinates that is contained in the MeshGeometry class.
>>> This function stores higher order mesh coordinate data that comes from
>>> assuming the mesh elements are mapped using a finite element function
>>> higher order than linear. Another boolean array is created inside
>>> MeshGeometry that indicates which elements are ACTUALLY curved, and which
>>> are just straight (standard). This is completely backwards compatible
>>> with previous mesh formats."
>>>
>>> I followed the directions in the DOLFIN manual to update. I'm not sure
>>> if there is anything else I need to do for this update.
>>>
>>> Anyway, the next step in this higher order mesh format, is to modify
>>> UFCCell.h and ufc::cell.
>>>
>>> - Shawn
>>
>> Sounds good, but where is it?
>>
>>
Attachment:
signature.asc
Description: Digital signature
Follow ups
References