On Fri, Mar 26, 2010 at 12:00 PM, Cochran, William K. <[email protected]> wrote: > > The assert at mesh/mesh_communication.C:1672 > > libmesh_assert (el_id[e] < mesh.n_elem()); > > has a chance of failing in parallel, given the algorithm: > > if proc == 0 > read mesh > broadcast data > prepare_for_use. > > The element ids of the mesh may not be contiguous when the inequality is > asserted. In my example, the mesh has 1326 elements. In serial, a > particular element e has el_id[e] = 540. On 2 processes, it is el_id[e] = > 1532.
Thanks for the info, we'll have to look into it. Just to clarify, are you using the Nemesis reader to read split up Exodus files or are you just reading an Exodus file in parallel. It seems that the element IDs should be the same for the exodus reader no matter how many processors there are, but I may be misremembering something. -- John ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
