Just noticed that this had been buried in my outbox:
On Thu, 21 Apr 2011, Vikram Garg wrote:
> Hey,
> I am writing because this is either an interesting theoretical
> requirement I am not understanding or a bug in my code/libMesh. For my
> application, I want to set different penalties on d
On May 18, 2011, at 1:48 PM, Roy Stogner wrote:
> Good to hear. The one aspect to that support that I'd feared might be
> lacking is I/O.
>
> Does that work for visualizing boundary ids as well?
Visualizing boundary ids is simple... just use Paraview or Ensight. Ensight is
great... it colors
On Wed, 18 May 2011, Derek Gaston wrote:
> On May 18, 2011, at 1:01 PM, Roy Stogner wrote:
>
>> From a code point of view it's no big deal either way - get the
>> interior parent of your element and you can get the subdomain id or
>> boundary ids from that. But for visualization, copying boundar
First: I don't use BoundaryMesh... so go wild
On May 18, 2011, at 1:01 PM, Roy Stogner wrote:
>> From a code point of view it's no big deal either way - get the
> interior parent of your element and you can get the subdomain id or
> boundary ids from that. But for visualization, copying boun
On Wed, 18 May 2011, John Peterson wrote:
On Wed, May 18, 2011 at 12:37 PM, Roy Stogner wrote:
Currently when we sync a BoundaryMesh for the entire boundary, we give
the boundary elements subdomain_ids and processor_ids that correspond
(after mapping them to be sequential starting with 0) to
On Wed, May 18, 2011 at 12:37 PM, Roy Stogner wrote:
>
> Currently when we sync a BoundaryMesh for the entire boundary, we give
> the boundary elements subdomain_ids and processor_ids that correspond
> (after mapping them to be sequential starting with 0) to the boundary
> condition ids their corr
Currently when we sync a BoundaryMesh for the entire boundary, we give
the boundary elements subdomain_ids and processor_ids that correspond
(after mapping them to be sequential starting with 0) to the boundary
condition ids their corresponding interior elements' sides had...
unless we're sync'ing
