I don't even understand how the current stuff works at all.
Since the node and element numbers change after running the mesh through an
XDA read and write - how do the dof ids match up with what was written out
with EquationSystems::write()??
Derek
On Wed, Nov 6, 2013 at 4:41 PM, Derek Gaston <fried...@gmail.com> wrote:
> For Parallel Mesh I was just thinking that each processor would write it's
> own file... so that you could perfectly recreate the exact Mesh data
> structure on read (not too mention being more amenable to parallel
> filesystems like Panasas)
>
> Derek
>
>
> On Wed, Nov 6, 2013 at 4:33 PM, Kirk, Benjamin (JSC-EG311) <
> benjamin.k...@nasa.gov> wrote:
>
>> On Nov 6, 2013, at 4:18 PM, Derek Gaston <fried...@gmail.com>
>> wrote:
>>
>> > 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…
>>
>> That should be possible… The parallel format is loosely thought out and
>> open to extension. From a serial file the global ids are inferred, for the
>> parallel case I don't see a reason we couldn't include a unique global id
>> too.
>>
>> > It should go:
>> >
>> > Meta Data
>> > Nodes
>> > Elements
>> > BCs
>>
>> The idea here is we can optionally support a partition file, which
>> defines element ownership. This could allow the elements to be shipped off
>> first in the case of a serial read, or read only on the processors that
>> need them. The important subset of nodes can then be determined.
>>
>> Reading the nodes first would require caching all of them until you know
>> which ones you can discard. Or closing the buffer and doing some seek
>> business.
>>
>> -Ben
>>
>>
>
------------------------------------------------------------------------------
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
