Scientific Simulations, LLC
  • Home
  • NSU2D
    • NSU2D Solver
    • UMESH2D
  • NSU3D
    • Capabilities
    • Interfaces
    • Applications
    • Image Gallery
    • NSU3D FAQ
    • Documentation >
      • Getting Started >
        • Obtaining the Code
        • Building the Flow Solver
        • Enabling MPI Support
        • Enabling OpenMP Support
        • Enabling Hybrid MPI-OpenMP Support
        • Other Compile Time Options
        • Building the Utility Suite
        • Configuring the Host System
      • Problem Setup >
        • Compatible Model Grids
        • Boundary Condition File
        • Component File
        • Solver Input File
        • Input File Parameters
        • Optional Parameters
      • Running NSU3D >
        • Launching the Solver
        • Solver Output
        • Restart File Output and Control
        • Additional History and Log Info Files
        • Monitored Values in History Files
        • Source Code Configurable Defaults
        • Solver Restart Facility
      • Utility Code Reference
      • Solver FIle Formats >
        • MCELL Format Description
        • Cell Type Definitions
  • Publications
  • Services
  • Contact
Getting Started
Problem Setup
Running NSU3D
Utility Code Reference
Solver File Formats

Component File

The name of a component file can optionally be specified as input to ugform (see Utility Code Reference), on Line 11 of the parameter input list. If no component file is available, the entry none on Line 11 will cause ugform to automatically create a single component and a single body for the entire grid. To specify various components and bodies on the grid, a component file is created by the user the name of which is specified on Line 11 of the ugform input list. A sample component file is shown below. Components are specified as groups of surface patches, and bodies are specified as groups of components. Each component/body must be assigned a name, and all patches/components must belong to only one component/body.

  • Components are listed first, this is done in lines 1, through 30 in the component file. Line 6 denotes the number of components. The names of these components are listed consecutively beginning on line 8.
  • The patches which constitute each component are then listed beginning on line 15 (in this example), with possible exceptions beginning on line 26 (for this example). Each definition line contains the component number, and a beginning and ending patch number. All patches between these two values are assigned to that component.  Patches can be listed multiple times in this assignment. Their component assignment is overwritten with the latest assignment value when they are specified multiple times. The EXCEPTIONS specification also overwrites the component numbers for particular patches. This portion of the file can be deleted (i.e. Lines 23 - 30 inclusively) if no exceptional patches are listed.
  • The specification of bodies begins on Line 35. This specification is similar to that of components except that bodies are composed of sets of components rather than patches. The number and range of the components must of course be consistent with that specified in the first portion of the component file.


       SAMPLE COMPONENT DEFINITION FILE       
============================================   
GROUPING OF PATCHES INTO COMPONENTS            
============================================   
NUMBER OF COMPONENTS                           
4.                                             
ICOMP                   COMP_NAME                       
1.                             FUSELAGE                        
2.                             WING                            
3.                             SYMMETRY_PLANE                  
4.                             OUTER_BOUNDARY                  
--------------------------------------------   
COMPONENT DEFINITIONS                          
COMPONENT      BEG_PATCH      END_PATCH        
1.                             1.                           5.               
1.                             11.                        12.              
1.                             14.                        59.              
2.                             60.                        87.              
2.                             95.                        98.              
2.                             88.                        94.              
3.                             13.                        13.              
4.                             6.                          10.              
--------------------------------------------   
EXCEPTIONS                                     
COMPONENT      PATCH                           
1.                             60.                             
1.                             67.                             
1.                             74.                             
1.                             81.                             
1.                             88.                             
============================================   
GROUPING OF COMPONENTS INTO BODIES             
============================================   
NBOD                                           
2.                                             
IBOD                      BOD_NAME                        
1.                            AIRPLANE                        
2.                            OUTER_BOUNDARY                  
--------------------------------------------   
BODY DEFINITIONS                               
BODY                    BEG_COMP       END_COMP         
1.                             1.                          2.               
2.                             3.                          4.               
--------------------------------------------   
EXCEPTIONS                                     
BODY                    COMPONENT                       
1.                            1.                              
​
1.                            2.
Powered by
  • Home
  • NSU2D
    • NSU2D Solver
    • UMESH2D
  • NSU3D
    • Capabilities
    • Interfaces
    • Applications
    • Image Gallery
    • NSU3D FAQ
    • Documentation >
      • Getting Started >
        • Obtaining the Code
        • Building the Flow Solver
        • Enabling MPI Support
        • Enabling OpenMP Support
        • Enabling Hybrid MPI-OpenMP Support
        • Other Compile Time Options
        • Building the Utility Suite
        • Configuring the Host System
      • Problem Setup >
        • Compatible Model Grids
        • Boundary Condition File
        • Component File
        • Solver Input File
        • Input File Parameters
        • Optional Parameters
      • Running NSU3D >
        • Launching the Solver
        • Solver Output
        • Restart File Output and Control
        • Additional History and Log Info Files
        • Monitored Values in History Files
        • Source Code Configurable Defaults
        • Solver Restart Facility
      • Utility Code Reference
      • Solver FIle Formats >
        • MCELL Format Description
        • Cell Type Definitions
  • Publications
  • Services
  • Contact
✕