BMPRegion Command - Revision history

Nairnj: /* Intensity Command */

2023-10-21T20:35:12Z

Intensity Command

← Older revision		Revision as of 20:35, 21 October 2023
Line 95:		Line 95:
	* <tt>(matID)</tt> is the material ID for a previously defined [[Material Command Block\|material]].		* <tt>(matID)</tt> is the material ID for a previously defined [[Material Command Block\|material]].
	* <tt>(grayMin)</tt> to <tt>(grayMax)</tt> defines a range in gray-scale intensities or text values to map to this material. The numbers must be from 0 (for black) to 255 (for white) and <tt>(grayMin)</tt> must be less than or equal to <tt>(grayMax)</tt>.		* <tt>(grayMin)</tt> to <tt>(grayMax)</tt> defines a range in gray-scale intensities or text values to map to this material. The numbers must be from 0 (for black) to 255 (for white) and <tt>(grayMin)</tt> must be less than or equal to <tt>(grayMax)</tt>.

			If the image (or text) data are at higher resolution than the MPM grid, the mapping will check all pixels intersecting each material point location. The material will be set to the most common material at that location (<i>i.e.</i>, the mode of the data at that location and not the average).

	In scripted files, the optional pairs of arguments, <tt><(prop),(value)></tt> are used to specify other initial conditions for the particles in the intensity range In each pair, the first parameter defines the property and the second parameter defines the value. The properties that are valid for both FEA and MPM input files are:		In scripted files, the optional pairs of arguments, <tt><(prop),(value)></tt> are used to specify other initial conditions for the particles in the intensity range In each pair, the first parameter defines the property and the second parameter defines the value. The properties that are valid for both FEA and MPM input files are:

Nairnj: /* Origin Command */

2023-10-21T20:30:51Z

Origin Command

← Older revision		Revision as of 20:30, 21 October 2023
Line 60:		Line 60:
	== Origin Command ==		== Origin Command ==

	The <tt>Origin</tt> command within a [[#BMPRegion Commands\|<tt>BMPRegion</tt> block]] (or <tt><BMP></tt> element in <tt>XML</tt> files) is used to map the image in the [[#BMPRegion Commands\|associated file]] to the background MPM grid or the existing FEA mesh. In ~~script~~ scripted files, the command is		The <tt>Origin</tt> command within a [[#BMPRegion Commands\|<tt>BMPRegion</tt> block]] (or <tt><BMP></tt> element in <tt>XML</tt> files) is used to map the image in the [[#BMPRegion Commands\|associated file]] to the background MPM grid or the existing FEA mesh. In scripted files, the command is

	Origin (x0),(y0),<(z0)>,<(flip)>		Origin (x0),(y0),<(z0)>,<(flip)>

Nairnj: /* BMPRegion Commands */

2023-10-21T20:30:10Z

BMPRegion Commands

← Older revision		Revision as of 20:30, 21 October 2023
Line 46:		Line 46:
	Inside <tt>BMPRegion</tt> blocks, you include various commands to determine how the pixels are converted into material points. The possible subordinate commands are:		Inside <tt>BMPRegion</tt> blocks, you include various commands to determine how the pixels are converted into material points. The possible subordinate commands are:

	* [[#Origin Command\|<tt>Origin</tt> command]] - used to connected the image coordinates ~~the~~ the MPM grid coordinates.		* [[#Origin Command\|<tt>Origin</tt> command]] - used to connected the image coordinates to the MPM grid coordinates.
	* [[#Intensity Command\|<tt>Intensity</tt> command]] - used to determine conversion of gray scale values in the images into material points or rotation angles		* [[#Intensity Command\|<tt>Intensity</tt> command]] - used to determine conversion of gray scale values in the images into material points or rotation angles
	* [[Setting Material Orientation\|(optional rotation commands)]] - these optional commands provide alternative methods for setting initial material orientation when modeling with [[Material Models\|anisotropic materials]], but are only allowed in MPM input files.		* [[Setting Material Orientation\|(optional rotation commands)]] - these optional commands provide alternative methods for setting initial material orientation when modeling with [[Material Models\|anisotropic materials]], but are only allowed in MPM input files.

Nairnj: /* BMPRegion Commands */

2023-10-21T16:14:36Z

BMPRegion Commands

← Older revision		Revision as of 16:14, 21 October 2023
Line 32:		Line 32:
	where		where

	* <tt>(bmpFilePath)</tt> is the full or relative path name to either a BMP file (with extension <tt>.bmp</tt>) or a plain text file containing tab-delimited or comma-separated values (with extension <tt>.txt</tt>). Most BMP styles are allowed and the file data are converted to 256 levels of gray (or intensity for RGB files) from 0 to 255. A text file's rows and columns translate to locations as if they were pixels in an image file. Floating point numbers are allowed but should be in the range of 0 to 255 and only integral values matter.		* <tt>(bmpFilePath)</tt> is the full or relative path name to either a BMP file (with extension <tt>.bmp</tt>) or a plain text file containing tab-delimited or comma-separated values (with extension <tt>.txt</tt>). Most BMP styles are allowed and the file data are converted to 256 levels of gray (or intensity for RGB files) from 0 to 255. A text file's rows and columns translate to locations as if they were pixels in an image file. Floating point numbers are allowed but all numbers should be in the range of 0 to 255 and only integral values matter.
	* <tt>(width)</tt> and <tt>(height)</tt> specify the physical width and height for the image (not number of pixels), but there are [[#Image Width and Height\|several ways to specify them]].		* <tt>(width)</tt> and <tt>(height)</tt> specify the physical width and height for the image (not number of pixels), but there are [[#Image Width and Height\|several ways to specify them]].
	* <tt>(scheme)</tt> specifies are rotation scheme if BMP (or text) files are provided to determine those angles. The scheme must by "Z" for 2D simulations (all rotations are about the z axis) or can be any one axis (X, Y, or Z), any pair of axes (e.g., "XY"), or any three axis scheme beginning in Z (e.g., "ZYZ"). The <tt>(scheme)</tt> must be followed by one <tt>(anglesPath)</tt> for each axis in the scheme. Because 2D simulations must always be "Z", the <tt>(scheme)</tt> can be omitted and replaced with the one <tt>(anglesPath)</tt>.		* <tt>(scheme)</tt> specifies are rotation scheme if BMP (or text) files are provided to determine those angles. The scheme must by "Z" for 2D simulations (all rotations are about the z axis) or can be any one axis (X, Y, or Z), any pair of axes (e.g., "XY"), or any three axis scheme beginning in Z (e.g., "ZYZ"). The <tt>(scheme)</tt> must be followed by one <tt>(anglesPath)</tt> for each axis in the scheme. Because 2D simulations must always be "Z", the <tt>(scheme)</tt> can be omitted and replaced with the one <tt>(anglesPath)</tt>.

Nairnj at 16:05, 21 October 2023

2023-10-21T16:05:52Z

← Older revision		Revision as of 16:05, 21 October 2023
Line 1:		Line 1:
	An advanced feature of both [[NairnMPM]] and [[NairnFEA]] is that you can digitize objects directly from images.		An advanced feature of both [[NairnMPM]] and [[NairnFEA]] is that you can digitize objects directly from images or data in a text file.

	== Introduction ==		== 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.		An alternative method for creating meshes in [[NairnFEA]] or material points in [[NairnMPM]] to to create them from an image file and data in a text file. An 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. A text file is typically created in other software such as a simple python script. In 2D or axisymmetric calculations, the file data fills in an FEA mesh or adds material points to the grid. in 3D MPM simulations, each file represents one slice of the object in the x-y plane at a fixed value of z. By combining a stack of slices, the file data can create all material points for a complex 3D object.

	== BMPRegion Commands ==		== BMPRegion Commands ==

Nairnj: /* Image Width and Height */

2023-09-21T20:45:58Z

Image Width and Height

← Older revision		Revision as of 20:45, 21 September 2023
Line 52:		Line 52:
	=== Image Width and Height ===		=== Image Width and Height ===

	The <tt>(width)</tt> and <tt>(height)</tt> parameters specify the width and height of the image data, but they can be specified using different styles. The options are:		The <tt>(width)</tt> and <tt>(height)</tt> parameters specify the physical width and height of the image or text data, 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]] (or determined by a [[Units Attribute\|units attribute]] in <tt>XML</tt> files). They need not match the aspect ratio of actual data, but if they differ the image will be rescaled.		# Give both as positive numbers - if both numbers are provided and are positive, they give width and height of the image or data in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]] (or determined by a [[Units Attribute\|units attribute]] in <tt>XML</tt> files). They need not match the aspect ratio of actual data, but if they differ the image will be rescaled.
	# Use a negative number - if either <tt>(width)</tt> or <tt>(height)</tt> is negative, the absolute value is taken as the number of [[ConsistentUnits Command#Legacy and Consistent Units\|length units]] per pixel (or other units per pixel as determined by a [[Units Attribute\|units attribute]] in <tt>XML</tt> files). The total width or height is calculated from the number of pixels in the BMP image.		# Use a negative number - if either <tt>(width)</tt> or <tt>(height)</tt> is negative, the absolute value is taken as the number of [[ConsistentUnits Command#Legacy and Consistent Units\|length units]] per pixel, row, or column (or other units per pixel as determined by a [[Units Attribute\|units attribute]] in <tt>XML</tt> files). The total width or height is calculated from the number of pixels in the BMP image or rows or columns for text files.
	# Give only one dimension - if only <tt>(width)</tt> or only <tt>(height)</tt> are given, the entered parameter gives that dimension of the image in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]], if positive, or [[ConsistentUnits Command#Legacy and Consistent Units\|length units]] per pixel, if negative (or other units as determined by a [[Units Attribute\|units attribute]] in <tt>XML</tt> files). The other dimension is calculated from the aspect ratio of the BMP data. To specify only <tt>(height)</tt> in scripted files, the <tt>(width)</tt> parameter has to be more negative than -1e8. To specify only <tt>(width)</tt> in scripted files that are using the optional <tt>(anglesPath)</tt> parameter, the <tt>(height)</tt> parameter has to be more negative than -1e8.		# Give only one dimension - if only <tt>(width)</tt> or only <tt>(height)</tt> are given, the entered parameter gives that dimension of the image or text data in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]], if positive, or [[ConsistentUnits Command#Legacy and Consistent Units\|length units]] per pixel (or row or column), if negative (or other units as determined by a [[Units Attribute\|units attribute]] in <tt>XML</tt> files). The other dimension is calculated from the aspect ratio of the BMP to trxt file data. To specify only <tt>(height)</tt> in scripted files, the <tt>(width)</tt> parameter has to be more negative than -1e8. To specify only <tt>(width)</tt> in scripted files that are using the optional <tt>(anglesPath)</tt> parameter, the <tt>(height)</tt> parameter has to be more negative than -1e8.

	== Origin Command ==		== Origin Command ==

Nairnj: /* Mapping Angles */

2023-09-21T20:41:38Z

Mapping Angles

← Older revision		Revision as of 20:41, 21 September 2023
Line 125:		Line 125:
	=== Mapping Angles ===		=== Mapping Angles ===

	When the first argument to the <tt>Intensity</tt> command is "angles" (or actually any text that is not a material ID), then that command is used to map gray-~~scales~~ in an [[#BMPRegion Commands\|associated angles mask file]] to material angle for elements in an FEA mesh or material points in an MPM model. This use of the <tt>Intensity</tt> command only makes sense when optional <tt>(anglesPath)</tt>s are used in the [[#BMPRegion Commands\|<tt>BMPRegion</tt> command]]. Angle mapping for more than one <tt>(anglesPath)</tt> file in 3D simulations can be done by using more than one <tt>Intensity</tt> command. Each extra command maps the corresponding <tt>(anglePath)</tt> file in order provided. If there are fewer <tt>Intensity</tt> commands then <tt>(anglesPath)</tt> files, the remaining files will use the map set by the last <tt>Intensity</tt> command.		When the first argument to the <tt>Intensity</tt> command is "angles" (or actually any text that is not a material ID), then that command is used to map gray-scale or text values in an [[#BMPRegion Commands\|associated angles mask file]] to material angle for elements in an FEA mesh or material points in an MPM model. This use of the <tt>Intensity</tt> command only makes sense when optional <tt>(anglesPath)</tt>s are used in the [[#BMPRegion Commands\|<tt>BMPRegion</tt> command]]. Angle mapping for more than one <tt>(anglesPath)</tt> file in 3D simulations can be done by using more than one <tt>Intensity</tt> command. Each extra command maps the corresponding <tt>(anglePath)</tt> file in order provided. If there are fewer <tt>Intensity</tt> commands then <tt>(anglesPath)</tt> files, the remaining files will use the map set by the last <tt>Intensity</tt> command.

	In scripted files, the angle mapping form of the command is:		In scripted files, the angle mapping form of the command is:
Line 138:		Line 138:


	<math>\theta = ~~(angle1) +~~ {(~~angle2~~)-~~(angle1)~~\over (gray2)-(gray1)} ~~\bigl~~(g-(gray1)\~~bigr~~)</math>		<math>\theta = {(gray2)-g\over (gray2)-(gray1)}(angle1) + {g-(gray1)\over (gray2)-(gray1)}(angle2) </math>

	This interpolation applies to all gray scale values, including those outside the range <tt>(gray1)</tt> to <tt>(gray2)</tt>.		This interpolation applies to all gray scale values, including those outside the range <tt>(gray1)</tt> to <tt>(gray2)</tt>.

Nairnj: /* BMPRegion Commands */

2023-09-21T20:24:29Z

BMPRegion Commands

← Older revision		Revision as of 20:24, 21 September 2023
Line 35:		Line 35:
	* <tt>(width)</tt> and <tt>(height)</tt> specify the physical width and height for the image (not number of pixels), but there are [[#Image Width and Height\|several ways to specify them]].		* <tt>(width)</tt> and <tt>(height)</tt> specify the physical width and height for the image (not number of pixels), but there are [[#Image Width and Height\|several ways to specify them]].
	* <tt>(scheme)</tt> specifies are rotation scheme if BMP (or text) files are provided to determine those angles. The scheme must by "Z" for 2D simulations (all rotations are about the z axis) or can be any one axis (X, Y, or Z), any pair of axes (e.g., "XY"), or any three axis scheme beginning in Z (e.g., "ZYZ"). The <tt>(scheme)</tt> must be followed by one <tt>(anglesPath)</tt> for each axis in the scheme. Because 2D simulations must always be "Z", the <tt>(scheme)</tt> can be omitted and replaced with the one <tt>(anglesPath)</tt>.		* <tt>(scheme)</tt> specifies are rotation scheme if BMP (or text) files are provided to determine those angles. The scheme must by "Z" for 2D simulations (all rotations are about the z axis) or can be any one axis (X, Y, or Z), any pair of axes (e.g., "XY"), or any three axis scheme beginning in Z (e.g., "ZYZ"). The <tt>(scheme)</tt> must be followed by one <tt>(anglesPath)</tt> for each axis in the scheme. Because 2D simulations must always be "Z", the <tt>(scheme)</tt> can be omitted and replaced with the one <tt>(anglesPath)</tt>.
	* <tt>(anglesPath)</tt>,... are 1 to 3 (one for each axis defined in <tt>(scheme)</tt>) optional full or relative path names to BMP or text files whose intensities or values determine a material angle for rotation about the corresponding axis in <tt>(scheme)</tt> (or "Z" axis if <tt>(scheme)</tt> is omitted). The angles can set Euler angles to orient the material axes at the start of simulations with anisotropic materials. The file must be exactly the same size (horizontal and vertical pixels or rows and columns of text) as the image file in <tt>(filePath)</tt>. The gray scale or text values are mapped to angles by using [[#Mapping Angles\|<tt>Intensity</tt> commands]]. The relation of axes to Euler angles determines the initial [[Setting Material Orientation#Rotation Matrix\|rotation matrix]] for each particle.		* <tt>(anglesPath)</tt>,... are 1 to 3 (one for each axis defined in <tt>(scheme)</tt>) optional full or relative path names to BMP or text files whose intensities or values determine a material angle for rotation about the corresponding axis in <tt>(scheme)</tt> (or "Z" axis if <tt>(scheme)</tt> is omitted). The angles can set Euler angles to orient the material axes at the start of simulations with anisotropic materials. The file data must be exactly the same size (horizontal and vertical pixels or rows and columns of text) as the image file in <tt>(filePath)</tt>. The gray scale or text values are mapped to angles by using [[#Mapping Angles\|<tt>Intensity</tt> commands]]. The relation of axes to Euler angles determines the initial [[Setting Material Orientation#Rotation Matrix\|rotation matrix]] for each particle.
	* <tt>(totalNumber)</tt> is to optionally set the number of material points in each element of the background grid for this region to differ from the default setting.[[#Notes\|<sup>1</sup>]] (it must be square or cube of points per side in 2D or 3D, respectively). This option is for <tt>XML</tt> files only. Use the "res" option below to pick points per element in scripted file.		* <tt>(totalNumber)</tt> is to optionally set the number of material points in each element of the background grid for this region to differ from the default setting.[[#Notes\|<sup>1</sup>]] (it must be square or cube of points per side in 2D or 3D, respectively). This option is for <tt>XML</tt> files only. Use the "res" option below to pick points per element in scripted file.

Nairnj: /* BMPRegion Commands */

2023-09-21T20:22:38Z

BMPRegion Commands

← Older revision		Revision as of 20:22, 21 September 2023
Line 34:		Line 34:
	* <tt>(bmpFilePath)</tt> is the full or relative path name to either a BMP file (with extension <tt>.bmp</tt>) or a plain text file containing tab-delimited or comma-separated values (with extension <tt>.txt</tt>). Most BMP styles are allowed and the file data are converted to 256 levels of gray (or intensity for RGB files) from 0 to 255. A text file's rows and columns translate to locations as if they were pixels in an image file. Floating point numbers are allowed but should be in the range of 0 to 255 and only integral values matter.		* <tt>(bmpFilePath)</tt> is the full or relative path name to either a BMP file (with extension <tt>.bmp</tt>) or a plain text file containing tab-delimited or comma-separated values (with extension <tt>.txt</tt>). Most BMP styles are allowed and the file data are converted to 256 levels of gray (or intensity for RGB files) from 0 to 255. A text file's rows and columns translate to locations as if they were pixels in an image file. Floating point numbers are allowed but should be in the range of 0 to 255 and only integral values matter.
	* <tt>(width)</tt> and <tt>(height)</tt> specify the physical width and height for the image (not number of pixels), but there are [[#Image Width and Height\|several ways to specify them]].		* <tt>(width)</tt> and <tt>(height)</tt> specify the physical width and height for the image (not number of pixels), but there are [[#Image Width and Height\|several ways to specify them]].
	* <tt>(scheme)</tt> specifies are rotation scheme if BMP files are provided to determine those angles. The scheme must by "Z" for 2D simulations (all rotations are about the z axis) or can be any one axis (X, Y, or Z), any pair of axes (e.g., "XY"), or any three axis scheme beginning in Z (e.g., "ZYZ"). The <tt>(scheme)</tt> must be followed by one <tt>(anglesPath)</tt> for each axis in the scheme. Because 2D simulations must always be "Z", the <tt>(scheme)</tt> can be omitted and replaced with the one <tt>(anglesPath)</tt>.		* <tt>(scheme)</tt> specifies are rotation scheme if BMP (or text) files are provided to determine those angles. The scheme must by "Z" for 2D simulations (all rotations are about the z axis) or can be any one axis (X, Y, or Z), any pair of axes (e.g., "XY"), or any three axis scheme beginning in Z (e.g., "ZYZ"). The <tt>(scheme)</tt> must be followed by one <tt>(anglesPath)</tt> for each axis in the scheme. Because 2D simulations must always be "Z", the <tt>(scheme)</tt> can be omitted and replaced with the one <tt>(anglesPath)</tt>.
	* <tt>(anglesPath)</tt>,... are 1 to 3 (one for each axis defined in <tt>(scheme)</tt>) optional full or relative path names to BMP files whose intensities or values determine a material angle for rotation about the corresponding axis in <tt>(scheme)</tt> (or "Z" axis if <tt>(scheme)</tt> is omitted). The angles can set Euler angles to orient the material axes at the start of simulations with anisotropic materials. The file must be exactly the same size (horizontal and vertical pixels or rows and columns of text) as the image file in <tt>(filePath)</tt>. The gray scale or text values are mapped to angles by using [[#Mapping Angles\|<tt>Intensity</tt> commands]]. The relation of axes to Euler angles determines the initial [[Setting Material Orientation#Rotation Matrix\|rotation matrix]] for each particle.		* <tt>(anglesPath)</tt>,... are 1 to 3 (one for each axis defined in <tt>(scheme)</tt>) optional full or relative path names to BMP or text files whose intensities or values determine a material angle for rotation about the corresponding axis in <tt>(scheme)</tt> (or "Z" axis if <tt>(scheme)</tt> is omitted). The angles can set Euler angles to orient the material axes at the start of simulations with anisotropic materials. The file must be exactly the same size (horizontal and vertical pixels or rows and columns of text) as the image file in <tt>(filePath)</tt>. The gray scale or text values are mapped to angles by using [[#Mapping Angles\|<tt>Intensity</tt> commands]]. The relation of axes to Euler angles determines the initial [[Setting Material Orientation#Rotation Matrix\|rotation matrix]] for each particle.
	* <tt>(totalNumber)</tt> is to optionally set the number of material points in each element of the background grid for this region to differ from the default setting.[[#Notes\|<sup>1</sup>]] (it must be square or cube of points per side in 2D or 3D, respectively). This option is for <tt>XML</tt> files only. Use the "res" option below to pick points per element in scripted file.		* <tt>(totalNumber)</tt> is to optionally set the number of material points in each element of the background grid for this region to differ from the default setting.[[#Notes\|<sup>1</sup>]] (it must be square or cube of points per side in 2D or 3D, respectively). This option is for <tt>XML</tt> files only. Use the "res" option below to pick points per element in scripted file.

Nairnj: /* BMPRegion Commands */

2023-09-21T20:21:10Z

BMPRegion Commands

← Older revision		Revision as of 20:21, 21 September 2023
Line 33:		Line 33:

	* <tt>(bmpFilePath)</tt> is the full or relative path name to either a BMP file (with extension <tt>.bmp</tt>) or a plain text file containing tab-delimited or comma-separated values (with extension <tt>.txt</tt>). Most BMP styles are allowed and the file data are converted to 256 levels of gray (or intensity for RGB files) from 0 to 255. A text file's rows and columns translate to locations as if they were pixels in an image file. Floating point numbers are allowed but should be in the range of 0 to 255 and only integral values matter.		* <tt>(bmpFilePath)</tt> is the full or relative path name to either a BMP file (with extension <tt>.bmp</tt>) or a plain text file containing tab-delimited or comma-separated values (with extension <tt>.txt</tt>). Most BMP styles are allowed and the file data are converted to 256 levels of gray (or intensity for RGB files) from 0 to 255. A text file's rows and columns translate to locations as if they were pixels in an image file. Floating point numbers are allowed but should be in the range of 0 to 255 and only integral values matter.
	* <tt>(width)</tt> and <tt>(height)</tt> specify the width and height for the image, but there are [[#Image Width and Height\|several ways to specify them]].		* <tt>(width)</tt> and <tt>(height)</tt> specify the physical width and height for the image (not number of pixels), but there are [[#Image Width and Height\|several ways to specify them]].
	* <tt>(scheme)</tt> specifies are rotation scheme if BMP files are provided to determine those angles. The scheme must by "Z" for 2D simulations (all rotations are about the z axis) or can be any one axis (X, Y, or Z), any pair of axes (e.g., "XY"), or any three axis scheme beginning in Z (e.g., "ZYZ"). The <tt>(scheme)</tt> must be followed by one <tt>(anglesPath)</tt> for each axis in the scheme. Because 2D simulations must always be "Z", the <tt>(scheme)</tt> can be omitted and replaced with the one <tt>(anglesPath)</tt>.		* <tt>(scheme)</tt> specifies are rotation scheme if BMP files are provided to determine those angles. The scheme must by "Z" for 2D simulations (all rotations are about the z axis) or can be any one axis (X, Y, or Z), any pair of axes (e.g., "XY"), or any three axis scheme beginning in Z (e.g., "ZYZ"). The <tt>(scheme)</tt> must be followed by one <tt>(anglesPath)</tt> for each axis in the scheme. Because 2D simulations must always be "Z", the <tt>(scheme)</tt> can be omitted and replaced with the one <tt>(anglesPath)</tt>.
	* <tt>(anglesPath)</tt>,... are 1 to 3 (one for each axis defined in <tt>(scheme)</tt>) optional full or relative path names to BMP files whose intensities or values determine a material angle for rotation about the corresponding axis in <tt>(scheme)</tt> (or "Z" axis if <tt>(scheme)</tt> is omitted). The angles can set Euler angles to orient the material axes at the start of simulations with anisotropic materials. The file must be exactly the same size (horizontal and vertical pixels or rows and columns of text) as the image file in <tt>(filePath)</tt>. The gray scale or text values are mapped to angles by using [[#Mapping Angles\|<tt>Intensity</tt> commands]]. The relation of axes to Euler angles determines the initial [[Setting Material Orientation#Rotation Matrix\|rotation matrix]] for each particle.		* <tt>(anglesPath)</tt>,... are 1 to 3 (one for each axis defined in <tt>(scheme)</tt>) optional full or relative path names to BMP files whose intensities or values determine a material angle for rotation about the corresponding axis in <tt>(scheme)</tt> (or "Z" axis if <tt>(scheme)</tt> is omitted). The angles can set Euler angles to orient the material axes at the start of simulations with anisotropic materials. The file must be exactly the same size (horizontal and vertical pixels or rows and columns of text) as the image file in <tt>(filePath)</tt>. The gray scale or text values are mapped to angles by using [[#Mapping Angles\|<tt>Intensity</tt> commands]]. The relation of axes to Euler angles determines the initial [[Setting Material Orientation#Rotation Matrix\|rotation matrix]] for each particle.