Difference between revisions of "ConsistentUnits Command"

From OSUPDOCS
Jump to navigation Jump to search
Line 18: Line 18:
Alternatively, if none of the length, mass, and time attributes are provided, the code will run with generic units for length (L), mass (M), and time (T). The default (if this command is not used) is to use "Legacy Units". If this command is used, you must specify all three attributes or specify none (to use generic units).
Alternatively, if none of the length, mass, and time attributes are provided, the code will run with generic units for length (L), mass (M), and time (T). The default (if this command is not used) is to use "Legacy Units". If this command is used, you must specify all three attributes or specify none (to use generic units).


== Table ==
== Legacy and Consistent Units ==


The original system of units is called "Legacy Units" while the new method is called "Consistent Units." The Legacy units can still be used (to allow backward compatibility of old input files) and it corresponds to any input file that omits the <tt>ConsistentUnits</tt> in the main header. The units required when using "Legacy Units" and in and some common "Consistent Units" systems are in the following table (note that you can use an metric consistent units are are not limited to those listed in the table):
The original system of units is called "Legacy Units" while the new method is called "Consistent Units." The Legacy units can still be used (to allow backward compatibility of old input files) and it corresponds to any input file that omits the <tt>ConsistentUnits</tt>. The units required when using "Legacy Units" and in the first column. The units required for some common "Consistent Units" systems are in the remaining columns (note that you can use any metric consistent units are are not limited to those listed in the table). When this documentation refers to units, it will refer to units class in the first column. You can refer to this table to see the units needed for "Legacy" units or for various sets of consistent units.




<!--<table border="1" cellpadding="2" cellspacing="0" width="90%" align="center">-->
<table border="1" cellpadding="2" cellspacing="0" width="90%" align="center">
<table align="center">


<tr><th>Unit</th><th>Legacy</th><th>Consistent</th><th>SI</th><th>mmgs</th><th>cgs</th>
<tr><th>Unit</th><th>Legacy</th><th>Consistent</th><th>SI</th><th>mmgs</th><th>cgs</th>

Revision as of 12:57, 2 June 2015

Introduction

NairnFEA and NairnMPM were initially developed using a specific set of units. The internal calculations were (for the most part) based on mm-g-seconds units (although there were some exceptions). The units for input of properties and output of results also usually followed this system, but not always. With the addition of the ConsistentUnits command (available since NairnFEA version 5, NairnMPM version 11, and OSParticulas version 2) all code can now be run in a new mode where input and output use consistent units and the user can specify any metric system of units. The old mode (which is still available) is called "Legacy Units" while the new mode is called "Consistent Units."

ConsistentUnits Command

The ConsistentUnits command is currently not supported for scripted input files. The problem is that the tools that create such files (NairnFEAMPM and NairnFEAMPMViz) enforce their own units that are currently incompatible with consistent units settings. This situation will change in the fuiture.

Altthough visualization tools cannot create input files using consistent units, they can read (and correctly interpret) output from simulations generated from raw XML files that use consistent. The units are selected in the Header element of XML files using:

<ConsistentUnits length='(units)' mass='(units)' time='(units)/>

where the (units) settings determine metric units as follows:

  • length can be km, m, dm cm, mm um (or microns), or nm
  • mass can be kg, g, mg, or ug
  • time can be s (or sec), ms (or msec), or us

Alternatively, if none of the length, mass, and time attributes are provided, the code will run with generic units for length (L), mass (M), and time (T). The default (if this command is not used) is to use "Legacy Units". If this command is used, you must specify all three attributes or specify none (to use generic units).

Legacy and Consistent Units

The original system of units is called "Legacy Units" while the new method is called "Consistent Units." The Legacy units can still be used (to allow backward compatibility of old input files) and it corresponds to any input file that omits the ConsistentUnits. The units required when using "Legacy Units" and in the first column. The units required for some common "Consistent Units" systems are in the remaining columns (note that you can use any metric consistent units are are not limited to those listed in the table). When this documentation refers to units, it will refer to units class in the first column. You can refer to this table to see the units needed for "Legacy" units or for various sets of consistent units.


UnitLegacyConsistentSImmgscgs
LengthmmLmmmcm
MassgMkggg
Densityg/cm3M/L3kg/m3g/mm3g/cm3
TimesTsss
Alt TimemsTsss
Velocitymm/sL/Tm/smm/scm/s
Alt Velocitym/sL/Tm/smm/scm/s
Accelerationmm/s2L/T2m/s2mm/s2cm/s2
ForceNF = M-L/T2NμNdyne
PressureMPaP = F/L2PaPaBa
Alt Strain%nonenonenonenone
EnergyJE = F-LJnJerg
Energy ReleaseJ/m2E/L2 J/m2nJ/mm2erg/cm2
Stress IntensityMPa-m0.5P-L0.5 Pa-m0.5Pa-mm0.5Ba-cm0.5
ViscositycPoiseP-TPa-sPa-sPoise
Diffusionmm2/sL2/Tm2/smm2/scm2/s
Solvent Fluxkg/(m2-s)M/(L2-T)kg/(m2-s)g/(mm2s)g/(cm2-s)
ConductivityW/(m-K)E/(L-K-s)W/(mm-K)nW/(mm-K)erg/(cm-K-s)
Heat CapacityJ/(kg-K)E/(M-K)J/(kg-K)nJ/(g-K)erg/(g-K)
Heat FluxW/m2E/L2W/m2nW/mm2erg/cm2