|
Mapping the Domain
|
Previous Top Next |
| · | A REGION specification begins with the statement REGION <number> (or REGION "name") and all loops following the header are included in the region.
|
| · | REGIONs occurring later in the script overlay and cover up parts of earlier REGIONs.
|
| · | The first REGION should contain the entire domain. This is an unenforced convention that makes the attachment of boundary conditions easier.
|
| · | A rectangular region, for example, is made up of four line segments:
|
| START(x1,y1)
|
| LINE TO(x2,y1)
|
| TO (x2,y2)
|
| TO (x1,y2)
|
| TO CLOSE
|
|
|
| (Of course, any quadrilateral figure can be made with the same structure, merely by changing the coordinates. And any polygonal figure can be constructed by adding more points.)
|
| · | Arcs can be built in several ways, the simplest of which is by specifying a center and an angle:
|
| START(r,0)
|
| ARC(CENTER=0,0) ANGLE=360
|
|
|
| · | Arcs can also be built by specifying a center and an end point:
|
|
|
| START(r,0)
|
| ARC(CENTER=0,0) TO (0,r) { a 90 degree arc }
|
|
|
| An elliptical arc will be built if the distance from the center to the endpoint is different than the distance from the center to the beginning point. The axes of the ellipse will extend along the horizontal and vertical coordinate axes; you cannot build a tilted ellipse.
|
| · | Loops can be named for use in later references, as in:
|
|
|
| START "Name" (
)
|
|
|
| BOUNDARIES
|
| REGION 1
|
| <closed loops around the domain>
|
| REGION 2
|
| <closed loops around overlays of the second material>
|
|
|
|
|