paella/doc
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Thomas FORGIONE
2015-04-21 16:47:12 +02:00
parent 4458dddae1
commit 8b08f66bff
141 changed files with 2612 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

88
report/chapters/actions.tex Normal file
View File

@@ -0,0 +1,88 @@
\chapter{Actions}
In order to avoid the realization of the identified risks, we applied some of our preventive actions.
\section{Initial actions table}
\begin{table}[h!]
\begin{center}
\begin{tabular}{|p{0.5cm}|p{3cm}|p{3cm}|p{2cm}|p{1.5cm}|p{1.5cm}|p{1.5cm}|p{1cm}|}
\hline
Id & Origin & Description & Accountable & Target date & Realisation & State \\
\hline
1 & Lack of knowledge from the developer & C++ training & Thomas & 22 Jan & 23 Jan & Closed \\
\hline
2 & Team work \& version management & Git repository creation & Thomas & 05 Feb & 05 Feb & Closed \\
\hline
3 & Input needed & Taking pictures & Thierry & 22 Jan & 22 Jan & Closed \\
\hline
4 & Report to write in english & Specifications translation & Emilie & 22 Jan & 22 Jan & Closed \\
\hline
5 & Set up the dev tools & Install Linux / OpenCV & Thomas & 01 Feb & 02 Feb & Closed \\
\hline
6 & Remember stuff to do & Actions table writing & Marion & 05 Feb & 04 Feb & Closed \\
\hline
7 & Git Repository not well organized & Git cleaning & Thomas & 05 Feb & & Open \\
\hline
8 & Compatibility with the other team & Defining subskeletons format & Thierry & 06 Feb & & Open \\
\hline
9 & We love sushi & Sushi eating with the client & Thierry & 13 Feb & & Open \\
\hline
\end{tabular}
\end{center}
\caption{Initial actions table}
\end{table}
\section{Final actions table}
\begin{table}[h!]
\begin{tabular}{|p{0.5cm}|p{3cm}|p{3cm}|p{2cm}|p{1.5cm}|p{1.5cm}|p{1.5cm}|p{1cm}|}
\hline
Id & Origin & Description & Accountable & Target date & Realisation & State & Risk table\\
\hline
1 & Project management & Meeting with the industrial supervisor & Thomas & 15 Jan & 15 Jan & Closed & \\
\hline
2 & Need of specifications & Meeting with the client & Thierry & 22 Jan & 22 Jan & Closed & \\
\hline
3 & Lack of knowledge from the developer & C++ training & Thomas & 22 Jan & 23 Jan & Closed & \\
\hline
4 & Team work \& version management & Git repository creation & Thomas & 05 Feb & 05 Feb & Closed & \\
\hline
5 & Project management & Meeting with the industrial supervisor & Thierry & 21 Jan & 21 Jan & Closed & \\
\hline
6 & Input needed & Taking pictures & Thierry & 22 Jan & 22 Jan & Closed & \\
\hline
7 & Report to write in english & Specifications translation & Emilie & 22 Jan & 22 Jan & Closed & \\
\hline
8 & Set up the dev tools & Install Linux / OpenCV & Thomas & 01 Feb & 02 Feb & Closed & \\
\hline
9 & Need of specifications & Meeting with the client & Thierry & 04 Feb & 04 Feb & Closed & \\
\hline
10 & Remember stuff to do & Actions table writing & Marion & 05 Feb & 04 Feb & Closed & \\
\hline
11 & Project management & Meeting with the industrial supervisor & Marion & 5 Feb & 5 Feb & Closed & \\
\hline
12 & Git Repository not well organized & Git cleaning & Thomas & 05 Feb & 05 Feb & Closed & \\
\hline
13 & Compatibility with the other team & Defining subskeletons format & Thierry & 06 Feb & 09 Feb & CLosed & \\
\hline
14 & Need of specifications & Meeting with the client & Thierry & 11 Feb & 11 Feb & Closed & \\
\hline
15 & The other group did'nt deliver binaries in time & Reschedule planning & Marion & 11 Feb & 11 Feb & Closed & 2 \\
\hline
16 & Binaries provided by he client are not compatible & Speak with the client & Thomas & 11 Feb & & Open & 4 \\
\hline
17 & Client new need & Contact the client by mail to know what we need to do & Thierry & 12 Feb & 12 Feb & Closed & 11 \\
\hline
18 & Project management & Meeting with the industrial supervisor & Amandine & 12 Feb & 12 Feb & Closed & \\
\hline
19 & Integration to do again & discuss with the client & Thierry & 25 Feb & 25 Feb & Closed &\\
\hline
20 & Project management & Meeting with the industrial supervisor & Emilie & 24 Feb & 24 Feb & Closed & \\
\hline
21 & Need of specifications & Meeting with the client & Thierry & 25 Feb & 25 Feb & Closed & \\
\hline
22 & The client need CMake to compile the code & Use CMake compilation & Thomas & 27 Feb & 27 Feb & Closed & \\
\hline
\end{tabular}
\caption{Actions table on February 12th}
\end{table}

9
report/chapters/conclusion.tex Normal file
View File

@@ -0,0 +1,9 @@
\chapter*{Conclusion}
This project was a useful experience for us. It allowed us to better understand the usefulness and efficiency of project management. Having a schedule, and anticipating risks with our risks table allowed us to enter this project more serenely, and to finish it in time.
The main difficulty we had to face happened during the first part of our project. The first part was shared between us and an other "Projet long" team. Some parts were also provided by the client. Unfortunately problems happened with some of his binaries, and the integration had to be abandoned. However the client was still satisfied with the results on this first part, since as a researcher it showed him problems to work on.
The technical part of the project was very interesting, we learned a lot about C++ programming. We obtained good results on the second part of the project, which produces interesting animations.
To conclude, this project was an opportunity for us to apply management on a real project and an interesting technical experience.

47
report/chapters/frontPage.tex Normal file
View File

@@ -0,0 +1,47 @@
\begin{titlepage}
\begin{sffamily}
\begin{center}
~\\[2cm]
\textsc{\LARGE Projet long report}\\[3cm]
% Title
\HRule \\[0.4cm]
{ \huge \bfseries Segmentation, Skeleton and Animation\\[0.4cm] }
\HRule \\[3cm]
\includegraphics[scale=0.5]{img/n7.png}~\\[2cm]
\end{center}
% Author and supervisor
\begin{minipage}{0.5\textwidth}
\begin{flushleft} \large
Thomas \textsc{Forgione}\\
Emilie \textsc{Jalras}\\
Marion \textsc{Lenfant}\\
Thierry \textsc{Malon}\\
Amandine \textsc{Pailloux}\\
\end{flushleft}
\end{minipage}
\begin{minipage}{0.5\textwidth}
\begin{flushright} \large
\emph{Client :} \\
M. Bastien \textsc{Durix}\\
Ms G\'{e}raldine \textsc{Morin}\\
Ms Sylvie \textsc{Chambon}\\
\emph{Industrial supervisor :}\\
Ms R\'{e}gine \textsc{Nigris}
\end{flushright}
\end{minipage}
\vfill
% Bottom of the page
{\large January 19th 2015 -- March 13th 2015}
\end{sffamily}
\end{titlepage}
\tableofcontents
\newpage

10
report/chapters/introManagement.tex Normal file
View File

@@ -0,0 +1,10 @@
\chapter*{Management introduction}
The second important aspect of our project was its management.
Indeed project management will soon be part of our everyday life in our future work. This is why becoming familiar with the management tools studied in class is important and the "Projet Long" was a great opportunity to put it into practice.
We spent our first project week on this part. We tried to define clearly the client need, in order to achieve good product specification. Unfortunately it had to evolve during the first part of our project. We took decisions about the way we would work, for example we decided to use pair programming, and to spend time on our tests before developing. We also worked especially on our risks table to anticipate problems, on our actions table to prevent risks realization, and on our schedule to make sure we would finish on time. \\
We have been updating this documents during the project in order to always anticipate problems.

21
report/chapters/introduction.tex Normal file
View File

@@ -0,0 +1,21 @@
\chapter*{Introduction}
As a conclusion to our studies at the ENSEEIHT, we have been working on our Projet Long. Our project takes part in Bastien Durix thesis which focuses on the extraction of 2D skeletons from pictures and the computation of 3D skeletons from associated 2D skeletons of the same objects, and will also help him on other parts of his approach.
Our subject consisted in realizing animated 3D versions of real 3D objects. We based ourselves on different pictures of objects taken from different perspectives, and use them to reconstruct a 3D version of the object, which we animate.\\
Here is our pipeline :
\begin{itemize}
\item segmentation
\item intrinsic and extrinsic camera calibration
\item points detection and matching
\item skeletonization : cut and match skeleton pieces
\item computing the B-splines
\item meshing the 3D skeleton computed with the 2D skeletons
\item meshing of extremities and junctions
\item choosing connecting points to animate the object
\item animation
\end{itemize}
We were two Projet Long groups working on these subject. The first part was split into two subsections : the other group got to work on the segmentation and B-splines computation, while we were given the matching part and the camera calibration. The second part, concerning the meshing and the animation, was done completely by the two groups.

36
report/chapters/license.tex Normal file
View File

@@ -0,0 +1,36 @@
\chapter{License}
We decided to add a license to our project in order to allow the client using
our project without any problems of properties. We chose the Zlib license
which allow a free-use of our project. You can see our lisence in the listing \ref{license}.\\
\begin{lstlisting}[caption=Zlib license, label=license]
Paella - Copyright (C) 2015 - Thomas FORGIONE, Emilie JALRAS, Marion LENFANT, Thierry MALON, Amandine PAILLOUX
This software is provided 'as-is', without any express or implied warranty.
In no event will the authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it freely,
subject to the following restrictions:
1. The origin of this software must not be misrepresented;
you must not claim that you wrote the original software.
If you use this software in a product, an acknowledgment
in the product documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such,
and must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
External-libraries
------------------
Boost is under the boost software license
Eigen is under the MPL2
OpenCV is under the BSD License
SFML is under the zlib/libpng license
\end{lstlisting}

22
report/chapters/productDescription.tex Normal file
View File

@@ -0,0 +1,22 @@
\chapter{Product description}
Here is the detailed description of the different steps of our project.
We spent time on finding tests before developing, which helped us to avoid some problems and find some errors earlier than we would have otherwise. You can find more information concerning our tests in the attached tests file.
\section{Segmentation, Camera calibration, skeletonization and branches matching}
\input{subsections/skeleton}
\input{subsections/segmentation}
\input{subsections/calibration}
\input{subsections/pointsDetectionAndMatching}
\input{subsections/branchesMatching}
\section{Meshing and animation}
\input{subsections/splines}
\input{subsections/circles}
\input{subsections/extremities}
\input{subsections/junctions}
\input{subsections/animation}

41
report/chapters/productSpecification.tex Normal file
View File

@@ -0,0 +1,41 @@
\chapter{Product specification}
During the first week of our project we tried to clearly define the need of the client and the specifications. In an industrial context it is really fundamental to describe the client expectations as well as possible. It protects us from the client if he suddenly wants something not intended at the beginning or if he is disappointed because he forgot to specify certain problems. But it also gives us some duties toward the client concerning the deliveries for instance. This is why it is really important to take it seriously.
Here is our product specification.
\section{General constraints}
\subsection{Expected deliverables and delivery delay}
We will deliver an archive containing:
\begin{itemize}
\item detailed documentation (commented code and a user manual)
\item source code : camera calibration and points matching, delivered on February 6th,
and then casing and animation on March 13th.
\end{itemize}
\subsection{Client supplies}
The client engages to supply the following elements :
\begin{itemize}
\item programs performing the skeleton extraction
\item mathematical formulas for skeleton casing
\item scientific articles concerning animation
\end{itemize}
\subsection{Imposed technical constraints}
Our technical constraints are as follow :
\begin{itemize}
\item C++ as programming language
\item it is suggested to use the openCV library
\item CMake is suggested as compilation utility
\item used libraries must be portable between Windows and Linux
\end{itemize}
\newpage
\section{Detailed Pipeline}
\begin{figure}[H]
\centering
\includegraphics[scale=0.56]{img/pipeline.png}
\caption{Detailled pipeline}
\end{figure}

69
report/chapters/risksManagement.tex Normal file
View File

@@ -0,0 +1,69 @@
\chapter{Risks management}
In order to anticipate problems and to set a right schedule, we tried to find as many risks as possible. We made our risks table evolve while the project progressed.
\section{Initial risks table}
\bottomcaption{Risks table on 25th February}
\begin{supertabular}{|p{0.5cm}|p{2cm}|p{2cm}|p{1cm}|p{2cm}|p{1.5cm}|p{2cm}|p{2cm}|p{2cm}|p{1.5cm}|}
\hline
Id & Description & risk cause & Proba (1-5) & Consequence & Seriousness (1-5) & Preventive actions & Corrective actions & Risk state \\
\hline
\cellcolor{green} 1 & Bad time estimation & Under estimation of the problem difficulty & 3 & Late delivery & 4 & Time margin of the planning, name a task advancement responsible & Raise the work amount, revise the planning & Open \\
\hline
\cellcolor{green} 2 & The other group does not deliver the deliverables on time & Under estimation of their problem difficulty, last time augmentation of the work amount & 2 & Delay for tests on the 3D part of the skeleton & 3 & Contemplate an other method to test on simple case & Implement ourselves a segmentation method based on simple threshold & Open \\
\hline
\cellcolor{green} 3 & The other group delivers wrong outputs & Bad comprehension of the subject & 3 & Tests do not work correctly & 1 & Find en agreement on the format & Develop a transition function & Open \\
\hline
\cellcolor{green} 4 & Binaries provided by the client are not compatible & Systems complexity & 4 & We can not carry on with the pipeline & 4 & Discuss with the client the provided binary & Emulate the system allowing the use of the binaries & Open \\
\hline
\cellcolor{green} 5 & Fragile harmony inside the group & Different uses for project management and programmation & 1 & Tensions, bad ambiance, intense stress & 5 & Name a cohesion responsible & Organize a mediation beetween the two parties & Open \\
\hline
\cellcolor{green} 6 & Bad understanding with the other group & A bancal division of the project might bring tensions & 2 & Difficulty to manage shared parts & 3 & Bring a present as a sign of sympathy & Come to a compromise & Open \\
\hline
\cellcolor{green} 7 & A group member is absent during a certain period of time & Illness, event & 5 & Someone's absence & 1 & Put in place teleworking solutions & Planning adaptation & Open \\
\hline
\cellcolor{green} 8 & Production of unreliable, unmaintainable and illegible code & Lack of skills with the used technology & 4 & Lack of time, bad quality, need to reprogram & 3 & C++ formation by a technical expert & Call of the expert & Open \\
\hline
\cellcolor{green} 9 & Need to access urgently to a deleted resource & Utilization of a suppression command, material crash & 2 & Lack of time, need to reprogram & 5 & Use github & Use of recuperation technology on long and complicated files & Open \\
\hline
\cellcolor{green} 10 & Pictures unadapted & Client not satisfied of the pictures & 4 & Wasting time & 2 & Defined the conditions of the shoot with the client more precisely & Be aware of client expectations and taking again the picture & Open \\
\hline
\end{supertabular}
\section{Final risks table}
In the table below you can find the risks state in the end of the project.\\
\bottomcaption{Risks table on 25th February}
\begin{supertabular}{|p{0.5cm}|p{2cm}|p{2cm}|p{1cm}|p{2cm}|p{1.5cm}|p{2cm}|p{2cm}|p{2cm}|p{1.5cm}|}
\hline
Id & Description & risk cause & Proba (1-5) & Consequence & Seriousness (1-5) & Preventive actions & Corrective actions & Risk state \\
\hline
\cellcolor{green} 1 & Bad time estimation & Under estimation of the problem difficulty & 3 & Late delivery & 4 & Time margin of the planning, name a task advancement responsible & Raise the work amount, revise the planning & Open \\
\hline
\cellcolor{yellow} 2 & The other group does not deliver the deliverables on time & Under estimation of their problem difficulty, last time augmentation of the work amount & 2 & Delay for tests on the 3D part of the skeleton & 3 & Contemplate an other method to test on simple case & Implement ourselves a segmentation method based on simple threshold & Open \\
\hline
\cellcolor{green} 3 & The other group delivers wrong outputs & Bad comprehension of the subject & 3 & Tests do not work correctly & 1 & Find en agreement on the format & Develop a transition function & Open \\
\hline
\cellcolor{yellow} 4 & Binaries provided by the client are not compatible & Systems complexity & 4 & We can not carry on with the pipeline & 4 & Discuss with the client the provided binary & Emulate the system allowing the use of the binaries & Open \\
\hline
\cellcolor{green} 5 & Fragile harmony inside the group & Different uses for project management and programmation & 1 & Tensions, bad ambiance, intense stress & 5 & Name a cohesion responsible & Organize a mediation beetween the two parties & Open \\
\hline
\cellcolor{green} 6 & Bad understanding with the other group & A bancal division of the project might bring tensions & 2 & Difficulty to manage shared parts & 3 & Bring a present as a sign of sympathy & Come to a compromise & Open \\
\hline
\cellcolor{green} 7 & A group member is absent during a certain period of time & Illness, event & 5 & Someone's absence & 1 & Put in place teleworking solutions & Planning adaptation & Open \\
\hline
\cellcolor{green} 8 & Production of unreliable, unmaintainable and illegible code & Lack of skills with the used technology & 4 & Lack of time, bad quality, need to reprogram & 3 & C++ formation by a technical expert & Call of the expert & Closed \\
\hline
\cellcolor{green} 9 & Need to access urgently to a deleted resource & Utilization of a suppression command, material crash & 2 & Lack of time, need to reprogram & 5 & Use github & Use of recuperation technology on long and complicated files & Open \\
\hline
\cellcolor{yellow} 10 & Pictures unadapted & Client not satisfied of the pictures & 4 & Wasting time & 2 & Defined the conditions of the shoot with the client more precisely & Be aware of client expectations and taking again the picture & Open \\
\hline
\cellcolor{green} 11 & New task to do & Client new needs & 4 & Late delivery & 4 & Add margin in planning & change planning and contact the client to negociate about this task & Closed \\
\hline
\cellcolor{green} 12 & Integration not cancelled & Client changes his mind and wants again the integration & 2 & Late delivery & 4 & discuss with the client & change planning & Open \\
\hline
\cellcolor{green} 13 & members of the group get remedial classes & bad results at the exams & 2 & member absent & 2 & add margin & change planning & Open \\
\hline
\end{supertabular}

29
report/chapters/schedule.tex Normal file
View File

@@ -0,0 +1,29 @@
\chapter{Schedule}
Thanks to our risks table we had anticipated the possibility of a schedule modification due to our interaction with the other group and with the client binaries. We had kept one week as security, and finally had to use it before the integration period.
\section{Initial schedule}
We spent our first week on the project management, like doing this schedule. \\
At the beginning we did a detailed schedule for the first part of the project, but not for the second part of the project. We just assigned 2 weeks and half to the meshing, and one week to the animation.
\begin{figure}[H]
\begin{center}
\includegraphics[scale=0.5]{img/initialSchedule}
\caption{\label{initialSchedule} Initial Schedule}
\end{center}
\end{figure}
\section{Final schedule}
Before starting the second part of the project we did the detailed schedule of this part, which you can see below.
The integration with the other group was abandoned, as you can see.
We also decided to finally start the report before finishing the second part.
\begin{figure}[H]
\begin{center}
\includegraphics[scale=0.5]{img/finalSchedule}
\caption{\label{finalSchedule} Final Schedule}
\end{center}
\end{figure}

6
report/chapters/technicalConclusion.tex Normal file
View File

@@ -0,0 +1,6 @@
\chapter*{Conclusion of the technical part}
The technical part of this project taught us a lot, especially in C++ programming.
Our knowledge from the multimedia specialization was very helpful, as well in the image analysis part as in the meshes and animation part.
During this project we also tried to think of tests before developing, which helped us in finding errors early, and anticipate problems.

4
report/chapters/tests.tex Normal file
View File

@@ -0,0 +1,4 @@
\chapter{Tests}
You can find our tests in the attached folder.
We reported the results obtained with different parameters or methods, and explained our choices. We also tackle the limits of our different programs.