projectalex.github.io/index.html at master · ProjectAlex/projectalex.github.io · GitHub

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
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
<!doctype html>
<html lang="en">

<head>
<meta charset="utf-8">

<title>Amazon Project</title>

<meta name="description" content="A framework for easily creating beautiful presentations using HTML">
<meta name="author" content="Hakim El Hattab">

<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />

<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">

<link rel="stylesheet" href="css/reveal.min.css">
<link rel="stylesheet" href="css/theme/default.css" id="theme">

<!-- For syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">

<!-- If the query includes 'print-pdf', include the PDF print sheet -->
<script>
if( window.location.search.match( /print-pdf/gi ) ) {
    var link = document.createElement( 'link' );
    link.rel = 'stylesheet';
    link.type = 'text/css';
    link.href = 'css/print/pdf.css';
    document.getElementsByTagName( 'head' )[0].appendChild( link );
}
</script>

<!--[if lt IE 9]>
        <script src="lib/js/html5shiv.js"></script>
        <![endif]-->
</head>

<body>

<div class="reveal">

    <!-- Any section element inside of this container is displayed as a slide -->
    <div class="slides">
            <section>
                <h1>Amazon <br /> Project</h1>
                <h3>Gaming : board games with shared big screen and devices</h3>
                <p>
                <small>Prashant Anantharaman - 4th yr
                    <br />S Surendhar- 4th yr
                    <br />M Mithul - 3rd yr
                    <br />Mithun Chakaravarrti  - 3rd yr
                    <br />  Navnith Ramkrishnan - 3rd yr
                    <br>
                    <br />Faculty Mentor : Dr. Rajeswari Sridhar, Asst. Professor (Sr), <br />Dept. of Computer Science and Engg.
                </small>
                </p>
            </section>

        <section>
            <section>
                <h1>Topic <br />Elaboration</h1>
            </section>
            <section>
                <h2>Why this topic?</h2>
                <ul>
                    <li>People nowadays are stuck to their mobiles and other handhelds, reducing face to face interaction between peers even when physically present at the same spot.</li>
                    <li>Since people nowadays are addicted to their gadgets and don’t let go of themselves, we aim at using these very gadgets to get them closer. </li>
                    <li>We want to bring back the concept of these old board games and spruce it up with digital features. </li>
                </ul>
            </section>
            <section>
                <h2>Literature Survey</h2>
                <ul>
                    <li>This application also educationally influences its users. We are incorporating the principles stated by Joshua H. Barnett, Leanna Archambault in November 2010. </li>
                    <li>We are planning to modify the difficulty and genre of questions based on the paper "AI for Dynamic Difficulty Adjustment in Games" by Robin Hunicke, Vernell Chapman, Northwestern University,  using a probabalistic method for representing and reasoning uncertainty in games</li>
                </ul>
            </section>
            <section>
                <h2>Literature Survey (Contd.)</h2>
                <li>Multiplayer Game capacity can be increased using the optimisation methods suggested by Hanghang Qi and David Malone, University of Ireland in "802.11 Wireless LAN Multiplayer Game Capacity and Optimization". In 802.11e wireless networks, with proper configuration of TXOP at the game server and access points, the network can be improved to support upto 15 players [A TXOP(Transmit Opportunity) is a bounded time interval during which a station can send as many frames as possible].</li>
            </section>

            <section>
                <h2>The Game</h2>
                <ul>
                    <li>The game is an adaptation of "Snakes and Ladders" combined with some features of "Scene It"</li>
                    <li>The game can be played by as many players as we want. For now we want to limit it to the number of people in our group, that is 5</li>
                    <li>Its a turn based game. You advance only when its your turn.</li>
                    <li>A question appears on the screen, and all the participants are supposed to answer the question</li>
                    <li>Only the person whose turn it was advances, opponents get to limit the number of positions the player can advance.</li>
                </ul>
            </section>
            <section>
                <h3>The Game (Contd.)</h3>
                <ul>
                    <li>The question will be a combination of pictures, videos, audio clips in various topics to exploit the fact that the game is digital.</li>
                    <li>The first person to reach the finish point is declared winner.</li>
                    <li>Each square has a different genre of question assigned to it. So the square you are in determines the question you will be asked in the next turn.</li>
                    <li>The system has a database of questions, and we train the system by answering the questions, enabling it to identify the difficulty level.</li>
                </ul>
            </section>
            <section>
                <h3>For example</h3>
                <ul>
                    <li>For a 5 player game if 3 people answer the question quicker than the player playing his hand he moves 2 spaces ahead, or if he is the first to answer he moves 5 spaces ahead. </li>
                    <li>This keeps all the players engrossed as they are constantly interacting with the game.</li>
                </ul>
            </section>
            <section>
                <h2>Design</h2>
                <ul>
                    <li>The board appears on the screen.</li>
                    <li>The current player in turn is displayed on the right at the top, whereas points of the opponents appear on the right corner.</li>
                    <li>The question appears down along with its options, and this appears on the devices as well.</li>
                    <li>The options can be selected only on the phone</li>
                </ul>
            </section>
            <section>
                <img src="sketch1.jpg" alt="" />
            </section>
            <section>
                <img src="sketch2.jpg" alt="" />
            </section>
        </section>
        <section>

            <section data-background="rpi.jpg">
                <h1 style="color:white">Implementation</h1>
            </section>
            <section>
                <h2>Implementation</h2>
                <ul>
                    <li>The Raspberry Pi runs a Server running Java </li>
                    <li>We have a centralized corpus of questions running on a VPS.</li>
                    <li>The pi handles displaying the Board UI to the Screen</li>
                    <li>The pi also fetches questions from the VPS.</li>
                    <li>The pi sends questions, options and scores to the mobile through sockets. </li>
                </ul>
            </section>
            <section>
                <h2>Implementation (Contd.)</h2>
                <ul>
                    <li>The client would be a native android app. (Could be extended to other platforms later).</li>
                    <li>The android app displays the questions, options, and the user needs to pick the answer there.</li>
                    <li>The communication between the Raspberry pi and the android app would happen through sockets.</li>
                </ul>
            </section>

            <section>
                <h2>Implementation<br />(Block Diagrams)</h2>
            </section>
            <section data-transition="linear" data-background-transition="slide">
                <img src="Overall-amazon.jpg" alt="" height="700px" width="600px" />
            </section>
            <section>
            <h5>Detailed Block Diagram</h5>
                <img src="GameClients-amazon.jpg" alt="" />
            </section>
            <section>
                <img src="ServerAPI-amazon.jpg" alt="" />
            </section>
            <section>
                <img src="QuestionCorpus-amazon.jpg" alt="" />
            </section>
            <section>
                <img src="Game-ServerSide-amazon.jpg" alt="" />
            </section>


            <section data-transition="linear" data-background-transition="slide">
                <h2>Existing Solutions and Problems</h2>
                <ul>
                    <li>Google's Chromecast is not opensource and thus does not give enough flexibility.
                    <li>PiCast runs on a raspberry Pi and allows devices to content stream over WiFi. It is priced similar to the chromecast making it economically feasible. Devices communicate with PiCast using an API. It supports only Videos, Audio, Images like Chromecast</li>
                    <li>Another device we considered was Roku Stick which uses DLNA to stream content and can be plugged into any HDMI compatible TV.</li>
                </ul>
            </section>
            <section>
                <h2>Challenges we face</h2>
                <ul>
                    <li>Speed - The connection speed may cause problems during gameplay.</li>
                    <li>Maximum number of players the server can handle will be a limiting factor.</li>
                    <li>Should be interconnected using WiFi</li>
                    <li>Fluctuations in speed and connections</li>
                </ul>
            </section>
            <section>
                <h2>How do we plan to tackle <br />the challenges</h2>
                <ul>
                    <li>The game must be tweaked according to the connection speed that is achievable.</li>
                    <li>The upper limit for number of players should be set based on the servers capability and the game that is chosen</li>
                    <li>The app must be able to work under a wobbly connection allowing players to reconnect and continue and not get kicked out</li>
                </ul>
            </section>
        </section>
        <section>
            <h2>References</h2>
            <ol>
                <li><a href="http://www.editlib.org/p/65614/">http://www.editlib.org/p/65614/</a> research paper on multiplayer gaming</li>
                <li><a href="http://www.hamilton.ie/dwmalone/netgames09.pdf">http://www.hamilton.ie/dwmalone/netgames09.pdf</a> a research paper on how Multiplayer game capacity can be optimised.</li>
                <li><a href="http://cs.northwestern.edu/~hunicke/pubs/Hamlet.pdf">http://cs.northwestern.edu/~hunicke/pubs/Hamlet.pdf</a> a research paper on how difficulty can be modified dynamically in games</li>
                <li><a href="http://web.cs.wpi.edu/~claypool/nossdav06/pdf/winter.pdf">http://web.cs.wpi.edu/~claypool/nossdav06/pdf/winter.pdf</a>a research paper on a A Hybrid Thin-Client protocol for Interactive Gaming Applications</li>
            </ol>
        </section>
        <section>
            <h1>Questions?</h1>
        </section>
        <section>
            <h1>Thank you</h1>
        </section>
    </div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.min.js"></script>

<script>

// Full list of configuration options available here:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,

theme: Reveal.getQueryHash().theme, // available themes are in /css/theme
transition: Reveal.getQueryHash().transition || 'default', // default/cube/page/concave/zoom/linear/fade/none

// Parallax scrolling
// parallaxBackgroundImage: 'https://s3.amazonaws.com/hakim-static/reveal-js/reveal-parallax-1.jpg',
// parallaxBackgroundSize: '2100px 900px',

// Optional libraries used to extend on reveal.js
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true, condition: function() { return !!document.body.classList; } },
{ src: 'plugin/notes/notes.js', async: true, condition: function() { return !!document.body.classList; } }
]
});

</script>

</body>
</html>