******** session06 ********
Q: Host is AFLR distributed? Is it freely available?
A: We have permission to distribute AFLR only in binary form as part of ESP PreBuilt.

Q: How do I use AFLR if I build ESP from source?
A: Download a PreBuilt version of ESP and copy ESP118/EngSketchPad/lib/aflr*AIM.* to $ESP_ROOT/lib

Q: Couldn’t you set up your script to automagically read the .egads files if they existed?
A: Yes, you could add logic to the python script to querry if the .egads files exist.

Q: Is scaleFactor similar to capsMeshLength, but only for one Body?
A: The Mesh_Sizing scaleFactor applies the scaling to Faces with the corresponding capsGroup value

Q: What is the connection between “components” and capsGroup?
A: None. The notion of "components" is an AFLR4 feature. Components must be specified with the integer valued Face attribute AFLR4_Cmp_ID
    
Q: If you specify Mesh_Sizing on a Face, does it override the global?
A: Yes.

Q: Is there some sort of inheritance when specifying meshing properties? Body->face->edge->node?
A: AFLR4 only has Face attributes to guide the meshing.

Q: What is curv_factor?
A: This controls the mesh resolution in high curvature regions. See the AFLR4 AIM documentation for more details.

Q: It would be nice to have a succinct list of allowable attributes on bodys, faces, and edges
A: This is listed in the AFLR4 AIM documentation under "AIM Attributes"

Q: Does the "_UG3_GBC" portion of the attribute name effect the farfield mesh?
A: "_UG3_GBS" is simply part of the AFLR naming convention. You have to set he full string $FARFIELD_UG3_GBC

Q: Does the AFLR AIM documentation have a list of available mesh formats it can generate?
A: Yes, but these are only for visualization. These meshes are not used by other AIMs for analysis.