Difference between revisions of "BMPRegion Command"
Line 61: | Line 61: | ||
where | where | ||
*<tt>( | *<tt>(xO)</tt>, <tt>(yO)</tt>, and <tt>(zO)</tt> give the (x,y,z) coordinate for the origin of the image when mapped to the grid or mesh in mm (or determined by a [[Units Attribute|units attribute]] in <tt>XML</tt> files). The <tt>(zO)</tt> coordinate is only needed for 3D calculations and is not allowed in FEA input files. | ||
* If the optional <tt>(flip)</tt> is "yes", the origin will move to the upper-left corner of the image with y increasing in the downward direction and x increasing to the right. This change will flip the image in the y direction in the analysis compared to the image graphics. | |||
If optional | |||
== Intensity Command == | == Intensity Command == |
Revision as of 10:42, 1 January 2014
An advanced feature of both NairnMPM and NairnFEA is that you can digitize objects directly from images.
Introduction
An alternative method for creating meshes in NairnFEA or material points in NairnMPM to to create them from an image file. The image file can be one you draw in a CAD program or can be a photo of object. The later options lets you create realistic numerical models of complex objects in a single command. In 2D or axisymmetric calculations, the image fills in an FEA mesh or adds material points to the grid. in 3D MPM simulations, the image represents one slice of the object in the x-y plane at a fixed value of z. By combining a stack of slices, those images can create all material points for a complex 3D object.
BMPRegion Commands
The command to digitize images is the same for both FEA and MPM input files. In scripted files, an image is converted into material points using:
BMPRegion (bmpPath),(width),<(height)>,<(anglesPath)> Origin (xO),(yO),<(zO>,<(flip)> Intensity (matID),(grayMin),(grayMax),<(prop),(value)>,... . . . Intensity "angles",(gray1),(gray2),(angle1),(angle2) (optional rotation command - MPM only) EndRegion
In XML files, the command block is (must be within the single <MaterialPoints> element for MPM input files):
<BMP name="(bmpPath)" width="(width)" height="(height)" angles="(anglesPath)"> <Origin x="(xO)" y="(yO)" z="(zO)" flipped="(flip)"/> <Intensity mat="(matID)" imin="(gramMin)" imax="(grayMax)"> (property command options) </Intensity> . . . <Intensity imin="(gray1)" imax="(gray2)" minAngle="(angle1)" maxAngle="(angle2)"/> (optional rotation commands - MPM only) </BMP>
where
- (bmpPath) is the full or relative path name to the BMP file. The file must be an uncompressed, gray-scale, BMP file with 8 or less bits per pixel. The most useful is an 8-bit file with 256 levels of gray.
- (width) and (height) specify the width and height for the image, but there are several ways to specify them.
- (anglesPath) is an optional full or relative path name to a mask BMP file whose intensities determine the material angle for rotation about eh z axis when setting anisotropic material points. The file must be an uncompressed, gray-scale, BMP file with 8 or less bits per pixel. The file must be exactly the same size (horizontal and vertical pixels) as the image file in (bmpPath).
Inside BMPRegion block, you include various commands to determine how the pixels are converted into material points. The possible subordinate commands are:
- Origin command - used to connected the image coordinates the the MPM grid coordinates.
- Intensity command - used to determine conversion of gray scale values in the images into material points or rotation angles
- (optional rotation commands) - these optional commands provide alternative methods for setting initial material orientation when modeling with anisotropic materials, but are only allowed in MPM input files.
Image Width and Height
The (width) and (height) parameters specify the width and height of the image, but they can be specified using different styles. The options are:
- Give both as positive numbers - if both numbers are provided and are positive, they give width and height of the image in mm (or determined by a units attribute in XML files). They need not match the aspect ratio of actual image, but if they differ the image will be scaled.
- Use a negative number - if either (width) or (height) is negative, the absolute value is taken as the number of mm per pixel (or other units per pixel as determined by a units attribute in XML files). The total width or height is calculated from the number of pixels in the BMP image.
- Give only one dimension - if only (width) or only (height) are given, the entered parameter gives that dimension of the image in mm, if positive, or mm per pixel, if negative (or other units as determined by a units attribute in XML files). The other dimension is calculated from the aspect ratio of the BMP file. To specify only (height) in scripted files, the (width) parameter has to be more negative than -1e8. To specify only (width) in scripted files that are using the optional (anglesPath) parameter, the (height) parameter has to be more negative than -1e8.
Origin Command
The Origin command within a BMPRegion block (or <BMP> element in XML files) is used to map the image in the associated BMP File to the background MPM grid or the existing FEA mesh. In script scripted files, the command is
Origin (x0),(y0),<(z0)>,<(flip)>
In XML files, the command is:
<Origin x="(xO)" y="(yO)" z="(zO)" flipped="(flip)"/>
where
- (xO), (yO), and (zO) give the (x,y,z) coordinate for the origin of the image when mapped to the grid or mesh in mm (or determined by a units attribute in XML files). The (zO) coordinate is only needed for 3D calculations and is not allowed in FEA input files.
- If the optional (flip) is "yes", the origin will move to the upper-left corner of the image with y increasing in the downward direction and x increasing to the right. This change will flip the image in the y direction in the analysis compared to the image graphics.