-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathevaluation.html
More file actions
173 lines (143 loc) · 10.4 KB
/
evaluation.html
File metadata and controls
173 lines (143 loc) · 10.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
<!DOCTYPE HTML>
<html>
<head>
<title>3D Pyramid Rendering - Evaluation</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
<link rel="stylesheet" href="assets/css/main.css" />
</head>
<body class="is-preload">
<!-- Wrapper -->
<div id="wrapper">
<!-- Main -->
<div id="main">
<div class="inner">
<!-- Header -->
<header id="header">
<a href="index.html" class="logo"><strong>Report</strong></a>
</header>
<!-- Content -->
<section>
<header class="main">
<h1>Evaluation</h1>
</header>
<h2>MoSCoW Achievements List</h2>
<span class="image main"><img src="images/evaluation_moscow.png" alt="" /></span>
<hr class="major" />
<h2>Known Bugs</h2>
<p>As our project does not have a large amount of code and has a clear functionality, we do not have a list of known bugs. However, there are some specific requirements that need to be fulfilled in order for our system to function to the fullest extent. If these requirements are not met, it can lead to errors during the composing process or incomplete holograms being projected. </p>
<span class="image main"><img src="images/system_requirements.png" alt="" /></span>
<hr class="major" />
<h2>Individual Contribution Table</h2>
<span class="image main"><img src="images/individual_contribution.png" alt="" /></span>
<hr class="major" />
<h2>Critical evaluation of the project</h2>
<h5>Functionality</h5>
<p>We have implemented all the Must Haves and the majority of optional features demanded from our clients. We managed to keep our implementation clear and simple, primarily using the OpenCV library. The libraries used in the project were reported to our clients and their approval was received before development. Its features mainly include image processing, video capture and analysis, as defined in our requirements list. </p>
<p>
We have implemented all the Must Haves and the majority of optional features demanded from our clients. We managed to keep our implementation clear and simple, primarily using the OpenCV library. The libraries used in the project were reported to our clients and their approval was received before development. Its features mainly include image processing, video capture and analysis, as defined in our requirements list.
</p>
<p>
To access the functionalities of our media editor and produce a synchronised video stream successfully, input videos need to follow specific requirements as defined in Table #3. We explain in detail every functionality, as well as the input and output options in the README file on our GitHub repository to ensure that the users understand the system and utilize it as intended.
</p>
<p>
Due to the logistical issues with the webcam, we could not analyse our live webcam sources as expected. However, we are confident that the 3D video composition would happen successfully as long as the requirements listed in Table #3 are followed.
</p>
<h5>Stability</h5>
<p>
We tested the stability of our project on different computers with different operating systems, both on Windows and Mac OS. The Python script designed for the project does not show any error or warning messages in either case. Therefore, stability is guaranteed. Moreover, our system was implemented using Python and uploaded on GitHub for distribution. Anyone can clone the repository on their device and utilize the functionalities without complex deployment processes.
</p>
<h5>Efficiency </h5>
<p>Based on our testing, our 3D media editor runs smoothly and quickly. The pre-recorded input video streams may take some time to be downloaded onto the device, however the actual composition and synchronization process happens almost instantly</p>
<h5>Compatibility</h5>
<p>
Since our project is built using Python, a user with Python and the libraries such as OpenCV and pyvirtualcam downloaded can run our script on their device without trouble. However, this pattern of design means that it could not be accessed on a phone independently. The videos have to be synchronised on the computer before they can be redirected through OBS onto other devices to be projected onto a pyramid.
</p>
<h5>Maintainability</h5>
<p>
The codebase of our project is simple and implemented in a well-structured format. The code is easy to maintain and extendable for further development. Additionally, the script has been documented thoroughly and a detailed user manual is provided in the form of a README file on the repository. Moreover, all the features in our system were implemented using open-source libraries and platforms, meaning that there is zero cost for usage as well as minimal legal concerns.
</p>
<h5>Project Management</h5>
<p>
We have all experienced a very difficult year, working remotely for the entire academic year without face-to-face communications. It was especially challenging to carry out a group project of this scale remotely. However, through the use of many online communication tools, we were able to collaborate well and managed to deliver a profound solution. Below is a summary of what we did well and what could be improved.
</p>
<ul>
<li>We made plans ahead, which maximised our productivity and avoided any procrastination or uneven distribution of tasks. We would set up weekly milestones, but sometimes readjust them if needed in order to keep the workload manageable, as long as it stayed reasonable within the overall development timeline. </li>
<li>We communicated effectively during the developing process as a group, even though we were all in different timezones. We held meetings at least once a week, making sure everyone was updated on the overall status of the project and any individual progress. </li>
<li>We clearly communicated our decisions and any difficulties we were having with our clients to avoid any misunderstanding. </li>
<li>When faced with challenges that could not be resolved by ourselves, we asked our TA and clients for help, avoiding the sunk cost effect. However, we failed to solve the logistical issues of the webcams not being delivered. We should have continuously contacted the people that could help without waiting for long periods of time for an email reply. </li>
<li>We divided our tasks equitably, based on the individual strengths and weaknesses. When a member was having trouble completing an individually assigned task, the group collectively worked on it.</li>
</ul>
<hr class="major" />
<h2>Future work</h2>
<p>Below is a list of additional features that we would like to implement in the future to improve our system: </p>
<ul>
<li>
Test the script with live video input from webcams. Since the logistical issues with the webcams affected our development continuously, we decided to test our script with Maya. If we received the necessary technology, we would extend the current features to work more rigorously with live webcam data.
</li>
<li>
Improve the background segmentation implementation. If we had more time, instead of assuming the presence of a greenscreen, we would implement a real-time background subtraction mechanism that can isolate the subject in a frame. This would make our system more user-friendly as the users would not have to use greenscreens.
</li>
<li>
A user interface could be implemented to improve the user experience and lower the complexity of our system from the users’ perspective.
</li>
<li>
If we could go back on campus, our system can be tested on a more rigorous holographic device in the UCL Engineering building instead of the portable miniature pyramid that we used to experiment with. This would allow for the creation of more complex visuals as well as improve the durability of our system.
</li>
</ul>
</section>
</div>
</div>
<!-- Sidebar -->
<div id="sidebar">
<div class="inner">
<!-- Search -->
<section id="search" class="alt">
<form method="post" action="#">
<input type="text" name="query" id="query" placeholder="Search" />
</form>
</section>
<!-- Menu -->
<nav id="menu">
<header class="major">
<h2>Menu</h2>
</header>
<ul>
<li><a href="index.html">Homepage</a></li>
<li><a href="requirements.html">Requirements</a></li>
<li><a href="research.html">Research</a></li>
<li><a href="algorithms.html">Algorithms</a></li>
<li><a href="design.html">Design</a></li>
<li><a href="implementation.html">Implementation</a></li>
<li><a href="testing.html">Testing</a></li>
<li><a href="evaluation.html">Evaluation</a></li>
<li><a href="appendices.html">Appendices</a></li>
</ul>
</nav>
<!-- Section -->
<section>
<header class="major">
<h2>Get in touch</h2>
</header>
<ul class="contact">
<li class="icon solid fa-envelope"><a href="#">andrei.bubutanu.19@ucl.ac.uk</a></li>
<li class="icon solid fa-envelope"><a href="#">yong.cho.17@ucl.ac.uk</a></li>
<li class="icon solid fa-envelope"><a href="#">coco.liu.19@ucl.ac.uk</a></li>
</ul>
</section>
<!-- Footer -->
<footer id="footer">
<p class="copyright">© University College London, IBM. All rights reserved. Design: Team 3</p>
</footer>
</div>
</div>
</div>
</div>
<!-- Scripts -->
<script src="assets/js/jquery.min.js"></script>
<script src="assets/js/browser.min.js"></script>
<script src="assets/js/breakpoints.min.js"></script>
<script src="assets/js/util.js"></script>
<script src="assets/js/main.js"></script>
</body>
</html>