Formatted and compiled latex files

Author: actions-user

docs/projMngmnt/Final_Team_Contrib.pdf

@@ -24,15 +24,31 @@
 
 \section{Demo Plans}
 
-For our \textbf{Rev 0 demonstration}, we will showcase the core functionality and usability of our \textbf{energy-efficient Python code refactoring tool}. This demonstration will highlight the following key aspects:
+For our \textbf{Rev 0 demonstration}, we will showcase the core
+functionality and usability of our \textbf{energy-efficient Python
+code refactoring tool}. This demonstration will highlight the
+following key aspects:
 
 \begin{enumerate}
 
-    \item \textbf{Code Smell Detection:} We will demonstrate how our tool identifies inefficient coding patterns (\textit{code smells}) in Python source code that contribute to higher energy consumption.
-    \item \textbf{Automated Refactoring:} Our tool will apply targeted refactorings to optimize the detected code smells, improving energy efficiency.
-    \item \textbf{Energy Consumption Measurement:} Using \texttt{CodeCarbon}, we will measure and compare the energy consumption of the original code versus the refactored version, providing clear insights into energy savings.
-    \item \textbf{Functionality Preservation:} To ensure that optimizations do not alter program behaviour, we will run the original test suite against both the unoptimized and refactored versions.
-    \item \textbf{VS Code Integration:} We will showcase our \textbf{VS Code plugin}, where users can analyze a Python file for code smells, choose specific optimizations, and preview the refactored code with energy measurements. Users will have the option to accept or reject the proposed changes.
+  \item \textbf{Code Smell Detection:} We will demonstrate how our
+    tool identifies inefficient coding patterns (\textit{code
+    smells}) in Python source code that contribute to higher energy consumption.
+  \item \textbf{Automated Refactoring:} Our tool will apply targeted
+    refactorings to optimize the detected code smells, improving
+    energy efficiency.
+  \item \textbf{Energy Consumption Measurement:} Using
+    \texttt{CodeCarbon}, we will measure and compare the energy
+    consumption of the original code versus the refactored version,
+    providing clear insights into energy savings.
+  \item \textbf{Functionality Preservation:} To ensure that
+    optimizations do not alter program behaviour, we will run the
+    original test suite against both the unoptimized and refactored versions.
+  \item \textbf{VS Code Integration:} We will showcase our \textbf{VS
+    Code plugin}, where users can analyze a Python file for code
+    smells, choose specific optimizations, and preview the refactored
+    code with energy measurements. Users will have the option to
+    accept or reject the proposed changes.
 
 \end{enumerate}
 
@@ -175,7 +191,10 @@ \section{Commits}
   \end{tabular}
 \end{table}
 
-The number of commits does not necessarily reflect the amount of work done by each team member. Some members prefer to make frequent small commits while others make fewer but larger commits that include multiple changes.
+The number of commits does not necessarily reflect the amount of work
+done by each team member. Some members prefer to make frequent small
+commits while others make fewer but larger commits that include
+multiple changes.
 
 \section{Issue Tracker}
 
@@ -185,22 +204,25 @@ \section{Issue Tracker}
 issues (C only)) over the time period of interest.}
 
 \begin{table}[H]
-\centering
-\begin{tabular}{lll}
-\toprule
-\textbf{Student} & \textbf{Authored (O+C)} & \textbf{Assigned (C only)}\\
-\midrule
-Tanveer Brar & 1 & 47 \\
-Mya Hussain & 8 & 51 \\
-Ayushi Amin & 8 & 58 \\
-Sevhena Walker & 81 & 72 \\
-Nivetha Kuruparan & 17 & 53 \\
-\bottomrule
-\end{tabular}
+  \centering
+  \begin{tabular}{lll}
+    \toprule
+    \textbf{Student} & \textbf{Authored (O+C)} & \textbf{Assigned (C only)}\\
+    \midrule
+    Tanveer Brar & 1 & 47 \\
+    Mya Hussain & 8 & 51 \\
+    Ayushi Amin & 8 & 58 \\
+    Sevhena Walker & 81 & 72 \\
+    Nivetha Kuruparan & 17 & 53 \\
+    \bottomrule
+  \end{tabular}
 \end{table}
 
-Counts are considered by taking the total counts over the year and subtracting the counts at the time of the POC Team Contribution. This is the period of intrest. 
-We did a lot of work over the winter break to exclude that period and only do "this term" would inaccurately represent the counts.
+Counts are considered by taking the total counts over the year and
+subtracting the counts at the time of the POC Team Contribution. This
+is the period of intrest.
+We did a lot of work over the winter break to exclude that period and
+only do "this term" would inaccurately represent the counts.
 \section{CICD}
 
 \wss{Say how CICD is used in your project}