-----------------------------------------------
== Download and compile (viz nodes) ==
This sections is inspired from <http://redmine.scorec.rpi.edu/projects/pumi/wiki/Build_Instructions>. Please read it first before continuing, as some information on this wiki page are not repeated.
The SCOREC tools now build against CMake. Only Parma, the PHASTA utilities and phParAdapt still build against Autotools.
From a termonal, run the following commands:
soft add +cmake
soft add +git
cd ~
mkdir SCOREC.develop
cd SCOREC.develop
git clone ssh://your_username@jumpgate-phasta.colorado.edu/users/mrasquin/SCOREC.develop/compilation

The git command will download these instructions, along with a checkout and compile script for Parma and phParAdapt. The next commands are to compile the whole stack with the GNU compiler on the viz nodes are:
soft add +gcc-4.8.1
soft add +openmpi-gnu
mkdir install-gcc-O2 //all the libraries and executable will go there
mkdir build-gcc-O2 // this is where you will run the cmake commands
cd build-gcc-O2
cmake ../CMake.SCOREC -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_INSTALL_PREFIX=/users/mrasquin/SCOREC.develop/install-gcc-O2 -DCMAKE_C_COMPILER=mpicc -DCMAKE_CXX_COMPILER=mpicxx

This will create the Makefiles. To compile the actual code you need to
make
make install

inside the build-gcc-O2 directory.

Do not forget to update the path to PREFIX according to your install directory.
By default, it compiles with meshmodel. See the redmine link above about how to compile with parasolid or other geometric model.
The cmake command downloads the parmetis package inside the build-gcc-O2 directory. If you want to use 64 bit integer in parmetis, which is only useful for big meshes in serial, edit

parmetis-4.0.2/metis/include/metis.h

and set

#define IDXTYPEWIDTH 64

Now, compile the SCOREC tools (in serial only for now - do not try make -j 8 for instance):

make 2>&1 | tee log_cmake_make.dat
make install 2>&1 | tee log_cmake_install.dat
cd .. #back to SCOREC.develop

Now you should have the pumi tools installed in SCOREC.develop/install-gcc-O2. It is time to download and compile the Parma library. From SCOREC.develop,
mkdir Autotools.SCOREC
cd Autotools.SCOREC
cp ../compilation/parma_install.sh .

Edit and update the script parma_install.sh. In particular, edit PREFIX to the same path used in the cmake command above. Other parameters you need to update are the compilation options (DEBUG), the svn username if you have one, etc. Then:
./parma_install.sh checkout_all 2>&1 | tee log_autotools_parma_checkout.dat
./parma_install.sh setup_all 2>&1 | tee log_autotools_parma_setup.dat
./parma_install.sh intall_all 2>&1 | tee log_autotools_parma_install.dat

For phParAdapt (and PHASTA utilites), the procedure is similar:
cp ../compilation/phParAdaptBuild.sh
edit path to PREFIX in parma_install.sh + other parameters
./phParAdaptBuild.sh checkout_all 2>&1 | tee log_autotools_phparadapt_checkout.dat
./phParAdaptBuild.sh setup_all 2>&1 | tee log_autotools_phparadapt_setup.dat
./phParAdaptBuild.sh install_all 2>&1 | tee log_autotools_phparadapt_install.dat

Your phParAdapt executable should be in ~/SCOREC.develop/install-gcc-O2/bin/phParAdapt

== Convert geom_ver63.sms to FMDB format==
*This can be done in same directory in which you created geom_ver63.sms. You first need to convert geom_ver63.sms to FMDB format. The executable that will do this is at /users/jema6380/runSimMesh2FMDB.sh
*Make a link from the output file, geom_FMDB.sms, to geom.sms (ln -s geom_FMDB.sms geom.sms)

==Create geom.spj==
*If you have not done so already, create geom.spj. This is not done with Simulation Maker as was done previously, but can simply be done with a vim editor. See the file /users/jema6380/Models/Boeing/BetaScale2CaltechTunnel/CT_Open32_B0_D30_U20/9-A0-24jets/geom.spj for some guidance. As a quick example, if your boundary condition is a velocity of 20 i_hat m/s (comp3) on the inlet face (which let's say has a face number of 1651), then you would enter:
comp3: 1651 2 20 1 0 0
where the "2" designates that we are talking about a face, which has 2 dimensions; the "20" is the speed; and the "1 0 0" is the direction.
*Michel created a script that will make this process faster, which is desirable if you have a large number of faces. If you want to use the script, then first use the executable at /users/jema6380/getFaceList.sh to create a list of faces. From the terminal type:
./getFaceList.sh "input_file"
where "input_file" is the file that contains the face numbers, which presumably does not already list them consecutively. This might be BLattr.inp, for exmple.
*Now create a new directory called "FacesModelAttributes" and put all of the boundary conditions in .dat files. See the files in /users/jema6380/Models/Boeing/BetaScale2CaltechTunnel/CT_Open32_B0_D30_U20/Simplified_SPJ_file/FacesModelAttributes/ for guidance. Make sure all the .dat files have a name that begins with "attr_" .
*copy /users/jema6380/buildSimplifiedAttrFile.sh to the Simplified_SPJ_file directory and do:
./buildSimplifiedAttrFile.sh
*This should create a file called result.spj, which contains all of the boundary conditions. cd back to your working mesh directory and make a link from result.spj to geom.spj. Also make a link from result.spj to geomNOIC.spj

==Partition geom_ver63.sms==
*Make sure you have geom.xmt_txt in your working directory.

PhParAdapt/SCOREC

2013-07-30T04:36:15Z

Chitak:

PhParAdapt/SCOREC

2013-07-30T04:35:23Z

Chitak: Created page with "== Download and compile (viz nodes) == This sections is inspired from <http://redmine.scorec.rpi.edu/projects/pumi/wiki/Build_Instructions>. Please read it first before continuin..."

== Download and compile (viz nodes) ==
This sections is inspired from <http://redmine.scorec.rpi.edu/projects/pumi/wiki/Build_Instructions>. Please read it first before continuing, as some information on this wiki page are not repeated.
The SCOREC tools now build against CMake. Only Parma, the PHASTA utilities and phParAdapt still build against Autotools.
From a termonal, run the following commands:
soft add +cmake
soft add +git
cd ~
mkdir SCOREC.develop
cd SCOREC.develop
git clone ssh://your_username@jumpgate-phasta.colorado.edu/users/mrasquin/SCOREC.develop/compilation

The git command will download these instructions, along with a checkout and compile script for Parma and phParAdapt. The next commands are to compile the whole stack with the GNU compiler on the viz nodes are:
soft add +gcc-4.8.1
soft add +openmpi-gnu
mkdir install-gcc-O2 //all the libraries and executable will go there
mkdir build-gcc-O2 // this is where you will run the cmake commands
cd build-gcc-O2
cmake ../CMake.SCOREC -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_INSTALL_PREFIX=/users/mrasquin/SCOREC.develop/install-gcc-O2 -DCMAKE_C_COMPILER=mpicc -DCMAKE_CXX_COMPILER=mpicxx

This will create the Makefiles. To compile the actual code you need to
make
make install

inside the build-gcc-O2 directory.

Do not forget to update the path to PREFIX according to your install directory.
By default, it compiles with meshmodel. See the redmine link above about how to compile with parasolid or other geometric model.
The cmake command downloads the parmetis package inside the build-gcc-O2 directory. If you want to use 64 bit integer in parmetis, which is only useful for big meshes in serial, edit

parmetis-4.0.2/metis/include/metis.h

and set

#define IDXTYPEWIDTH 64

Now, compile the SCOREC tools (in serial only for now - do not try make -j 8 for instance):

make 2>&1 | tee log_cmake_make.dat
make install 2>&1 | tee log_cmake_install.dat
cd .. #back to SCOREC.develop

Now you should have the pumi tools installed in SCOREC.develop/install-gcc-O2. It is time to download and compile the Parma library. From SCOREC.develop,
mkdir Autotools.SCOREC
cd Autotools.SCOREC
cp ../compilation/parma_install.sh .

Edit and update the script parma_install.sh. In particular, edit PREFIX to the same path used in the cmake command above. Other parameters you need to update are the compilation options (DEBUG), the svn username if you have one, etc. Then:
./parma_install.sh checkout_all 2>&1 | tee log_autotools_parma_checkout.dat
./parma_install.sh setup_all 2>&1 | tee log_autotools_parma_setup.dat
./parma_install.sh intall_all 2>&1 | tee log_autotools_parma_install.dat

For phParAdapt (and PHASTA utilites), the procedure is similar:
cp ../compilation/phParAdaptBuild.sh
edit path to PREFIX in parma_install.sh + other parameters
./phParAdaptBuild.sh checkout_all 2>&1 | tee log_autotools_phparadapt_checkout.dat
./phParAdaptBuild.sh setup_all 2>&1 | tee log_autotools_phparadapt_setup.dat
./phParAdaptBuild.sh install_all 2>&1 | tee log_autotools_phparadapt_install.dat

Your phParAdapt executable should be in ~/SCOREC.develop/install-gcc-O2/bin/phParAdapt

2013-07-17T21:42:58Z

Chitak: Created page with "There are currently many versions of NSpre out there. The oldest version of NSpre which should work with any meshes created with Simmetrix versions prior to 7.2-120626, uses geo..."

Opening a Simmetrix ticket

2012-10-29T02:05:21Z

Chitak:

To open a ticket with simmetrix, use the following support form.

====Simmetrix Support Form====

Customer ID: jan001
Platform: linux
Simmetrix Product: MeshSim
Product Version: 7.2 (edit this to whichever version you are using)
Type [Question,Bug,Feature Request]: Question/Bug/Feature request
Priority [High,Medium,Low]: High/Medium/Low
Summary: (e.g. BL gets destroyed in initial meshing at some places.)

Description:

Here, put a brief description of the bug or question you have for Simmetrix.

You can put the Summary above as the subject in your email. The email should be sent to "support@simmetrix.com'. Remember, for the email to get registered as a support ticket, the delimiter ( ====Simmetrix Support Form====) has to be before all the content of the email and has to be exactly
====Simmetrix Support Form====

If this is not followed, you will get an email from Simmetrix saying "Delimiter not found".

Opening a Simmetrix ticket

2012-10-29T01:58:47Z

Chitak:

To open a ticket with simmetrix use the following support form.

====Simmetrix Support Form====

Customer ID: jan001
Platform: linux
Simmetrix Product: MeshSim
Product Version: 7.2 (edit this to whichever version you are using)
Type [Question,Bug,Feature Request]: Bug
Priority [High,Medium,Low]: High/Medium/Low
Summary: (e.g. BL gets destroyed in initial meshing at some places.)

Description:

Put a brief description of the bug or question you have for Simmetrix.

You can put the Summary above as the subject in your email. The email should be sent to support@simmetrix.com. Remember, for the email to get registered as a support ticket, the delimiter ( ====Simmetrix Support Form====) has to be before all the content of the email and has to be exactly ====Simmetrix Support Form====

2012-10-29T01:57:08Z

Chitak:

Opening a Simmetrix ticket

2012-10-29T01:51:54Z

Chitak: /* Simmetrix Support Form */

Opening a Simmetrix ticket

2012-10-29T01:50:38Z

Chitak: Created page with "To open a ticket with simmetrix use the following support form. ====Simmetrix Support Form==== Customer ID: jan001 Platform: linux Simmetrix Product: MeshSim Product Version: 7..."

Janus Cheat Sheet

2012-07-27T13:20:05Z

Chitak: /* Running Jobs */

== Login ==
ssh your_identikey_user@login.rc.colorado.edu
[pin][token]

== Running Jobs ==
Environment Setup:
use Torque
use Moab
use Git
use .openmpi-1.4.3_intel-12.0_ib
use Graphviz
use Subversion

available nodes/cores:

pbsnodes -a
showbf
Jobscript Template:

#!/bin/bash
#PBS -N name_of_job
#PBS -l walltime=0:20:00
#PBS -l nodes=1:ppn=12
. /curc/tools/utils/dkinit
reuse .openmpi-1.4.3_intel-12.0_ib

mpirun /path/to/executable

Submission:

qsub -q janus-debug jobscript.sh

Status

checkjob job_id
showq -u $USER

Cancel:

qdel job_id

Large Memory, Interactive:

qsub -I -l nodes=1:ppn=32,walltime=1:00:00 -q himem

Interactive, for debugging (with totalviewer)

qsub -X -I -l nodes=1:ppn=12,walltime=1:00:00 -q janus-debug

Non Default allocation:

qsub -A UCBXXXXXXX job.sh

or in the job script:
#PBS -A UCBXXXXXXX

== Allocation Status ==
use Crc-allocations
check_allocation.py
use Moab
showstats -u $USER

==[[GridFTP]]==
export MYPROXY_SERVER_DN=$MYPROXY_SERVER_DN"/C=US/O=Globus Consortium/OU=Globus Connect Service/CN=842a610a-4de7-11e1-9674-123138151443"
myproxy-logon -T -b -s gridftp-00.rc.colorado.edu -v -l bema1643

globus-url-copy -v -r -cd -rst -rst-retries 0 -fast -vb -p 64 -stripe -tcp-bs 4M -g2 -ss '/C=US/O=Globus Consortium/OU=Globus Connect Service/CN=842a610a-4de7-11e1-9674-123138151443' gsiftp://gridftp-00.rc.colorado.edu/lustre/janus_scratch/bema1643/test.img sshftp://matthb2@jumpgate-phasta.colorado.edu/scratch/matthb2/foo/

globus-url-copy -v -r -cd -rst -rst-retries 0 -fast -vb -p 64 -stripe -tcp-bs 4M -g2 -ds '/C=US/O=Globus Consortium/OU=Globus Connect Service/CN=842a610a-4de7-11e1-9674-123138151443' sshftp://matthb2@jumpgate-phasta.colorado.edu/scratch/mrasquin/416M/ gsiftp://gridftp-00.rc.colorado.edu/lustre/janus_scratch/bema1643/

(note: -ss to specify that the source server has a non-standard DN, -ds for the destination)

==Queues/Policy==
https://www.rc.colorado.edu/crcdocs/queues
https://www.rc.colorado.edu/policies/janus-jobs

BLMesher

2012-05-04T07:41:26Z

Chitak: /* Example 8: Global BL attributes */

[[Category:Software]]
How to create the mesh '''using script'''

-----------------------------------------------
== Start ==
* To begin, we need a geometry model. It can be created using commercial softwares such as Solid Work and saved as *.x_t
* You need the BLMesher code which is available on svn:
svn co https://redmine.scorec.rpi.edu/svn/phasta/BLMesher
* If you have read only access to phasta project on redmine, then use:
svn co https://redmine.scorec.rpi.edu/anonsvn/phasta/BLMesher

==Files needed ==
Create a folder and copy all these files into it.
* Geometry model file (geom.xmt_txt or geom.x_t)
* Mesh generation attribution file (Attributes.inp)
* exe file (Run.sh)

File Attributes.inp is the script that defines the mesh generation characteristics for different entities of the model.

Run.sh is an exe file including commands as below:
PATH=/users/chitak/develop/Meshing/BLMesher
$PATH/bin/x86_64_linux/BLMesher-0 geom.xmt_txt geom.sms 1 0.1 BLAttr.inp
It defines the proper path for mesh generator. It also defines that geom.xmt_txt is the model file and the mesh must be created using the attributes defined in Attributes.inp and the mesh data must be written into geom.sms

In the second line of the Run.sh file, the value before attributes.inp (in this case, 0.1) is the size of the boxes that are created before the the final mesh generation. (In fact, BLMesher tries to divide the whole domain into small boxes and then divide these boxes to create the mesh).
Lets call the characteristic size of the domain, d, and the size of the boxes E.

You must choose E as below and use it in Run.sh:
<math> E=\frac{d}{2^{(m+1)}} </math> or <math> E=\frac{d}{2^m} </math>
m is an integer.

Other flags like optimization and smoothing can also be given in this line. Use -h option with the executable to view the complete list of the options and their meaning. Note that the order of these flags is extremely important. Other than the executable, there are 11 other command line inputs which can be given. These can be given in Run.sh with the executable.

== Edit the script ==
* The first line is the version number (for future use). For eg.: version 1
* Use "#" to comment a line or disable it.
* To create attributes for each model entity, two lines in the following format are being used.
<entity dimension> <entity tag> <size type> <attribute type> <extra>
<value or expression for mesh size on this entity>
* Note that a blank line between these two lines is not allowed.

.

== Create the mesh ==
* After preparing the script, execute the file Run.sh. It creates the mesh and write the data to geom.sms (as you defined in Run.sh).
* Note that after executing the Run.sh, you must use command "top" to check the memory usage. If you find out that memory usage is huge and is increasing, you must kill the job before the machine crashes

.

== Visualize the mesh ==
To see the generated mesh, you can use simapps:
/usr/local/simapps/<simapps version>/simapps ThreeDViewer &

.

== Define the mesh characteristics in attribute file ==
The parameters in the first line, respectively are:
- Entity dimension: 2 for 2-D cases and 3 for 3-D cases
- Entity tag: You can find the entity tag using simapps
- Size type on entity: 1 for absolute mesh size and 2 for relative mesh size
- Attribute type on entity:
0 just imposes the size on entity. '''<extra> field''' is NULL
1 for entity with boundary layers. '''<extra> field''' is explained below.
2 for periodic entity: In this case, '''<extra> field''' is followed with slave entity tag
3 for refinement source. Specify entity dimension as -1 in this case. '''<extra> field''' is explained below.

'''<extra> field:'''

For Boundary layer:
is followed with (a) faceSide/useDir (BL orientation), (b) numEndEnts (==0, layers with fixed heigths), (c) firstLayerHeight, (d) totalHeight, (e) nLayers, (f) blMixed, (g) blBlends, (h) blPropagate and (i) edgeBLFaceTag (only if 2D BL on edge)
is followed with (a) faceSide/useDir (BL orientation), (b) numEndEnts (==2, to vary height linearly between two end/bounding entities), (c) varyDirection, (d) endEntTag1 , (e) firstLayerHeight1, (f) totalHeight1, (g) endEntTag2, (h) firstLayerHeight2, (i) totalHeight2, (j) nLayers, (k) blMixed, (l) blBlends, (m) blPropagate and (n) edgeBLFaceTag (only if 2D BL on edge)

For refinement:
is followed with (a) ref. source type (1-cube, 2-cylinder etc.), (b) source info. as Simmetrix APIs (like radius, length, center and normal in case of cylinder, and center, wdir, hdir and ddir in case of cube/parallelepiped)

* Note if entity dimension is -1, (in case of refinement) do not specify the entity tag and size type.

.

== Example 1: Uniform mesh ==
Simple uniform mesh on region with tag 205
3 205 1 0
2e-4

The above lines can be divided as below:
(3) (205) (1) (0)
(2e-4)

(3): Entity dimension. It's a 3-D region.
(205): Entity tag
(1): Size type on entity. 1 for absolute mesh size
(0): Attribute type on entity. 0 just imposes the size on entity. <extra> field is NULL
(2e-4): Mesh size (This is in the second line)
Note: The second line (Mesh size) can be a value or an expression such as:
0.0125+0.1*(1.0-exp(-3.0*sqrt(($x-0.0)^2+($y-0.0)^2+($z-0.5)^2)))

.

== Example 2: Refinement in a cylindrical region ==
-1 3 1 1.5e-3 1 2 0.3 0 0 0 1
2.5e-4

The above lines can be divided as below:
(-1) (3) (1) (1.5e-3) (1) (2 0.3 0) (0 0 1)
(2.5e-4)

(-1): Entity dimension, for refinement cases
(3): Attribute type. in this case, refinement.
(1): For refinement in a cylindrical region
(1.5e-3 ): Radius
(1): Length of the Cylinder (Half)
(2 0.3 0): The center of the circle
(0 0 1): Axis
(2.5e-4): mesh size (This is in the second line)

.

== Example 3: Refinement in a box region ==
-1 3 2 6e-3 5e-3 0.0 1.5e-3 0.0 0.0 0.0 5.0e-4 0.0 0.0 0.0 5.0e-4
2.5e-4

The above lines can be divided as below:
(-1) (3) (2) (6e-3 5e-3 0.0) (1.5e-3 0.0 0.0) (0.0 5.0e-4 0.0) (0.0 0.0 5.0e-4)
(2.5e-4)

(-1): Entity dimension. -1 only for refinement cases.
(3): Attribute type. in this case, refinement.
(2): For refinement in a box region
(6e-3 5e-3 0.0): The center of the box
(1.5e-3 0.0 0.0): x-Half length
(0.0 5.0e-4 0.0): y-Half length
(0.0 0.0 5.0e-4): z-Half length
(2.5e-4): mesh size (This is in the second line)

.

== Example 4: Refine the mesh along 3 lines on face with tag 5 ==
3 5 1 0
(0.5e-03) +0.1*(1.0-exp(-2.0*sqrt(($x-1.9)^2+($y-0.36)^2)))*(1.0-exp(-10.0*sqrt(($x-1.77)^2+($y-0.42)^2)))*(1.0-exp(-6.0*sqrt(($x-1.8)^2+($y-0.43)^2)))
The first line can be divided as below:
(3) (5) (1) (0)

(3): Entity dimension, 3-D
(5): Entity tag
(1): Size type on entity. 1 for absolute mesh size
(0): Attribute type on entity. 0 just imposes the size on entity. <extra> field is NULL

This is an example of an expression that will make the mesh fine in three lines. e.g., x=1.9 y=0.36 on model entity number 5.

.

== Example 5: Periodic mesh ==

If periodic BC is used at two faces, the mesh must be identical in both of them.

In this case, faces 1 and 81 are periodic

2 1 1 2 81
2.1e-4

The above lines can be divided as below:
(2) (1) (1) (2) (81)
(2.1e-4)

(2): Entity dimension, 2-D. it's a face.
(1): Entity tag
(1): Size type on entity. 1 for absolute mesh size
(2): Attribute type on entity. 2 for periodic entity. <extra> field is followed with a slave entity tag
(81): Slave entity tag
(2.1e-4):mesh size (This is in the second line)

.

== Example 6: Boundary layer mesh , constant thickness ==
On face with tag 173
2 173 1 1 0 0 0.4e-4 3.e-4 5 0 0 0
1.61e-4

The above lines can be divided as below:
(2) (173) (1) (1) (0) (0) (0.4e-4) (3.e-4) (5) (0) (0) (0)
(1.61e-4)

(2): Entity dimension, 2-D. it's a face.
(173): Face tag
(1): Size type on entity. 1 for absolute mesh size
(1): Attribute type on entity. 1 for entity with boundary layers.
(0): Boundary layer orientation (FaceSide/useDir)
(0): NumEndEnts. 0 for layers with fixed heights
(0.4e-4): First layer height
(3.e-4): Total height of boundary layer
(5): Number of layers
(0): Boundary layer Mixed topology (1 for triangles and quads)
(0): Boundary layer blending. 0 for no BL blending
(0): Boundary Layer propagation
(1.61e-4): mesh size on the surface (This value is in the second line)

If you are specifying a 2D BL on a model edge, then at the end of the line, you have to give a target face tag, to which face you want that BL attribute applied.

.

== Example 7: Boundary layer mesh, ramped thickness ==
On face with tag 27
2 27 1 1 0 2 0 22 1.e-3 2.e-2 20 2.e-3 10.e-2 5 1 0 0
0.1

The above lines can be divided as below:
(2) (27) (1) (1) (0) (2) (0) (22) (1.e-3) (2.e-2) (20) (2.e-3) (10.e-2) (5) (1) (0) (0)
(0.1)

(2): Entity dimension, 2-D. it's a face.
(27): Face tag
(1): Size type on entity. 1 for absolute mesh size
(1): Attribute type on entity. 1 for entity with boundary layers.
(0): Boundary layer orientation (FaceSide/useDir)
(2): For Layers with linearly varying height (NumEndEnts)
(0): Direction of variation (pos. x-dir.)
(22): Edge tag at pos. 1
(1.e-3): First layer height at pos. 1
(2.e-2): Total height of all layers at pos. 1
(20): Edge tag at pos. 2
(2.e-3): First layer height at pos. 2
(10.e-2): Total height of all layers at pos. 2
(5): Number of layers
(1): Boundary layer Mixed topology (1 for triangles and quads)
(0): Boundary layer blending. 0 for no BL blending
(0): Boundary Layer propagation. 0 for no propogation
(0.1): mesh size on the surface (This value is in the second line)

== Example 8: Global BL attributes ==

These can be set globally as follows. Only 1 attribute can be set at a time.

-1 7 attribute_type
value

The above lines can be divided as below:
(-1) (7) (attribute_type)
(value)

(-1): Entity dimension. -1 for setting global attributes
(7): for setting BL global attribute
(attribute_type): type of BL attribute you want to set. It can be one of the following:
1: smoothing distance
2: layer edge aspect ratio
3: exposed aspect ratio (opposite of aspect ratio, look at the documentation MS_minExposedAspectRatio for more info)
(value): value for the above attribute

.

BLMesher

2012-05-04T07:41:05Z

Chitak: /* Example 8: Global BL attributes */

2011-11-21T00:33:04Z

Chitak: Created page with "How to create the mesh using script"

How to create the mesh using script