CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > ANSYS > ANSYS Meshing & Geometry

[ICEM] Appropriate bocos for POPINDA output

Register Blogs Community New Posts Updated Threads Search

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   August 5, 2015, 11:43
Default Appropriate bocos for POPINDA output
  #1
New Member
 
Join Date: Jul 2015
Posts: 5
Rep Power: 11
FlorisvdBeek is on a distinguished road
Hi guys,

I could really use some help! As I have found absolutely nothing about output for popinda solvers yet, I must be one of the only few using this functionality, but as making this work would save me a lot of time further in my process, here goes:

I have (succesfully) created a 2D structured HEXA mesh for a jet engine in a farfield. Now, for an acoustic solver (PIANO) I require a .popform data file, which ICEM CFD can produce directly by the POPINDA solver functionality under output. I seem completely unable, though, to get a proper .log file for the boundary conditions. All conditions in this output file are specified as 'unspecified BCs', as can be seen in the screenshots.

The steps I have undertaken:
  • Import geometry
  • Divide geometry over different parts (ENGINE_CORE etc..)
  • Do the blocking
  • Yes I am very sure that all edges which represent the contours (farfield and engine geometry curves) are associated The points are associated to a seperate part called V1, but this shouldn't make a difference (right?)
  • Create structured multiblock mesh
  • Set BCs under Output (for POPINDA)
  • Set par file under Output
  • Export .popform and .log input files
I've read somewhere else that it can be important to first define the BCs and then convert the premesh to a structured multiblock, but this does not seem to make any difference in my case.

I've added a ss of the BC and PAR dialog screens, and a part of the .log file (to demonstrate the lack of variation, block 1 should have 3 different bocos..). For clearity, PIANO requires ITYP to be '-1' to indicate an interior edge, '12' for a wall and '21' for radiation (farfield).

Any help is most welcome!
Thanks in advance,
Floris
Attached Images
File Type: jpg boco.jpg (30.9 KB, 8 views)
File Type: jpg parfile.jpg (35.3 KB, 7 views)
FlorisvdBeek is offline   Reply With Quote

Old   November 19, 2017, 05:22
Default
  #2
Senior Member
 
NablaDyn's Avatar
 
Join Date: Oct 2015
Location: Germany
Posts: 100
Rep Power: 11
NablaDyn is on a distinguished road
Quote:
Originally Posted by FlorisvdBeek View Post
Hi guys,

I could really use some help! As I have found absolutely nothing about output for popinda solvers yet, I must be one of the only few using this functionality, but as making this work would save me a lot of time further in my process, here goes:

I have (succesfully) created a 2D structured HEXA mesh for a jet engine in a farfield. Now, for an acoustic solver (PIANO) I require a .popform data file, which ICEM CFD can produce directly by the POPINDA solver functionality under output. I seem completely unable, though, to get a proper .log file for the boundary conditions. All conditions in this output file are specified as 'unspecified BCs', as can be seen in the screenshots.

The steps I have undertaken:
  • Import geometry
  • Divide geometry over different parts (ENGINE_CORE etc..)
  • Do the blocking
  • Yes I am very sure that all edges which represent the contours (farfield and engine geometry curves) are associated The points are associated to a seperate part called V1, but this shouldn't make a difference (right?)
  • Create structured multiblock mesh
  • Set BCs under Output (for POPINDA)
  • Set par file under Output
  • Export .popform and .log input files
I've read somewhere else that it can be important to first define the BCs and then convert the premesh to a structured multiblock, but this does not seem to make any difference in my case.

I've added a ss of the BC and PAR dialog screens, and a part of the .log file (to demonstrate the lack of variation, block 1 should have 3 different bocos..). For clearity, PIANO requires ITYP to be '-1' to indicate an interior edge, '12' for a wall and '21' for radiation (farfield).

Any help is most welcome!
Thanks in advance,
Floris
Don't know if this is still a relevant topic.

First, it depends on the solver you are going to use for CFD, how to define the POPINDA boundary conditions. If you are using e.g. FLOWer, you will need the log file which is being created with the Logic software. AFAIK it only creates the patch lists for the boundary faces which you'll afterwards have to assign a boundary condition manually. But if you use OpenFOAM you do not need the log file.
NablaDyn is offline   Reply With Quote

Reply

Tags
bocos, icem 2d blocking, popform, popinda


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[swak4Foam] outputTime in Swak function immortality OpenFOAM Community Contributions 20 October 6, 2022 13:08
writing execFlowFunctionObjects immortality OpenFOAM Post-Processing 30 September 15, 2013 07:16
RNG diverged during the analysis the flow over a multi element airfoil, why? s.m OpenFOAM Running, Solving & CFD 0 August 5, 2013 09:39
mixerVesselAMI2D's mass is not balancing sharonyue OpenFOAM Running, Solving & CFD 6 June 10, 2013 10:34
lift and drag on ship superstructures vaina74 OpenFOAM Running, Solving & CFD 3 June 8, 2010 13:30


All times are GMT -4. The time now is 14:43.