[Sumover-dev] [svn commit] r4200 - vic/branches/cc/docs/plan

[sumover-dev at cs.ucl.ac.uk]

Author: soohyunc
Date: Mon Jun 30 23:09:13 2008
New Revision: 4200

Modified:
   vic/branches/cc/docs/plan/1-intro.tex
   vic/branches/cc/docs/plan/2-overview.tex
   vic/branches/cc/docs/plan/3-results.tex
   vic/branches/cc/docs/plan/report.tex

Log:
report re-structuring...


Modified: vic/branches/cc/docs/plan/1-intro.tex
==============================================================================
--- vic/branches/cc/docs/plan/1-intro.tex	(original)
+++ vic/branches/cc/docs/plan/1-intro.tex	Mon Jun 30 23:09:13 2008
@@ -114,53 +114,17 @@
 Next, it's necessary to generate traffic in a real network (or a dummy network)
 for that purpose.
 
-\subsection{\label{ssec:plan}Milestones}
+\subsection{\label{ssec:structure}Structure of the Report}
 
-Based on Section~\ref{ssec:aims}, we break down time scale needed to develop
-each component as belows. The milestones would like more ``conceptual'' rather
-than practical or tangible. The project dates listed below are only indicative
-as the project will evolve based on the results being obtained while working on
-it.
-
-\paragraph{\textsf{May 26}} \underline{\textbf{GSoC Project Start}}
-
-\paragraph{\textsf{May 31}} Finish background research and readings: \emph{vic} source
-codes and UltraGrid's TFRC implementation along with RTP extension part.  The
-aim here is try looking at how TFRC was implemented over a \emph{vic}-like platform
-(different library and different language so it would not be possible to
-directly re-use them.).
-
-\paragraph{\textsf{Jun. 6}} Commit necessary TFRC files - e.g., TFRC
-(\texttt{tfrc\_sndr.cpp, tfrc\_rcvr.cpp}, etc), RTP integration
-(\texttt{rtp\_tfrc.cpp}, etc), CC handler (\texttt{cc.cpp}, etc). It would not
-be necessariliy a full implementation at this stage yet.
-
-\paragraph{\textsf{Jun. 20}} Primitive TFRC implementation. At this stage, we
-should be able to send a packet using TFRC (with dummy packets).
-
-\paragraph{\textsf{Jun. 27}} Commit necessary TFWC files. It would not be
-necessariliy a full implementation at this stage yet.
-
-\paragraph{\textsf{Juil. 4}} Primitive TFWC implementation
-
-\paragraph{\textsf{Jul. 7}} \underline{\textbf{Mid-term Evaluation}} -- Write
-interim report: what has been obtained successfully and what has not, what
-should be changed for the final project goal, etc.
-
-\paragraph{\textsf{Jul. 18}} Examine what feedback information can be used to
-codecs.  (e.g., modify codecs? or use Q-factor in a specific codec?, etc)
-
-\paragraph{\textsf{Jul. 25}} Finalizing TFR(W)C interactioin with codecs.
-
-\paragraph{\textsf{Aug. 1}} Test and Evaluation for the whole systems.
-
-\paragraph{\textsf{Aug. 8}} Final evaluation and discussion
-
-\paragraph{\textsf{Aug. 15}} Come up with final version of source codes and a
-report.
-
-\paragraph{\textsf{Aug. 18}} \underline{\textbf{Project Submission}}-- Submit
-the results to Google and wrap-up.
+This report is organized as belows. In order to get an idea on integrating the
+congestion control modules in \emph{vic}, we describe the basic working
+mechanisms of UltraGrid~\ref{UltraGrid} in Section~\ref{sec:ultragrid}.
+Section~\ref{sec:overview} describes the high-level overview of \emph{vic}
+architecture and also gives an examples how the still grabber generates packets
+over the network. Section~\ref{sec:cc-api} describes our proposed congestion
+control APIs and how it could be integrated in \emph{vic}.
+Section~\ref{sec:summary} summarized the project milestones and the expected
+outcomes.
 
 \newpage
 

Modified: vic/branches/cc/docs/plan/2-overview.tex
==============================================================================
--- vic/branches/cc/docs/plan/2-overview.tex	(original)
+++ vic/branches/cc/docs/plan/2-overview.tex	Mon Jun 30 23:09:13 2008
@@ -56,7 +56,7 @@
 grabbing video frames from the memory and passes to the encoder
 (\texttt{encoder-h261.cpp}): in this case, \texttt{H261PixelEncoder::consume()}
 will be called. After that, it starts encoding macro-blocks given a set of YUV
-inputs and send the encoded frames to the transmit module
+inputs and sends the encoded frames to the transmit module
 (\texttt{SessionManager::transmit()}). The encoder provides the encoded frames
 to the transmit module as long as they are available: see the dashed line in
 Figure~\ref{fig:still-grabber}.  \texttt{SessionManager::transmit()} then
@@ -69,6 +69,6 @@
 the encoded frames could be queued in some send buffer, and the congestion
 control module picks up the frames determined by its suggested rate, for
 example, if it is TFRC then it picks up the frames in a certain interval, or if
-it is TFWC then it pick up the frames as long as the sending window allows.
+it is TFWC then it pick up the frames as long as the sending window allows. 
 
 \newpage

Modified: vic/branches/cc/docs/plan/3-results.tex
==============================================================================
--- vic/branches/cc/docs/plan/3-results.tex	(original)
+++ vic/branches/cc/docs/plan/3-results.tex	Mon Jun 30 23:09:13 2008
@@ -1,6 +1,55 @@
 % $Id$
 
-We have summarized the expected outcomes and deliveralbes from the project.
+This section summarizes the project milestones and the expected outcomes.
+
+\subsection{\label{ssec:plan}Milestones}
+
+Based on Section~\ref{ssec:aims}, we break down time scale needed to develop
+each component as belows. The milestones would like more ``conceptual'' rather
+than practical or tangible. The project dates listed below are only indicative
+as the project will evolve based on the results being obtained while working on
+it.
+
+\paragraph{\textsf{May 26}} \underline{\textbf{GSoC Project Start}}
+
+\paragraph{\textsf{May 31}} Finish background research and readings: \emph{vic} source
+codes and UltraGrid's TFRC implementation along with RTP extension part.  The
+aim here is try looking at how TFRC was implemented over a \emph{vic}-like platform
+(different library and different language so it would not be possible to
+directly re-use them.).
+
+\paragraph{\textsf{Jun. 6}} Commit necessary TFRC files - e.g., TFRC
+(\texttt{tfrc\_sndr.cpp, tfrc\_rcvr.cpp}, etc), RTP integration
+(\texttt{rtp\_tfrc.cpp}, etc), CC handler (\texttt{cc.cpp}, etc). It would not
+be necessariliy a full implementation at this stage yet.
+
+\paragraph{\textsf{Jun. 20}} Primitive TFRC implementation. At this stage, we
+should be able to send a packet using TFRC (with dummy packets).
+
+\paragraph{\textsf{Jun. 27}} Commit necessary TFWC files. It would not be
+necessariliy a full implementation at this stage yet.
+
+\paragraph{\textsf{Juil. 4}} Primitive TFWC implementation
+
+\paragraph{\textsf{Jul. 7}} \underline{\textbf{Mid-term Evaluation}} -- Write
+interim report: what has been obtained successfully and what has not, what
+should be changed for the final project goal, etc.
+
+\paragraph{\textsf{Jul. 18}} Examine what feedback information can be used to
+codecs.  (e.g., modify codecs? or use Q-factor in a specific codec?, etc)
+
+\paragraph{\textsf{Jul. 25}} Finalizing TFR(W)C interactioin with codecs.
+
+\paragraph{\textsf{Aug. 1}} Test and Evaluation for the whole systems.
+
+\paragraph{\textsf{Aug. 8}} Final evaluation and discussion
+
+\paragraph{\textsf{Aug. 15}} Come up with final version of source codes and a
+report.
+
+\paragraph{\textsf{Aug. 18}} \underline{\textbf{Project Submission}}-- Submit
+the results to Google and wrap-up.
+
 
 \subsection{\label{ssec:codes}Program Source Code}
 

Modified: vic/branches/cc/docs/plan/report.tex
==============================================================================
--- vic/branches/cc/docs/plan/report.tex	(original)
+++ vic/branches/cc/docs/plan/report.tex	Mon Jun 30 23:09:13 2008
@@ -134,11 +134,17 @@
 \section{\label{sec:intro}Introduction}
 \input{1-intro}
 
+\section{\label{sec:ultragrid}UltraGrid Overview}
+\input{2-ultragrid}
+
 \section{\label{sec:overview}Project Overview}
-\input{2-overview}
+\input{3-overview}
+
+\section{\label{sec:cc-api}Proposed CC APIs}
+\input{4-cc-api}
 
-\section{\label{sec:results}Results} 
-\input{3-results}
+\section{\label{sec:summary}Milestones and Outcomes} 
+\input{5-summary}
 
 %\input{acknowledgment}