On Wed, 10 Dec 2008, Derek Gaston wrote:
> This works for me. Maybe it's because I start with an Exodus file in the
> beginning that has sidesets declared on it. But if I go through the
> following with meshtool... everything works fine:
>
> meshtool -d 3 -i input.e -o out.xda
> meshtool -d 3 -
Roy,
This works for me. Maybe it's because I start with an Exodus file in the
beginning that has sidesets declared on it. But if I go through the
following with meshtool... everything works fine:
meshtool -d 3 -i input.e -o out.xda
meshtool -d 3 -i out.xda -o out.e
After all of this out.e is es
Weird we have many people using this stuff all day long. I'll take a
look at meshtool this afternoon.
Derek
Sent from my iPhone
On Dec 8, 2008, at 11:04 AM, Roy Stogner <[EMAIL PROTECTED]>
wrote:
>
> On Mon, 8 Dec 2008, Derek Gaston wrote:
>
>> You could also use Exodus... I modified the E
On Mon, 8 Dec 2008, Derek Gaston wrote:
> You could also use Exodus... I modified the Exodus writer to correctly write
> out the boundary ids
For some definition of "correctly", anyway. ;-) With the SVN head,
my attempt to run "meshtool -d 2 -i one_tri.xda -o one_tri.exd" dies
in ExodusII_IO_
> You could also use Exodus... I modified the Exodus writer to correctly
> write out the boundary ids which you should then be able to see in
> Paraview (I can definitely see them with Ensight...).
>
>> I've written a little tool to twiddle boundary_info ids based on point
>> location and face norm
You could also use Exodus... I modified the Exodus writer to correctly
write out the boundary ids which you should then be able to see in
Paraview (I can definitely see them with Ensight...).
Derek
On Dec 2, 2008, at 2:23 PM, Roy Stogner wrote:
>
> I've written a little tool to twiddle bound
>> Fine with me as long as mesh.partition(n) still does what it always has.
>
> Two changes for simplicity's sake on the ParallelMesh behavior:
>
> ParMETIS instead of METIS is now the default even when the
> ParallelMesh is still serialized.
>
> The ParmetisPartitioner object doesn't get destro
On Tue, 2 Dec 2008, John Peterson wrote:
> Fine with me as long as mesh.partition(n) still does what it always has.
Two changes for simplicity's sake on the ParallelMesh behavior:
ParMETIS instead of METIS is now the default even when the
ParallelMesh is still serialized.
The ParmetisPartition
On Tue, Dec 2, 2008 at 5:44 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
> On Tue, 2 Dec 2008, Roy Stogner wrote:
>
>> On Tue, 2 Dec 2008, John Peterson wrote:
>>
>>> Use the BoundaryInfo object to Sync with a boundary mesh and write to
>>> GMV. Set each element's processor_id to its boundary ID to
On Tue, 2 Dec 2008, Roy Stogner wrote:
> Or better yet - instead of creating a Parmetis or Metis partitioner
> deep in mesh_base.C, let's leave it up to the Mesh constructor to
> create a partitioner, then give the user the ability to destruct the
> default and replace it with their own (including
On Tue, 2 Dec 2008, Roy Stogner wrote:
> On Tue, 2 Dec 2008, John Peterson wrote:
>
>> Use the BoundaryInfo object to Sync with a boundary mesh and write to
>> GMV. Set each element's processor_id to its boundary ID to color them
>> independently.
>
> Nice idea! Thanks!
>
> It looks like meshtoo
On Tue, Dec 2, 2008 at 3:47 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
> On Tue, 2 Dec 2008, John Peterson wrote:
>
>> On Tue, Dec 2, 2008 at 3:23 PM, Roy Stogner <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> I've written a little tool to twiddle boundary_info ids based on point
>>> location and face norma
On Tue, 2 Dec 2008, John Peterson wrote:
> On Tue, Dec 2, 2008 at 3:23 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
>>
>> I've written a little tool to twiddle boundary_info ids based on point
>> location and face normal direction, but I'm using it on a fine mesh
>> where I'd like to visualize the r
On Tue, Dec 2, 2008 at 3:23 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
>
> I've written a little tool to twiddle boundary_info ids based on point
> location and face normal direction, but I'm using it on a fine mesh
> where I'd like to visualize the results to verify them. Do we output
> boundary
I've written a little tool to twiddle boundary_info ids based on point
location and face normal direction, but I'm using it on a fine mesh
where I'd like to visualize the results to verify them. Do we output
boundary ids to gmv/tecplot/vtk/whatever? And if so, what's the
quickest way to get them
15 matches
Mail list logo
