Adding Boundary IDs

[alessio quaglino]

Hello,

I have a script that generates 3D tet UCD meshes. Is there a way to use them in MOOSE by specifying boundaries in a different way than using IDs (which are not available in the UCD format)? For example, I would like to set Dirichlet conditions at the faces corresponding to x=0 and x=10, can this be done?

Thanks,

Alessio

[Daniel Schwen]

Again the answer is MeshModifiers :-)

If your boundaries are nice and flat you can probably use SideSetsAroundSubdomain and specify a normal to pick a specific side of your domain rather than the entire hull.

--
You received this message because you are subscribed to the Google Groups "moose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moose-users...@googlegroups.com.
Visit this group at http://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/5b6f7e7d-96cd-41de-94a1-2dabd0806aa2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[alessio quaglino]

Thanks. Is this syntax correct?

[MeshModifiers]

  [./left]

    type = SideSetsAroundSubdomain

    block = 0

    new_boundary = 'left'

    normal = '0 0 -1'

  [../]

  [./right]

    type = SideSetsAroundSubdomain

    block = 0

    new_boundary = 'right'

    normal = '0 0 1'

  [../]

[]

I am getting the following error:

*** ERROR ***

The object 'MeshModifiers/left' contains the fo' contains the following block id***

The object 'MeshModifiers/le' contains the following block idsllowing block ids that do no exist on ts that do no exist on the mesh: 0 [39m

ft' contains the following block ids t that do no exist on the mesh: 0 [39m

he mesh: 0 [39m

[[0] /Users/alessio/Dochat do no exist on the mesh: 0 [39m3] /Users/alessio/Documents/pruments/projects/moose/framewo

[1] [2] /Users/alessio/Documents/projecojects/moose/framework/src/base/Blrk/src/base/BlockRestrictable.C/Users/alessio/Documents/projects/moosets/moose/framework/src/base/BlockRestrictable.C, ockRestrictable.C, line 139, compiled Sep  4 2, line 139, compiled Sep  4 2015 at 13:/framework/src/base/BlockRestrictable.C, line line 139, compiled Sep  4 2015 at 13:38:07015 at 13:38:07

[Cody Permann]

That syntax is correct, you should run serially while you debug, it'll make reading those error messages easier. We have a test in moose/test/tests/mesh_modifiers/sidesets_around_subdomain/ that you can look at if you are still stuck. Are you using a generated mesh? If so, you'll need to assign an unused boundary name, something other than "left" or "right".  If not, are the boundaries perpendicular to your normals?

Cody

To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/a82fcbcc-0595-47f0-af8c-5e79c45ca225%40googlegroups.com.

[Peterson, JW]

On Mon, Nov 2, 2015 at 3:04 AM, alessio quaglino <small...@gmail.com> wrote:

Thanks. Is this syntax correct?

[MeshModifiers]

  [./left]

    type = SideSetsAroundSubdomain

    block = 0

    new_boundary = 'left'

    normal = '0 0 -1'

  [../]

  [./right]

    type = SideSetsAroundSubdomain

    block = 0

    new_boundary = 'right'

    normal = '0 0 1'

  [../]

[]

I am getting the following error:

*** ERROR ***

The object 'MeshModifiers/left' contains the fo' contains the following block id***

The object 'MeshModifiers/le' contains the following block idsllowing block ids that do no exist on ts that do no exist on the mesh: 0 [39m

ft' contains the following block ids t that do no exist on the mesh: 0 [39m

he mesh: 0 [39m

[[0] /Users/alessio/Dochat do no exist on the mesh: 0 [39m3] /Users/alessio/Documents/pruments/projects/moose/framewo

[1] [2] /Users/alessio/Documents/projecojects/moose/framework/src/base/Blrk/src/base/BlockRestrictable.C/Users/alessio/Documents/projects/moosets/moose/framework/src/base/BlockRestrictable.C, ockRestrictable.C, line 139, compiled Sep  4 2, line 139, compiled Sep  4 2015 at 13:/framework/src/base/BlockRestrictable.C, line line 139, compiled Sep  4 2015 at 13:38:07015 at 13:38:07

Are you running in parallel?

It looks like the error is that there are no block IDs (i.e. no subdomains) assigned to the mesh at all.  This could be the fault of the UCD reader in libmesh, it probably hasn't been used in 10+ years...

--

John

[Peterson, JW]

Yeah, so for every cell we read a material_id

        in >> dummy        // Cell number, means nothing to us

           >> material_id  // doesn't mean anything at present, might later

           >> type;        // string describing cell type:

but then don't do anything with it :-(

If you can send me a simple, non-proprietary UCD file that is representative of the one you are trying to read, we can probably fix this.

--

John

[alessio quaglino]

OK so I have switched to MSH mesh format and it works fine for me. Thank you for the quick response!

Alessio