How to obtain the grid and geometry files for the T Junction tutorial

[Yvan Fournier]

Hello,
When setting zones and boundary conditions, all that matters is the way you name these zones (Code_Saturne imports the names, not the types). You may the use the names in selection criteria. In the tutorial, names = numbers due to the file format limitations, so it may be less clear, but simply assigning ANSYS workbench boundary condition names in Code_Saturne's GUI boundary condition "localization" field should work.
If boundary conditions are not set up correctly, Code_Saturne 1.3.3 will issue a lsit of faces not correctly defined, which is not very useful. Versions 2.0-rc2 and later output an ensight.error postprocessing directory in which faces not correctly defined may be visualized, which is much more useful for non-trivial cases.
Best regards,
  Yvan

[Debashis Basu]

Thanks for the reply.
Best wishes,
Debashis
 
Previously Yvan Fournier wrote:

Hello,
When setting zones and boundary conditions, all that matters is the way you name these zones (Code_Saturne imports the names, not the types). You may the use the names in selection criteria. In the tutorial, names = numbers due to the file format limitations, so it may be less clear, but simply assigning ANSYS workbench boundary condition names in Code_Saturne's GUI boundary condition "localization" field should work.
If boundary conditions are not set up correctly, Code_Saturne 1.3.3 will issue a lsit of faces not correctly defined, which is not very useful. Versions 2.0-rc2 and later output an ensight.error postprocessing directory in which faces not correctly defined may be visualized, which is much more useful for non-trivial cases.
Best regards,
  Yvan