dash-3d-tmp/phd
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Thierry's fix

Browse Source
This commit is contained in:
Thomas Forgione
2019-10-11 11:06:22 +02:00
parent beee676839
commit bd7bc84eee
19 changed files with 36 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/conclusion/contributions.tex
View File

@@ -5,7 +5,7 @@ In this thesis, we have presented three main contributions.
\paragraph{}
First, we set up a basic system allowing 3D navigation and 3D content streaming.
We developped a navigation aid in the form of 3D bookmarks, and we conducted a user study to analyse its impact on navigation and streaming.
On one hand, we concluded that navigation aid help people navigating in a scene, they can perform tasks faster and more easily.
On one hand, we concluded that navigation aid helps people navigating in a scene, they can perform tasks faster and more easily.
On the other hand, we showed that this help in 3D navigation comes at the cost of a negative impact for the quality of service: since users navigate faster, they require more data to perform in the same way.
However, we also showed that this cost is not a fatality\todo{not sure of that sentence, we could also say \emph{is not inevitable}}.
Due to the prior knowledge we have about bookmarks, we are able to precompute data offline that we are then able to use when users click on bookmarks to improve the quality of service.

6
src/conclusion/future-work.tex
View File

@@ -1,17 +1,17 @@
\fresh{}
\section{Future work}
After all this, there is still plenty of avenues for improving our streaming system.
After all this, we have three major perspectives for future work.
\subsection{Semantic information}
In all of this work, no attention has been paid towards semantic.
Our content preparation does not take anything like that into account, and our adaptation sets and segments surely will cut data that could be grouped semantically.
Having semantic support can help us have a better structure for our content: we know that displaying half a building will lead to low quality of experience.
Having semantic support can help us having a better structure for our content: we know that displaying half a building will lead to low quality of experience.
Moreover, semantic data could also change the utilities we have been defining for our segments: some data can be marked as more important than other and this can be taken into account in our utilities.
\subsection{Compression / multi resolution for geometry}
In all of this work, no attention has been paid towards geometry compression or multi-resolution.
Geometry data is transmitted as OBJ files which is the worst possible format for transmission, and compression could drastically increase the quality of experience.
Geometry data is transmitted as OBJ files which mostly consist in ASCII encoded numbers, which is terrible for transmission, and compression could drastically increase the quality of experience.
Being able to support multi resolution geometry would be even better, and even if performing multi resolution on a large and heterogeneous scene just like ours is difficult, we have no doubt that semantic information can help this task.
\subsection{Performance optimization}