Entity Command - Revision history

Nairnj: /* Usage */

2014-02-05T17:53:07Z

Usage

← Older revision		Revision as of 17:53, 5 February 2014
Line 30:		Line 30:
	# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be documented as accepting them. In commands that directly support entity use, you must provide the name as in the <tt>Entity</tt> command or without the leading ampersand (&) and trailing semicolon (;).[[#Notes\|<sup>1</sup>]] The commands that accept entities are all commands intended to accept numerical values.		# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be documented as accepting them. In commands that directly support entity use, you must provide the name as in the <tt>Entity</tt> command or without the leading ampersand (&) and trailing semicolon (;).[[#Notes\|<sup>1</sup>]] The commands that accept entities are all commands intended to accept numerical values.
	# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;).[[#Notes\|<sup>1</sup>]] This usage works for many, but not all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> output to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responsibility to make sure they are defined by <tt>Entity</tt> commands.		# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;).[[#Notes\|<sup>1</sup>]] This usage works for many, but not all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> output to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responsibility to make sure they are defined by <tt>Entity</tt> commands.
			# The [[XMLData Command\|XMLData command]] lets you insert verbatim <tt>XML</tt> code into commands files, but the verbatim text cannot include [[Expression Syntax\|expressions]]. A work around is to define an entity using an <tt>Entity</tt> command with the expression and then use that entity in the verbatim <tt>XML</tt> code.

	== Notes ==		== Notes ==

	# When using [[NairnFEAMPM]], entities provided with the leading ampersand (&) and trailing semicolon (;) must be enclosed in quotes (''e.g''., <tt>"&fxn;"</tt>). They do not need to be quoted when using [[NairnFEAMPMViz]].		# When using [[NairnFEAMPM]], entities provided with the leading ampersand (&) and trailing semicolon (;) must be enclosed in quotes (''e.g''., <tt>"&fxn;"</tt>). They do not need to be quoted when using [[NairnFEAMPMViz]].

Nairnj: /* Notes */

2013-09-13T06:00:37Z

Notes

← Older revision		Revision as of 06:00, 13 September 2013
Line 33:		Line 33:
	== Notes ==		== Notes ==

	# When using [[NairnFEAMPM]], entities provided with the leading ampersand (&) and trailing semicolon (;) ~~mist~~ be enclosed in quotes (''e.g''., <tt>"&fxn;"</tt>). They do not need to be quoted when using [[NairnFEAMPMViz]].		# When using [[NairnFEAMPM]], entities provided with the leading ampersand (&) and trailing semicolon (;) must be enclosed in quotes (''e.g''., <tt>"&fxn;"</tt>). They do not need to be quoted when using [[NairnFEAMPMViz]].

Nairnj: /* Notes */

2013-09-13T05:57:08Z

Notes

← Older revision		Revision as of 05:57, 13 September 2013
Line 33:		Line 33:
	== Notes ==		== Notes ==

	# In [NairnFEAMPMViz]]		# When using [[NairnFEAMPM]], entities provided with the leading ampersand (&) and trailing semicolon (;) mist be enclosed in quotes (''e.g''., <tt>"&fxn;"</tt>). They do not need to be quoted when using [[NairnFEAMPMViz]].

Nairnj: /* Usage */

2013-09-13T05:54:26Z

Usage

← Older revision		Revision as of 05:54, 13 September 2013
Line 28:		Line 28:
	== Usage ==		== Usage ==

	# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be documented as accepting them. In commands that directly support entity use, you must provide the name as in the <tt>Entity</tt> command or without the leading ampersand (&) and trailing semicolon (;).[#Notes\|<sup>1</sup>] The commands that accept entities are all commands intended to accept numerical values.		# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be documented as accepting them. In commands that directly support entity use, you must provide the name as in the <tt>Entity</tt> command or without the leading ampersand (&) and trailing semicolon (;).[[#Notes\|<sup>1</sup>]] The commands that accept entities are all commands intended to accept numerical values.
	# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but ~~nor~~ all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your ~~responbility~~ to make sure they are defined by <tt>Entity</tt> commands.		# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;).[[#Notes\|<sup>1</sup>]] This usage works for many, but not all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> output to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responsibility to make sure they are defined by <tt>Entity</tt> commands.

	== Notes ==		== Notes ==

	# In [NairnFEAMPMViz]]		# In [NairnFEAMPMViz]]

Nairnj: /* Usage */

2013-09-13T05:44:52Z

Usage

← Older revision		Revision as of 05:44, 13 September 2013
Line 29:		Line 29:

	# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be documented as accepting them. In commands that directly support entity use, you must provide the name as in the <tt>Entity</tt> command or without the leading ampersand (&) and trailing semicolon (;).[#Notes\|<sup>1</sup>] The commands that accept entities are all commands intended to accept numerical values.		# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be documented as accepting them. In commands that directly support entity use, you must provide the name as in the <tt>Entity</tt> command or without the leading ampersand (&) and trailing semicolon (;).[#Notes\|<sup>1</sup>] The commands that accept entities are all commands intended to accept numerical values.
	# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined by <tt>Entity<tt> commands.		# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined by <tt>Entity</tt> commands.

	== Notes ==		== Notes ==

	# In [NairnFEAMPMViz]]		# In [NairnFEAMPMViz]]

Nairnj: /* Usage */

2013-09-13T05:44:37Z

Usage

← Older revision		Revision as of 05:44, 13 September 2013
Line 28:		Line 28:
	== Usage ==		== Usage ==

	# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be ~~document~~ as accepting them. In commands that directly support entity use, you ~~can~~ provide the name ~~with~~ or without the leading ampersand (&) and trailing semicolon (;). The commands that accept entities are all commands intended to accept numerical values.		# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be documented as accepting them. In commands that directly support entity use, you must provide the name as in the <tt>Entity</tt> command or without the leading ampersand (&) and trailing semicolon (;).[#Notes\|<sup>1</sup>] The commands that accept entities are all commands intended to accept numerical values.
	# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined by <tt>Entity<tt> commands.		# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined by <tt>Entity<tt> commands.

			== Notes ==

			# In [NairnFEAMPMViz]]

Nairnj: /* Usage */

2013-09-13T04:43:30Z

Usage

← Older revision		Revision as of 04:43, 13 September 2013
Line 29:		Line 29:

	# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be document as accepting them. In commands that directly support entity use, you can provide the name with or without the leading ampersand (&) and trailing semicolon (;). The commands that accept entities are all commands intended to accept numerical values.		# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be document as accepting them. In commands that directly support entity use, you can provide the name with or without the leading ampersand (&) and trailing semicolon (;). The commands that accept entities are all commands intended to accept numerical values.
	# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined.		# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined by <tt>Entity<tt> commands.

Nairnj: /* Usage */

2013-09-13T04:39:42Z

Usage

← Older revision		Revision as of 04:39, 13 September 2013
Line 28:		Line 28:
	== Usage ==		== Usage ==

	# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be document as accepting them. In commands that support entity use, you can provide the name with or without the leading ampersand (&) and trailing semicolon (;). The commands that accept entities are all commands intended to accept numerical values.		# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be document as accepting them. In commands that directly support entity use, you can provide the name with or without the leading ampersand (&) and trailing semicolon (;). The commands that accept entities are all commands intended to accept numerical values.
	# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined.		# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined.

Nairnj: /* Usage */

2013-09-13T04:36:01Z

Usage

← Older revision		Revision as of 04:36, 13 September 2013
Line 28:		Line 28:
	== Usage ==		== Usage ==

	# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be document as accepting them. ~~To use an~~ entity ~~in those commands, give the same name~~ use ~~in the <tt>Entity</tt> command (''i.e.''~~, the ~~entity~~ name without the leading ampersand (&) or trailing semicolon (;). The commands that accept entities are all commands intended to accept numerical values.		# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be document as accepting them. In commands that support entity use, you can provide the name with or without the leading ampersand (&) and trailing semicolon (;). The commands that accept entities are all commands intended to accept numerical values.
	# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined.		# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined.

Nairnj: /* Usage */

2013-09-13T04:25:28Z

Usage

← Older revision		Revision as of 04:25, 13 September 2013
Line 28:		Line 28:
	== Usage ==		== Usage ==

	~~One~~ entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity. Each command that allows an entity will be document as accepting them. To use an entity, give the same name use in the <tt>Entity</tt> command (i.e., the entity name without the leading ampersand (&) or trailing semicolon (;). The commands that accept entities are all commands intended to accept numerical values.		# Once entities are defined, you can use then in selected commands. For example, the [[MPM Methods and Simulation Timing#Input Commands\|<tt>MaximumTime</tt> command]] will accept an entity to set the maximum time. Each command that allows an entity will be document as accepting them. To use an entity in those commands, give the same name use in the <tt>Entity</tt> command (''i.e.'', the entity name without the leading ampersand (&) or trailing semicolon (;). The commands that accept entities are all commands intended to accept numerical values.
			# You can also use entities on most commands that expect string arguments such as the [[MPM Archiving Options#Scripted Input Files\|<tt>Archive</tt> command]] or in place of any argument that can be a [[User Defined Functions\|user-defined function]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should always use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, commands that accept string arguments. When in doubt, you can test by providing an entity and then checking the resulting <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without verifying you have actually defined that entity. It is your responbility to make sure they are defined.
	You can also use entities on most commands that expect string arguments such as the [[MPM Archiving ~~Option\|~~Scripted Input Files\|<tt>Archive</tt> command]] or any argument that can be a [[User Defined Functions\|user-defined function.]]. In this usage, the string you supply is simply used in place of the expected string and therefore you should use the complete entity name including the leading ampersand (&) and trailing semicolon (;). This usage works for many, but nor all, ~~command~~ that accept string arguments. When in doubt, you can test by providing an entity and then checking the ~~results~~ <tt>XML</tt> to verify the entity was inserted as expected. In addition, the entity you provide is inserted without ~~verify~~ you have actually defined that entity. It is your responbility to make sure they are defined.