On Dec 1, 2010, at 7:31 PM, Roy Stogner wrote:
> Did you really managed to get overlapping BC IDs working with a
> dozen-line patch? Egg on our faces... I don't think any of the
> primary developers use multiple IDs on the same boundary right now,
> but if we'd known it would be that simple to s
Thanks very much, and sorry I let this get buried in my outbox - it's
in the svn head now.
---
Roy
On Tue, 9 Nov 2010, Erik Zeek wrote:
> When PETSc is installed into a prefix directory it no longer has a directory
> component for $PETSC_ARCH. The test for PETSc MPI support didn't allow for
> t
On Wed, 1 Dec 2010, Boyce Griffith wrote:
> I noticed that adding multiple boundary IDs to the boundary_info object
> caused an assertion to fail in xdr_io::write_serialized_bcs() at line
> 740 of xdr_io.C, which asserts that n_bcs == n_bcs_out.
>
> Looking at the code that packs up the IDs, it a
Hi, Folks --
I noticed that adding multiple boundary IDs to the boundary_info object
caused an assertion to fail in xdr_io::write_serialized_bcs() at line
740 of xdr_io.C, which asserts that n_bcs == n_bcs_out.
Looking at the code that packs up the IDs, it appears that only the
first boundary
