Roy Stogner writes:
> Just run ./configure without "--enable-parmesh", and declare objects
> to be of type Mesh, which will end up as a typedef of SerialMesh.
> You'll still need to keep your own code (e.g. node redistibution)
> consistent between processors, but you won't have to worry about b
On Sun, 18 May 2008, [EMAIL PROTECTED] wrote:
> Should I declare all meshes as SerialMesh?
Just run ./configure without "--enable-parmesh", and declare objects
to be of type Mesh, which will end up as a typedef of SerialMesh.
You'll still need to keep your own code (e.g. node redistibution)
cons
Roy
Thanks for your answer.
Roy Stogner writes:
> Don't feel bad - I run into segmentation faults *before* shifting mesh
> nodes. :-P ParallelMesh still has unfixed bugs that are triggered by
> element coarsening, it's not well tested enough in general, and I
> don't know when anyone's goin
On Sat, 17 May 2008, [EMAIL PROTECTED] wrote:
> Here are some questions concerning the parallel mesh. I ran into segmentation
> faults after I shifted mesh nodes.
Don't feel bad - I run into segmentation faults *before* shifting mesh
nodes. :-P ParallelMesh still has unfixed bugs that are trig
Hi
Here are some questions concerning the parallel mesh. I ran into segmentation
faults after I shifted mesh nodes. The only reason I could find was a
assertion failure on line 644 in mesh_communication_global_indices.C.
Unfortunately I was not able to debug that problem any further.
If I underst
