deletions | additions       diff --git a/UWUW.tex b/UWUW.tex  index 397549d..67116d3 100644  --- a/UWUW.tex  +++ b/UWUW.tex 
...
CNERG have developed a new scheme known as ``The University of Wisconsin Unified Workflow'' - (UW$^2$), with this scheme we encode problem metadata as raw text strings which are interpreted downstream by a pre-process tool. Material assignments are specified with the \texttt{mat:\{name\}} key-value pair. This data is stored in the geometry file and is indelibly associated with the volume. The PyNE \cite{pyne2014,Bates2014} \texttt{MaterialLibrary} capabillity is used to look up the association of that material name to the composition as defined in the material library. This PyNE \texttt{Material} object, is then inserted into the geometry file thus a local copy of that which was present and permenantly inserted into the geometry file. This material object is then used at run time to translate the PyNE form into the physics engine specific form.  Similarly for material metadata, there exists methods to handle the tally specific metadata, for this purpose a specific class was written for PyNE which allows the instanciation of tallies with names, volume id numbers and so on. The syntax for the creation of tallies is \texttt{tally:\{particle name\} \\ \backslash  \{tally type}}, using the naming PyNE particle naming scheme. Like with Materials, the Tally objects are stored in the geometry file and translated to physics engine specific form at run time. Currently Cubit \cite{} is used to assign this metadata using the group feature, where volumes which have a consistent property are assigned to the same group. The group data are handled by a pre-process code which assigns each volume in the group the property belonging to the group. Ultimately, as input every DAGMC enabled code is capable of recieving an identical description of material compositions and identical descriptions of tallies.