CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   ANSYS Meshing & Geometry (https://www.cfd-online.com/Forums/ansys-meshing/)
-   -   [ICEM] Appropriate bocos for POPINDA output (https://www.cfd-online.com/Forums/ansys-meshing/157699-appropriate-bocos-popinda-output.html)

FlorisvdBeek August 5, 2015 10:43

Appropriate bocos for POPINDA output
 
2 Attachment(s)
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

NablaDyn November 19, 2017 04:22

Quote:

Originally Posted by FlorisvdBeek (Post 558460)
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.


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