Thanks Ben, That worked great! The partitions are much more stable using
parmetis. I didn't even know if that was an option with serial mesh, so I
learned something new.
Cody
On Tue, Jul 9, 2013 at 1:09 PM, Kirk, Benjamin (JSC-EG311) <
[email protected]> wrote:
> On Jul 9, 2013, at 12:40
FYI,
I just got an interesting error when I went to push:
$ git push
Counting objects: 9, done.
Delta compression using up to 24 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 611 bytes, done.
Total 5 (delta 4), reused 0 (delta 0)
remote: Unexpected system error afte
On Jul 9, 2013, at 12:40 PM, Cody Permann wrote:
> While I'm on the subject of partitioners, does anyone know of a way to make
> the Metis partitioner less sporadic in moving the partitions around? With
> each time step of this PF simulation, the set of elements owned by a specific
> process
I'm running a phase-field simulation with adaptivity and decided to use the
centroid partitioner instead of the default partitioner (Metis for serial
mesh?) for reasons I'll explain in a moment. Unfortunately, I'm triggering
a segfault, but so far it's been rather difficult to hit. I've run the
s
On Tue, Jul 9, 2013 at 11:53 AM, Roy Stogner wrote:
>
> That's a little tricky, since you'd basically have to clone the whole
> PeriodicBoundaries structure... but I'm still inclined to say you're
> right. Would you guys mind putting together the patch?
>
Unfortunately - we don't have the time r
On Tue, 9 Jul 2013, Derek Gaston wrote:
it turns out that you can still call non-const methods on member
variables of the class from a const method if those member variables
are pointers or references
(see:
http://stackoverflow.com/questions/7390437/c-const-member-functions-are-modifying-membe
Ok - I tracked it down. The issue is that we have a derived class from
PeriodicBoundaryBase that overrides get_corresponding_pos()... and even
though you made that function "const" it turns out that you can still
call non-const methods on member variables of the class from a const method
if th
On Tue, 9 Jul 2013, Derek Gaston wrote:
> Nope - it's not that the PointLocator is NULL... the PointLocator is
> _returning_ NULL (ie it couldn't find an element).
Is it possible that it's using the wrong translation vector somehow?
One thread working on boundary pair A inadvertently pulling the
Nope - it's not that the PointLocator is NULL... the PointLocator is
_returning_ NULL (ie it couldn't find an element).
Look at line 1956 in fe_base.C
Derek
On Mon, Jul 8, 2013 at 9:28 PM, Roy Stogner wrote:
>
> On Mon, 8 Jul 2013, Derek Gaston wrote:
>
> It appears that something is wrong in
