• 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. Flow
  3. merge two meshe files

Stats

  • State Verified Answer
  • Replies 6
  • Subscribers 9
  • Views 3374
  • Members are here 0
More Content

merge two meshe files

sima101f
sima101f over 1 year ago

Hi. 

Is there any way that i can merge two mesh files and make them a single case?

For eg. I have axial compressor meshed separately and my radial compressor meshed separtely. Now I wanted to run them together, but i don't want to mesh them again. 

Thanks

Sid 

  • Sign in to reply
  • Cancel
Parents
  • Colinda
    0 Colinda over 1 year ago

    Hi Sid,

    Did you manage to combine both meshes into one?

    If you still need assistance, could you please tell a bit more how you made the meshes? Did you use AutoGrid5 and then run the simulation in Fine Turbo? Which version are you using? 

    If you used AutoGrid5 you can import both meshes in IGG and set the rotor/stator interface there. It is very important in that case that the outlet of the first row is on the exact same surface as the inlet of the second row. Often that is not the case if the space between both rows is very limited. The outlet region of the first row may then overlap with the inlet region of the second row. This can be taken care of by a z-constant line when initially meshing the rows separately, to create a block at outlet/inlet. In that way the outlet block of the first row and the inlet block of the second block can be removed and the remaining meshing can then be connected.

    Best regards,
    Colinda

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • sima101f
    0 sima101f over 1 year ago in reply to Colinda

    Dear Colinda,

    Thank you very much for your explanation. Indeed it worked. I need some further guidance. As soon as I import my mesh into Fine, things are bit chaotic not very nicely structured. For example in rotating machinery section id number for row 1 of cf stage and ax stage were similar(10). Instead of that id for row 1 for cf stage should be last row of my ax stage + 10. Anyhow, I changed it manually. Now problem is when I go to initial solution tab interface for my cf stage id's are not being recognized. The new generated id numbers are not present. For example, in the following picture id 100 is my channel exit, which in principle should be outlet of cf stage but it is still recognized as outlet of my ax satge and inlet of cf stage. Could you please guide me here.  

    With Regards

    Sid

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Youri Elkouch
    +1 Youri Elkouch over 1 year ago in reply to sima101f

    Hey,

    let me take over Colinda in this case.

    What you are experiencing is most likely due to incorrect boundary condition setup when you merged your 2 meshes in IGG.

    In IGG, once you have imported your 2 meshes, you need to check the boundary conditions. This menu is found in the 'Grid' tab.

    In this menu, make sure that the previous axial outlet (called HO4S....downstream_outlet) is not set to OUT. You have to set it to ROT. Same for the 2 inlet patches of your cf stage inlet, they should change from INL to ROT. 

    Also, about your FINE/Turbo setup : how did you create it? I would advise to duplicate your axial setup, and link to the new mesh. This linking should not modify anything on your axial setup, except for the last patch that should now appear as a rotor/stator (it should not appear anymore as an outlet). The setup of the new cf blocks should be default values, to be set by you.

    If all goes well, you should end up with only one inlet, one outlet, and a new rotor/stator interface.

    Let me know how it goes.

    Best regards,

    Youri

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
Reply
  • Youri Elkouch
    +1 Youri Elkouch over 1 year ago in reply to sima101f

    Hey,

    let me take over Colinda in this case.

    What you are experiencing is most likely due to incorrect boundary condition setup when you merged your 2 meshes in IGG.

    In IGG, once you have imported your 2 meshes, you need to check the boundary conditions. This menu is found in the 'Grid' tab.

    In this menu, make sure that the previous axial outlet (called HO4S....downstream_outlet) is not set to OUT. You have to set it to ROT. Same for the 2 inlet patches of your cf stage inlet, they should change from INL to ROT. 

    Also, about your FINE/Turbo setup : how did you create it? I would advise to duplicate your axial setup, and link to the new mesh. This linking should not modify anything on your axial setup, except for the last patch that should now appear as a rotor/stator (it should not appear anymore as an outlet). The setup of the new cf blocks should be default values, to be set by you.

    If all goes well, you should end up with only one inlet, one outlet, and a new rotor/stator interface.

    Let me know how it goes.

    Best regards,

    Youri

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
Children
No Data
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