Showing posts with label API. Show all posts
Showing posts with label API. Show all posts

Monday, 9 January 2012

DAT203 - Infrastructure

In every city, there is an infrastructure - London has one, Birmingham has one, Manchester has one, even our own Plymouth has one as well. However, the infrastructure of Plymouth isn't as well developed as other competing cities around the UK, in fact, pretty much every major city in developed Europe. In today's lecture, we was shown many examples of urban infrastructure, both in fiction and reality, of which we were then introduced to our assignment, a joint project with Plymouth City Council.

The reason for Plymouth's slow development dates back to after World War 2, when the city was bombed by the Nazi Luftwaffe. The city had more bombs dropped on it than Coventry, and as a result, most of the city had to be rebuilt from the ground up. in 1943, Sir Patrick Abercrombie drew up a plan for redeveloping the city, and was then enacted after World War 2, with 20,000 new houses built by the 1960s, and a new Civic high-rise completed during that same period. 

The city was designed with the automobile in mind, which has resulted in an American-influenced infrastructure and architecture, which was typical of many American cities at the time. In addition, it was also fitting for Plymouth, as it was a city that has historical links with the Plymouth in the United States, of which the Pilgrim Fathers discovered, but following a trend of pedestrianisation in the 1980s and the 1990s, the main roads going through the city centre's main shopping districts were paved over, and this has resulted in an important piece of infrastructure being severed or severely curtailed. 

In addition, the ills of the existing transport infrastructure were then felt in the 2000s and the 2010s as other comparable cities were then becoming fully developed, and with the recovery from the global financial crisis still underway, this has now come more important than ever, with the airport now closed and better railway links being needed to help boost growth in city commerce and to increase the speed of redevelopment.

Wednesday, 19 October 2011

DAT206: Group project using Kinect

In our group project, we are using the Kinect with OpenKinect, which is an open community-driven API that is used to access the Kinect's sensors and camera, and also allows Processing to control the tilt. The Kinect was only just released last year, so for the first time in IDAT, we will be using the many capabilities that have never before been exploited in a project.

Originally meant as an interactive peripheral for the Xbox 360, in response to Sony's PlayStation Move and the incumbent Wiimote, many opportunities became true after Spanish hacker Héctor Martín Cantero managed to create the first open-source driver for the device in response to an Adafruit competition bounty. The OpenKinect project was founded after Héctor posted the hack on Github, and is available in various programming languages; the version we're using is the Processing variant, which includes the necessary libraries in order to access the API. OpenKinect is in continuous development, and many more programming languages are being added as development progresses.

Our game will be themed on zombie survival, and the goal of the game is to survive the whole duration of the game without getting touched by zombies, and defend yourself against them. We are going to try and fuse two Kinect devices to create a 3D world, and use the tracking features in the OpenKinect API to detect the player's movement and interactions against the zombies, and to detect collisions that would result in the player's heath being subtracted. We are also going to use an object to act as the gun, which the player uses against the zombies. The Kinect will detect the player's interaction with the object, and whenever the player pulls the trigger, it fires the gun, and if the gun is aimed well at the zombies, the zombie then gets killed.

Popular Posts