Did you ever try my barrier?

On Apr 19, 2013, at 11:48 AM, Roy Stogner <[email protected]> wrote:

> 
> On Fri, 19 Apr 2013, Derek Gaston wrote:
> 
>> Just to put an end-cap on this.... I switched over to the newest
>> mvapich (1.9b) and all of this stuff cleared up.  It's still not
>> clear to me what the issue is/was.... but it's working ;-)
> 
> That's a relief!  Thanks for keeping us updated!
> 
> It'd be nice to know what caused the issue, but probably not worth the
> massive effort it'd take to debug.
> 
> I generally like how we add workarounds for compile-time problems with
> old PETSc versions and compiler versions, because that's generally
> easy enough to do...  but for run-time problems with old MPI versions,
> forget about it.  I've also got a "breaks-with-old-mpich2,
> works-with-new" bug on my plate here that I'm never planning to really
> investigate.
> ---
> Roy------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter_______________________________________________
> Libmesh-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/libmesh-devel


------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to