XMLData Command - Revision history

Chadh at 23:13, 25 January 2019

2019-01-25T23:13:14Z

Nairnj at 17:48, 5 February 2014

2014-02-05T17:48:35Z

← Older revision		Revision as of 17:48, 5 February 2014
Line 32:		Line 32:
	The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.		The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.

	<font color="red">Caution:</font> - all lines are inserted verbatim. If the block contains [[Expression Syntax\|expressions]], they will not be evaluated, but just inserted as the expression text. You can avoid this limitation, however, by using an [[Expression Syntax\|expression]] to define an [[Entity Command\|entity]] and then using that entity in the verbatim <tt>XML</tt> code. Similarly, if you comment out a line using the [[Command Line Syntax#Comment Line\|scripting language comment method]], ~~the~~ line will still be inserted with the verbatim <tt>XML</tt>. If you want to ~~add real comments (or~~ comment ~~out lines) in~~ the <tt>XML</tt> code, you can use the <tt>XML</tt> comment method of <tt><!-- an XML comment --></tt> instead.		<font color="red">Caution:</font> - all lines are inserted verbatim. If the block contains [[Expression Syntax\|expressions]], they will not be evaluated, but just inserted as the expression text. You can avoid this limitation, however, by using an [[Expression Syntax\|expression]] to define an [[Entity Command\|entity]] and then using that entity in the verbatim <tt>XML</tt> code. Similarly, if you comment out a line using the [[Command Line Syntax#Comment Line\|scripting language comment method]], that line will still be inserted with the verbatim <tt>XML</tt>. If you want to comment the <tt>XML</tt> code (or comment out lines in that code), you can use the <tt>XML</tt> comment method of <tt><!-- an XML comment --></tt> instead.

	== Notes ==		== Notes ==

Nairnj at 17:46, 5 February 2014

2014-02-05T17:46:04Z

← Older revision		Revision as of 17:46, 5 February 2014
Line 32:		Line 32:
	The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.		The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.

	<font color="red">Caution:</font> - all lines are inserted verbatim. If the block contains [[Expression Syntax\|expressions]], they will not be evaluated, but just inserted as the expression text. You can avoid this limitation, however, by using an [[Expression Syntax\|expression]] to define an [[Entity Command\|entity]] and then using that entity in the verbatim XML code. Similarly, if you comment out a line using the scripting language comment method, the line will ~~sill~~ be inserted with the verbatim XML. If you want to add real comments (or comment out lines in the XML code), you can use the XML comment method of <tt><!-- an XML comment --></tt> ~~within the verbatim <tt>XML</tt> code~~.		<font color="red">Caution:</font> - all lines are inserted verbatim. If the block contains [[Expression Syntax\|expressions]], they will not be evaluated, but just inserted as the expression text. You can avoid this limitation, however, by using an [[Expression Syntax\|expression]] to define an [[Entity Command\|entity]] and then using that entity in the verbatim <tt>XML</tt> code. Similarly, if you comment out a line using the [[Command Line Syntax#Comment Line\|scripting language comment method]], the line will still be inserted with the verbatim <tt>XML</tt>. If you want to add real comments (or comment out lines) in the <tt>XML</tt> code, you can use the <tt>XML</tt> comment method of <tt><!-- an XML comment --></tt> instead.

	== Notes ==		== Notes ==

Nairnj at 17:43, 5 February 2014

2014-02-05T17:43:40Z

← Older revision		Revision as of 17:43, 5 February 2014
Line 30:		Line 30:
	* <tt>(matid)</tt> specifies a material ID, but is only used when <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])		* <tt>(matid)</tt> specifies a material ID, but is only used when <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])

	The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section. ~~Note that~~ all lines are inserted verbatim. In the block contains expressions, they will not be evaluated, but just inserted as ~~that~~ text. You can avoid this limitation, however, by using an expression to define an ~~enetity~~ and then using the ~~entity~~ in the verbatim XML code.		The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.

			<font color="red">Caution:</font> - all lines are inserted verbatim. If the block contains [[Expression Syntax\|expressions]], they will not be evaluated, but just inserted as the expression text. You can avoid this limitation, however, by using an [[Expression Syntax\|expression]] to define an [[Entity Command\|entity]] and then using that entity in the verbatim XML code. Similarly, if you comment out a line using the scripting language comment method, the line will sill be inserted with the verbatim XML. If you want to add real comments (or comment out lines in the XML code), you can use the XML comment method of <tt><!-- an XML comment --></tt> within the verbatim <tt>XML</tt> code.

	== Notes ==		== Notes ==

Nairnj at 17:38, 5 February 2014

2014-02-05T17:38:13Z

← Older revision		Revision as of 17:38, 5 February 2014
Line 30:		Line 30:
	* <tt>(matid)</tt> specifies a material ID, but is only used when <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])		* <tt>(matid)</tt> specifies a material ID, but is only used when <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])

	The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.		The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section. Note that all lines are inserted verbatim. In the block contains expressions, they will not be evaluated, but just inserted as that text. You can avoid this limitation, however, by using an expression to define an enetity and then using the entity in the verbatim XML code.

	== Notes ==		== Notes ==

Nairnj: /* XMLData Command */

2014-01-21T06:38:38Z

XMLData Command

← Older revision		Revision as of 06:38, 21 January 2014
Line 28:		Line 28:
	** "CustomTasks" to insert at the end of the <tt><CustomTasks></tt> section.		** "CustomTasks" to insert at the end of the <tt><CustomTasks></tt> section.
	** "End" to insert at the end of all other <tt>XML</tt> data.		** "End" to insert at the end of all other <tt>XML</tt> data.
	* <tt>(id)</tt> specifies a material ID, but is only used when <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])		* <tt>(matid)</tt> specifies a material ID, but is only used when <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])

	The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.		The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.

Nairnj: /* Notes */

2013-12-26T00:26:45Z

Notes

← Older revision		Revision as of 00:26, 26 December 2013
Line 41:		Line 41:
	</Material>		</Material>
	</pre>		</pre>
	where the property commands set the material properties. The second <tt>(matid)</tt> parameter to the <tt>XMLData</tt> command must be provided and it must have a unique [[Material Command Block\|material ID]] (which can be used like regular material IDs). This insertion option is provided to work with materials in the code engines that are not yet supported by [[NairnFEAMPM]] or [[NairnFEAMPMViz]].		where the property commands set the material properties. The second <tt>(matid)</tt> parameter to the <tt>XMLData</tt> command must be provided and it must have a unique [[Material Command Block\|material ID]] (which can be used like regular material IDs). This insertion option is provided to work with [[Material Models\|materials]] in the code engines that are not yet supported by [[NairnFEAMPM]] or [[NairnFEAMPMViz]], such a new [[Material Models\|materials]] currently in development.

	<li>For "MaterialPoints", "Materials", "GridBCs", and "ParticleBCs", the data will be inserted when the <tt>XMLData</tt> command is used. This approach allows you to intersperse <tt>XML</tt> features with scripted features in these sections. For other sections the <tt>XML</tt> is inserted at the end each section.		<li>For "MaterialPoints", "Materials", "GridBCs", and "ParticleBCs", the data will be inserted when the <tt>XMLData</tt> command is used. This approach allows you to intersperse <tt>XML</tt> features with scripted features in these sections. For other sections the <tt>XML</tt> is inserted at the end each section.

Nairnj: /* XMLData Command */

2013-12-26T00:25:33Z

XMLData Command

← Older revision		Revision as of 00:25, 26 December 2013
Line 28:		Line 28:
	** "CustomTasks" to insert at the end of the <tt><CustomTasks></tt> section.		** "CustomTasks" to insert at the end of the <tt><CustomTasks></tt> section.
	** "End" to insert at the end of all other <tt>XML</tt> data.		** "End" to insert at the end of all other <tt>XML</tt> data.
	* <tt>(id)</tt> specifies a material ID ~~whenever~~ <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])		* <tt>(id)</tt> specifies a material ID, but is only used when <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])

	The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.		The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multuple <tt>XMLData</tt> blocks for each section and subsquent blocks will be appended to previous blocks for each section.

Nairnj: /* XMLData Command */

2013-12-25T21:44:00Z

XMLData Command

← Older revision		Revision as of 21:44, 25 December 2013
Line 26:		Line 26:
	** "ParticleBCs" to insert in the <tt><ParticleBCs></tt> section. it may be interspersed with other particle boundary conditions (MPM Only).		** "ParticleBCs" to insert in the <tt><ParticleBCs></tt> section. it may be interspersed with other particle boundary conditions (MPM Only).
	** "Thermal" to insert at the end of the <tt><Thermal></tt> section.		** "Thermal" to insert at the end of the <tt><Thermal></tt> section.
			** "CustomTasks" to insert at the end of the <tt><CustomTasks></tt> section.
	** "End" to insert at the end of all other <tt>XML</tt> data.		** "End" to insert at the end of all other <tt>XML</tt> data.
	* <tt>(id)</tt> specifies a material ID whenever <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])		* <tt>(id)</tt> specifies a material ID whenever <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])

Nairnj: /* Notes */

2013-09-13T00:37:30Z

Notes

← Older revision		Revision as of 00:37, 13 September 2013
Line 43:		Line 43:

	<li>For "MaterialPoints", "Materials", "GridBCs", and "ParticleBCs", the data will be inserted when the <tt>XMLData</tt> command is used. This approach allows you to intersperse <tt>XML</tt> features with scripted features in these sections. For other sections the <tt>XML</tt> is inserted at the end each section.		<li>For "MaterialPoints", "Materials", "GridBCs", and "ParticleBCs", the data will be inserted when the <tt>XMLData</tt> command is used. This approach allows you to intersperse <tt>XML</tt> features with scripted features in these sections. For other sections the <tt>XML</tt> is inserted at the end each section.

			<li>Another command to insert raw <tt>XML</tt> data is the [[Entity Command]].

	</ol>		</ol>

← Older revision		Revision as of 23:13, 25 January 2019
Line 22:		Line 22:
	** "Mesh" to insert at the end of the <tt><Mesh></tt> section.		** "Mesh" to insert at the end of the <tt><Mesh></tt> section.
	** "MaterialPoints" to insert in the <tt><MaterialPoints></tt> definition section of MPM files or with shape commands in FEA files to define the mesh. It may be interspersed with Region, Hole, and BMPRegion commands.		** "MaterialPoints" to insert in the <tt><MaterialPoints></tt> definition section of MPM files or with shape commands in FEA files to define the mesh. It may be interspersed with Region, Hole, and BMPRegion commands.
	** "~~Materials~~" to insert a custom material along with other materials. Each insertion for this section must define a single [[Material Models\|material]] (see [[#Notes\|below]])		** "Material" to insert a custom material along with other materials. Each insertion for this section must define a single [[Material Models\|material]] (see [[#Notes\|below]])
	** "GridBCs" to insert in the <tt><GridBCs></tt> section. it may be interspersed with other grid boundary conditions.		** "GridBCs" to insert in the <tt><GridBCs></tt> section. it may be interspersed with other grid boundary conditions.
	** "ParticleBCs" to insert in the <tt><ParticleBCs></tt> section. it may be interspersed with other particle boundary conditions (MPM Only).		** "ParticleBCs" to insert in the <tt><ParticleBCs></tt> section. it may be interspersed with other particle boundary conditions (MPM Only).
Line 30:		Line 30:
	* <tt>(matid)</tt> specifies a material ID, but is only used when <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])		* <tt>(matid)</tt> specifies a material ID, but is only used when <tt>(section)</tt> is "Materials" (see [[#Notes\|below]])

	The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have ~~multuple~~ <tt>XMLData</tt> blocks for each section and ~~subsquent~~ blocks will be appended to previous blocks for each section.		The <tt>XML</tt> data that is inserted will be all lines between the <tt>XMLData</tt> command and the <tt>EndXMLData</tt> Command. You can have multiple <tt>XMLData</tt> blocks for each section and subsequent blocks will be appended to previous blocks for each section.

	<font color="red">Caution:</font> - all lines are inserted verbatim. If the block contains [[Expression Syntax\|expressions]], they will not be evaluated, but just inserted as the expression text. You can avoid this limitation, however, by using an [[Expression Syntax\|expression]] to define an [[Entity Command\|entity]] and then using that entity in the verbatim <tt>XML</tt> code. Similarly, if you comment out a line using the [[Command Line Syntax#Comment Line\|scripting language comment method]], that line will still be inserted with the verbatim <tt>XML</tt>. If you want to comment the <tt>XML</tt> code (or comment out lines in that code), you can use the <tt>XML</tt> comment method of <tt><!-- an XML comment --></tt> instead.		<font color="red">Caution:</font> - all lines are inserted verbatim. If the block contains [[Expression Syntax\|expressions]], they will not be evaluated, but just inserted as the expression text. You can avoid this limitation, however, by using an [[Expression Syntax\|expression]] to define an [[Entity Command\|entity]] and then using that entity in the verbatim <tt>XML</tt> code. Similarly, if you comment out a line using the [[Command Line Syntax#Comment Line\|scripting language comment method]], that line will still be inserted with the verbatim <tt>XML</tt>. If you want to comment the <tt>XML</tt> code (or comment out lines in that code), you can use the <tt>XML</tt> comment method of <tt><!-- an XML comment --></tt> instead.
Line 38:		Line 38:
	<ol>		<ol>

	<li>Each insertion into "~~Materials~~" must define a single [[Material Command Block\|<tt>Material</tt> command block]]:		<li>Each insertion into "Material" must define a single [[Material Command Block\|<tt>Material</tt> command block]]:
	<pre><Material Type="20" Name="New Material">		<pre><Material Type="20" Name="New Material">
	(property commands)		(property commands)
Line 45:		Line 45:
	where the property commands set the material properties. The second <tt>(matid)</tt> parameter to the <tt>XMLData</tt> command must be provided and it must have a unique [[Material Command Block\|material ID]] (which can be used like regular material IDs). This insertion option is provided to work with [[Material Models\|materials]] in the code engines that are not yet supported by [[NairnFEAMPM]] or [[NairnFEAMPMViz]], such a new [[Material Models\|materials]] currently in development.		where the property commands set the material properties. The second <tt>(matid)</tt> parameter to the <tt>XMLData</tt> command must be provided and it must have a unique [[Material Command Block\|material ID]] (which can be used like regular material IDs). This insertion option is provided to work with [[Material Models\|materials]] in the code engines that are not yet supported by [[NairnFEAMPM]] or [[NairnFEAMPMViz]], such a new [[Material Models\|materials]] currently in development.

	<li>For "MaterialPoints", "Materials", "GridBCs", and "ParticleBCs", the data will be inserted when the <tt>XMLData</tt> command is used. This approach allows you to intersperse <tt>XML</tt> features with scripted features in these sections. For other sections the <tt>XML</tt> is inserted at the end each section.		<li>For "MaterialPoints", "Materials, "GridBCs", and "ParticleBCs", the data will be inserted when the <tt>XMLData</tt> command is used. This approach allows you to intersperse <tt>XML</tt> features with scripted features in these sections. For other sections the <tt>XML</tt> is inserted at the end each section.

	<li>Another command to insert raw <tt>XML</tt> data is the [[Entity Command]].		<li>Another command to insert raw <tt>XML</tt> data is the [[Entity Command]].

	</ol>		</ol>