Let me be a bit more clear:
After writing an XDA file and reading it back in - I want _exactly_ the
same Mesh structure that I had to start with.... same numbering, same
everything...
Derek
On Wed, Nov 6, 2013 at 4:16 PM, Derek Gaston <fried...@gmail.com> wrote:
> As a follow on to this I think the XDA format is not currently done
> properly.
>
> It should go:
>
> Meta Data
> Nodes
> Elements
> BCs
>
> Where the "Nodes" section has
> node_id node_unique_id coord_x coord_y coord_z
>
> That way you don't have to create "surrogate" nodes during read - you just
> create the correct ones (with the correct ids) and then use them when
> creating the elements.
>
> But, as usual - I'm sure there's something I'm not thinking of....
>
> Derek
>
>
>
> On Wed, Nov 6, 2013 at 4:02 PM, Derek Gaston <fried...@gmail.com> wrote:
>
>> When you write and read an XDA file in parallel the node and element
>> numbering is changed.
>>
>> This means that nodesets can't work through a "restart" in parallel...
>> and even worse if you are trying to "append" to the Exodus file it doesn't
>> work (because that Exodus file already has a different numbering so the
>> solution looks "scrambled").
>>
>> Further, if you have "holes" in your numbering (ie your nodes start at
>> 500 and go to 1000) those numbers aren't preserved at all.
>>
>> We must write out the element and node numbers and preserve them through
>> a write to XDA and a read from XDA.
>>
>> Agree, disagree?
>>
>> Derek
>>
>
>
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
