• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Pointwise
  3. Influence of Sources on "Match" Symmetry Planes

Stats

  • State Not Answered
  • Replies 3
  • Subscribers 6
  • Views 1552
  • Members are here 0
More Content

Influence of Sources on "Match" Symmetry Planes

TW202408282947
TW202408282947 over 1 year ago

I have run into an issue in multiple scenarios where, when initializing an unstructured block, "match" domains do not respect sources. The most common scenario is when I am modeling only half the domain (assuming a symmetric solution), and my sources (for instance, where I want high resolution in regions of interest) cross through the symmetry plane, and that symmetry plane intersects walls. So when I initialize the block, I have a "match" domain (symmetry plane) that must match the boundary layer growth AND respect sources in the isotropic tet region. When I build the symmetry plane domain, before initializing the block, it is refined by the source, but as soon as I initialize the block, that refinement goes away. Our current "fix" is to "Initialize Boundary Only" so that the symmetry plane gets the correct trex settings at the wall (this will also get rid of the refinement from the source), and then re-"initialize domain" for only the symmetry plane to get the source refinement back, and then initialize the block with "Push Attributes" turned OFF. This is cumbersome, and it is rather unintuitive when trying to explain to someone else how to modify and regenerate one of my meshes.

My understanding is that when "Push Attributes" is ON, it will automatically re-initialize any boundary set to "match", but for some reason, that domain initialization (which the user cannot control) does not have sources turned on. I haven't found a way in any settings to change this behavior, and I don't know why it is default.

I would think that this kind of workflow is fairly standard, so I would appreciate any help navigating the issue how Pointwise intends it. Or if this is just a bug or a inaccessible default setting that should be changed, this would make a great feature request! Thanks!

  • Sign in to reply
  • Cancel
  • Claudio M Pita
    0 Claudio M Pita over 1 year ago

    Hi, 

    Thank you very much for your question. Here my comments:

    • Sources are automatically used when domains affected by it are initialized. 
    • On the other hand, sources only affect the interior of a block by default; they do not affect the block's bounding domains unless this is indicated in the corresponding T-Rex boundary condition. What you need to do in this case is to turn on the Adapt option in the appropriate T-Rex boundary condition (Match in this case) and re-initialize the block. Please note the attached image for reference.
    • To answer your question, this default source-block behavior is done this way because there are instances when it is desired to get a source to only affect the interior of a nearby block and not its boundaries. Please keep in mind that sources have a "region of influence" dictated by their Decay value. 

    I hope this clarifies the situation. 

    Best regards,

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • TW202408282947
    0 TW202408282947 over 1 year ago in reply to Claudio M Pita

    This is great! Thank you Claudio!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Claudio M Pita
    0 Claudio M Pita over 1 year ago in reply to TW202408282947

    Hi, 

    You are very welcome. 

    Glad you found the information useful. 

    Best regards,

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information