# HG changeset patch
# User Sean Halle <seanhalle@yahoo.com>
# Date 1342336564 25200
# Node ID 7e903acb5f6470df3552722777d908b93c8d4438
# Parent  4618b5af3b04e910b764a950c71a83ece74a38e0
perf tuning -- small changes to authors and so forth

diff -r 4618b5af3b04 -r 7e903acb5f64 0__Papers/Holistic_Model/Perf_Tune/latex/Holistic_Perf_Tuning.pdf
Binary file 0__Papers/Holistic_Model/Perf_Tune/latex/Holistic_Perf_Tuning.pdf has changed
diff -r 4618b5af3b04 -r 7e903acb5f64 0__Papers/Holistic_Model/Perf_Tune/latex/Holistic_Perf_Tuning.tex
--- a/0__Papers/Holistic_Model/Perf_Tune/latex/Holistic_Perf_Tuning.tex	Fri Jul 13 15:36:29 2012 -0700
+++ b/0__Papers/Holistic_Model/Perf_Tune/latex/Holistic_Perf_Tuning.tex	Sun Jul 15 00:16:04 2012 -0700
@@ -56,7 +56,7 @@
            {nengel@mailbox.tu-berlin.de}
 \authorinfo{Sean Halle}
            {Open Source Research Institute}
-           {Email1}
+           {seanhalle@OpenSourceResearchInstitute.org}
 \authorinfo{Ben Juurlink}
            {TU Berlin}
            {b.juurlink@tu-berlin.de}
@@ -541,7 +541,7 @@
 \subsubsection{Recording time, instructions, and cache misses }
  Just recording the units and connections between them is not enough. Because the SCG represents core usage, it also needs  the cycles spent on each activity, including internal runtime activities. The size of each interval of core usage is recorded and assigned to a  segment of a particular unit's life-line.
 
-The UCC also makes use  of the number of instructions in a unit, as an estimate of size of work in the unit, as illustrated by Fig [fig:UCC_expl]. Without knowing the relative size of the units, it is hard to estimate the amount of parallelism \emph{usefully} available in the application.
+The UCC also makes use  of the number of instructions in a unit, as an estimate of size of work in the unit, as illustrated by Fig \ref{fig:UCC_expl}. Without knowing the relative size of the units, it is hard to estimate the amount of parallelism \emph{usefully} available in the application.
 
 To measure the instructions, cycles, and communication (cache misses), we use hardware performance counters. Readings are inserted into the runtime code to capture core time spent on each segment of the life-line of a unit: 
 \begin{enumerate}