Main Page - Revision history

Nairnj: /* Input Files for Calculations */

2023-11-28T23:11:29Z

Input Files for Calculations

← Older revision		Revision as of 23:11, 28 November 2023
Line 17:		Line 17:

	MPM simulations using [[OSParticulas]] or [[NairnMPM]] or FEA calculations using [[NairnFEA]] are controlled by input from an <tt>XML</tt> input file. This input file can be created manually by using any text or <tt>XML</tt> editing software. It is usually preferred, however, to use a higher-level [[Scripting Language Syntax\|scripting language]] to set up the calculations and then have an interpreter format those commands into the <tt>XML</tt> files needed by the code engines. This scripting method allows for more powerful input files that are much easier to customize for a range of simulations. Scripting calculations can be done by using either the [[NairnFEAMPM]] application (Mac only) or the [[NairnFEAMPMViz]] (Java tool) application. The [[Scripting Language Syntax\|scripting languages]] in these two applications are almost identical.		MPM simulations using [[OSParticulas]] or [[NairnMPM]] or FEA calculations using [[NairnFEA]] are controlled by input from an <tt>XML</tt> input file. This input file can be created manually by using any text or <tt>XML</tt> editing software. It is usually preferred, however, to use a higher-level [[Scripting Language Syntax\|scripting language]] to set up the calculations and then have an interpreter format those commands into the <tt>XML</tt> files needed by the code engines. This scripting method allows for more powerful input files that are much easier to customize for a range of simulations. Scripting calculations can be done by using either the [[NairnFEAMPM]] application (Mac only) or the [[NairnFEAMPMViz]] (Java tool) application. The [[Scripting Language Syntax\|scripting languages]] in these two applications are almost identical.

	~~=== Creating MPM and FEA Input Files ===~~

	The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:		The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:
Line 27:		Line 25:
	For convenience, these help topics are listed in the side bar on the left.		For convenience, these help topics are listed in the side bar on the left.

	==== Scripted Input Files ====		=== Scripted Input Files ===

	The recommended method for writing input files is to use the built-in scripting commands. Scripted input files are comprised of a series of commands. This documentation will explain these commands and elements using the style:		The recommended method for writing input files is to use the built-in scripting commands. Scripted input files are comprised of a series of commands. This documentation will explain these commands and elements using the style:
Line 41:		Line 39:
	The main reason to prefer scripted files is their flexibility. Besides a series of command, these input files use a built-in [[Scripting Language Syntax\|scripting language]] that can make use of [[Variable Names\|variables]] and both numeric and string [[Expression Syntax\|expressions]].		The main reason to prefer scripted files is their flexibility. Besides a series of command, these input files use a built-in [[Scripting Language Syntax\|scripting language]] that can make use of [[Variable Names\|variables]] and both numeric and string [[Expression Syntax\|expressions]].

	==== XML Input Files ====		=== XML Input Files ===

	If you are a glutton for punishment and do not mind absence of variables and expressions, input commands can be written directly in <tt>XML</tt> input files comprised of a series of <tt>XML</tt> elements. This documentation will explain all <tt>XML</tt> elements for all features using the style:		If you are a glutton for punishment and do not mind absence of variables and expressions, input commands can be written directly in <tt>XML</tt> input files comprised of a series of <tt>XML</tt> elements. This documentation will explain all <tt>XML</tt> elements for all features using the style:

Nairnj: /* Scripted Input Files */

2023-11-28T23:10:16Z

Scripted Input Files

← Older revision		Revision as of 23:10, 28 November 2023
Line 39:		Line 39:
	* <tt><(arg3)></tt> - enclosing an argument in angle brackets indicates an optional argument. If the argument is omitted, the code will assume some default value.		* <tt><(arg3)></tt> - enclosing an argument in angle brackets indicates an optional argument. If the argument is omitted, the code will assume some default value.

	The main reason to prefer scripted files is their flexibility. Besides a series of command, these input files ~~using~~ a built-in [[Scripting Language Syntax\|scripting language]] that can make use of [[Variable Names\|variables]] and both numeric and string [[Expression Syntax\|expressions]].		The main reason to prefer scripted files is their flexibility. Besides a series of command, these input files use a built-in [[Scripting Language Syntax\|scripting language]] that can make use of [[Variable Names\|variables]] and both numeric and string [[Expression Syntax\|expressions]].

	==== XML Input Files ====		==== XML Input Files ====

Nairnj: /* Input Files for Calculations */

2023-11-28T23:08:40Z

Input Files for Calculations

← Older revision		Revision as of 23:08, 28 November 2023
Line 18:		Line 18:
	MPM simulations using [[OSParticulas]] or [[NairnMPM]] or FEA calculations using [[NairnFEA]] are controlled by input from an <tt>XML</tt> input file. This input file can be created manually by using any text or <tt>XML</tt> editing software. It is usually preferred, however, to use a higher-level [[Scripting Language Syntax\|scripting language]] to set up the calculations and then have an interpreter format those commands into the <tt>XML</tt> files needed by the code engines. This scripting method allows for more powerful input files that are much easier to customize for a range of simulations. Scripting calculations can be done by using either the [[NairnFEAMPM]] application (Mac only) or the [[NairnFEAMPMViz]] (Java tool) application. The [[Scripting Language Syntax\|scripting languages]] in these two applications are almost identical.		MPM simulations using [[OSParticulas]] or [[NairnMPM]] or FEA calculations using [[NairnFEA]] are controlled by input from an <tt>XML</tt> input file. This input file can be created manually by using any text or <tt>XML</tt> editing software. It is usually preferred, however, to use a higher-level [[Scripting Language Syntax\|scripting language]] to set up the calculations and then have an interpreter format those commands into the <tt>XML</tt> files needed by the code engines. This scripting method allows for more powerful input files that are much easier to customize for a range of simulations. Scripting calculations can be done by using either the [[NairnFEAMPM]] application (Mac only) or the [[NairnFEAMPMViz]] (Java tool) application. The [[Scripting Language Syntax\|scripting languages]] in these two applications are almost identical.

	==== Creating MPM and FEA Input Files ====		=== Creating MPM and FEA Input Files ===

	The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:		The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:
Line 26:		Line 26:

	For convenience, these help topics are listed in the side bar on the left.		For convenience, these help topics are listed in the side bar on the left.

			==== Scripted Input Files ====

	The recommended method for writing input files is to use the built-in scripting commands. Scripted input files are comprised of a series of commands. This documentation will explain these commands and elements using the style:		The recommended method for writing input files is to use the built-in scripting commands. Scripted input files are comprised of a series of commands. This documentation will explain these commands and elements using the style:
Line 38:		Line 40:

	The main reason to prefer scripted files is their flexibility. Besides a series of command, these input files using a built-in [[Scripting Language Syntax\|scripting language]] that can make use of [[Variable Names\|variables]] and both numeric and string [[Expression Syntax\|expressions]].		The main reason to prefer scripted files is their flexibility. Besides a series of command, these input files using a built-in [[Scripting Language Syntax\|scripting language]] that can make use of [[Variable Names\|variables]] and both numeric and string [[Expression Syntax\|expressions]].

			==== XML Input Files ====

	If you are a glutton for punishment and do not mind absence of variables and expressions, input commands can be written directly in <tt>XML</tt> input files comprised of a series of <tt>XML</tt> elements. This documentation will explain all <tt>XML</tt> elements for all features using the style:		If you are a glutton for punishment and do not mind absence of variables and expressions, input commands can be written directly in <tt>XML</tt> input files comprised of a series of <tt>XML</tt> elements. This documentation will explain all <tt>XML</tt> elements for all features using the style:

Nairnj: /* Creating MPM and FEA Input Files */

2023-11-28T23:07:35Z

Creating MPM and FEA Input Files

← Older revision		Revision as of 23:07, 28 November 2023
Line 37:		Line 37:
	* <tt><(arg3)></tt> - enclosing an argument in angle brackets indicates an optional argument. If the argument is omitted, the code will assume some default value.		* <tt><(arg3)></tt> - enclosing an argument in angle brackets indicates an optional argument. If the argument is omitted, the code will assume some default value.

	If you are a glutton for punishment and do not mind ~~a lack~~ of ~~flexibiity~~, input commands can be written <tt>XML</tt> input files comprised of a series of <tt>XML</tt> elements. This documentation will explain ~~these~~ elements using the style:		The main reason to prefer scripted files is their flexibility. Besides a series of command, these input files using a built-in [[Scripting Language Syntax\|scripting language]] that can make use of [[Variable Names\|variables]] and both numeric and string [[Expression Syntax\|expressions]].

			If you are a glutton for punishment and do not mind absence of variables and expressions, input commands can be written directly in <tt>XML</tt> input files comprised of a series of <tt>XML</tt> elements. This documentation will explain all <tt>XML</tt> elements for all features using the style:

	<Command attr1='(arg1)' attr2='(arg2)'>(arg3)</Command>		<Command attr1='(arg1)' attr2='(arg2)'>(arg3)</Command>

Nairnj: /* Input Files for Calculations */

2023-11-28T23:03:10Z

Input Files for Calculations

← Older revision		Revision as of 23:03, 28 November 2023
Line 18:		Line 18:
	MPM simulations using [[OSParticulas]] or [[NairnMPM]] or FEA calculations using [[NairnFEA]] are controlled by input from an <tt>XML</tt> input file. This input file can be created manually by using any text or <tt>XML</tt> editing software. It is usually preferred, however, to use a higher-level [[Scripting Language Syntax\|scripting language]] to set up the calculations and then have an interpreter format those commands into the <tt>XML</tt> files needed by the code engines. This scripting method allows for more powerful input files that are much easier to customize for a range of simulations. Scripting calculations can be done by using either the [[NairnFEAMPM]] application (Mac only) or the [[NairnFEAMPMViz]] (Java tool) application. The [[Scripting Language Syntax\|scripting languages]] in these two applications are almost identical.		MPM simulations using [[OSParticulas]] or [[NairnMPM]] or FEA calculations using [[NairnFEA]] are controlled by input from an <tt>XML</tt> input file. This input file can be created manually by using any text or <tt>XML</tt> editing software. It is usually preferred, however, to use a higher-level [[Scripting Language Syntax\|scripting language]] to set up the calculations and then have an interpreter format those commands into the <tt>XML</tt> files needed by the code engines. This scripting method allows for more powerful input files that are much easier to customize for a range of simulations. Scripting calculations can be done by using either the [[NairnFEAMPM]] application (Mac only) or the [[NairnFEAMPMViz]] (Java tool) application. The [[Scripting Language Syntax\|scripting languages]] in these two applications are almost identical.

	==== ~~Writing~~ MPM and FEA Input Files ====		==== Creating MPM and FEA Input Files ====

	The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:		The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:

Nairnj: /* Input Files for Calculations */

2023-11-28T23:03:00Z

Input Files for Calculations

← Older revision		Revision as of 23:03, 28 November 2023
Line 18:		Line 18:
	MPM simulations using [[OSParticulas]] or [[NairnMPM]] or FEA calculations using [[NairnFEA]] are controlled by input from an <tt>XML</tt> input file. This input file can be created manually by using any text or <tt>XML</tt> editing software. It is usually preferred, however, to use a higher-level [[Scripting Language Syntax\|scripting language]] to set up the calculations and then have an interpreter format those commands into the <tt>XML</tt> files needed by the code engines. This scripting method allows for more powerful input files that are much easier to customize for a range of simulations. Scripting calculations can be done by using either the [[NairnFEAMPM]] application (Mac only) or the [[NairnFEAMPMViz]] (Java tool) application. The [[Scripting Language Syntax\|scripting languages]] in these two applications are almost identical.		MPM simulations using [[OSParticulas]] or [[NairnMPM]] or FEA calculations using [[NairnFEA]] are controlled by input from an <tt>XML</tt> input file. This input file can be created manually by using any text or <tt>XML</tt> editing software. It is usually preferred, however, to use a higher-level [[Scripting Language Syntax\|scripting language]] to set up the calculations and then have an interpreter format those commands into the <tt>XML</tt> files needed by the code engines. This scripting method allows for more powerful input files that are much easier to customize for a range of simulations. Scripting calculations can be done by using either the [[NairnFEAMPM]] application (Mac only) or the [[NairnFEAMPMViz]] (Java tool) application. The [[Scripting Language Syntax\|scripting languages]] in these two applications are almost identical.

	==== MPM and FEA Input Files ====		==== Writing MPM and FEA Input Files ====

	The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:		The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:

Nairnj: /* Input Files for Calculations */

2023-11-28T23:02:41Z

Input Files for Calculations

← Older revision		Revision as of 23:02, 28 November 2023
Line 27:		Line 27:
	For convenience, these help topics are listed in the side bar on the left.		For convenience, these help topics are listed in the side bar on the left.

	~~==== Documentation Notes ====~~		The recommended method for writing input files is to use the built-in scripting commands. Scripted input files are comprised of a series of commands. This documentation will explain these commands and elements using the style:

	~~To learn how to write input command files see the [[MPM Input Files\|MPM Calculations]] and [[FEA Calculations]] help topics~~ (~~and list in the side bar or all windows~~)~~. This topics have subtopics to all available calculations options in [[NairnMPM]]~~, ~~[[OSParticulas]]~~, ~~and [[NairnFEA]].~~		Command (arg1),(arg2),<(arg3)>,<(arg4)>

	~~Scripted input files~~ are ~~comprised of~~ a ~~series~~ of commands ~~and~~ <tt>XML</tt> input files ~~are~~ comprised of a series of <tt>XML</tt> elements. This documentation will explain these ~~commands and~~ elements using the style:		where

			* <tt>Command</tt> is the command name.
			* <tt>(arg1),(arg2)</tt>, ''etc.'', specify arguments whose function will be explained along with the command. Arguments are separated by commas, spaces, or tabs. If an argument includes a space, enclose that argument in quotes.
			* <tt><(arg3)></tt> - enclosing an argument in angle brackets indicates an optional argument. If the argument is omitted, the code will assume some default value.

			If you are a glutton for punishment and do not mind a lack of flexibiity, input commands can be written <tt>XML</tt> input files comprised of a series of <tt>XML</tt> elements. This documentation will explain these elements using the style:

	~~Command (arg1),(arg2),<(arg3)>,<(arg4)>~~
	<Command attr1='(arg1)' attr2='(arg2)'>(arg3)</Command>		<Command attr1='(arg1)' attr2='(arg2)'>(arg3)</Command>

	where		where

	* <tt>Command</tt> is the ~~command~~ name.		* <tt>Command</tt> is the <tt>XML</tt> element name.
	* <tt>(arg1),(arg2)</tt>, ''etc.'', specify arguments whose function will be explained along with the command.		* <tt>(arg1),(arg2)</tt>, ''etc.'', specify arguments whose function will be explained along with the command.
	* <tt><(arg3)></tt> - enclosing an argument in angle brackets indicates an optional argument. If the argument is omitted, the code will assume some default value.
	* <tt>attr1</tt>, <tt>attr2</tt>, ''etc.'', are attributes to the <tt>XML</tt> element.		* <tt>attr1</tt>, <tt>attr2</tt>, ''etc.'', are attributes to the <tt>XML</tt> element.

Nairnj: /* MPM and FEA Input Files */

2023-11-28T22:37:16Z

MPM and FEA Input Files

← Older revision		Revision as of 22:37, 28 November 2023
Line 22:		Line 22:
	The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:		The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:

	* [[MPM Input Files\|~~Input Files for~~ MPM Calculations]]		* Input Files for [[MPM Input Files\|MPM Calculations]]
	* [[FEA Input Files\|~~Input Files for~~ FEA Calculations]]		* Input Files for [[FEA Input Files\|FEA Calculations]]

			For convenience, these help topics are listed in the side bar on the left.

	==== Documentation Notes ====		==== Documentation Notes ====

Nairnj: /* Documentation Notes */

2023-11-28T22:35:48Z

Documentation Notes

← Older revision		Revision as of 22:35, 28 November 2023
Line 27:		Line 27:
	==== Documentation Notes ====		==== Documentation Notes ====

	To learn how to write input command files see the [[MPM Calculations]] and [[FEA Calculations]] help topics (and list in the side bar or all windows). This topics have subtopics to all available calculations options in [[NairnMPM]], [[OSParticulas]], and [[NairnFEA]].		To learn how to write input command files see the [[MPM Input Files\|MPM Calculations]] and [[FEA Calculations]] help topics (and list in the side bar or all windows). This topics have subtopics to all available calculations options in [[NairnMPM]], [[OSParticulas]], and [[NairnFEA]].

	Scripted input files are comprised of a series of commands and <tt>XML</tt> input files are comprised of a series of <tt>XML</tt> elements. This documentation will explain these commands and elements using the style:		Scripted input files are comprised of a series of commands and <tt>XML</tt> input files are comprised of a series of <tt>XML</tt> elements. This documentation will explain these commands and elements using the style:

Nairnj: /* Input File Documentation Notes */

2023-11-28T22:35:13Z

Input File Documentation Notes

← Older revision		Revision as of 22:35, 28 November 2023
Line 25:		Line 25:
	* [[FEA Input Files\|Input Files for FEA Calculations]]		* [[FEA Input Files\|Input Files for FEA Calculations]]

	==== ~~Input File~~ Documentation Notes ====		==== Documentation Notes ====

			To learn how to write input command files see the [[MPM Calculations]] and [[FEA Calculations]] help topics (and list in the side bar or all windows). This topics have subtopics to all available calculations options in [[NairnMPM]], [[OSParticulas]], and [[NairnFEA]].

	Scripted input files are comprised of a series of commands and <tt>XML</tt> input files are comprised of a series of <tt>XML</tt> elements. This documentation will explain these commands and elements using the style:		Scripted input files are comprised of a series of commands and <tt>XML</tt> input files are comprised of a series of <tt>XML</tt> elements. This documentation will explain these commands and elements using the style: