Week 35: 18th May - 22nd May: Final Push

Thats everything done and handed in. Now for the showcase.

Week 34: 11th May - 17th May: Focus Dissertation!!

Now the exam is finished with, I am hoping to get the dissertation completely finsihed all tweaks and everything for monday. Unfortunately I have not been able to send Dr Lucas a full first draft as they were not finished in time to send all at once. However, I have sent him the methodology as I said before and today I sent him the realated work section. Hopefully, they will be fine with not much to change. I already have comments back for the methodology section.

Week34: 11th May - 17th May: Dissertation and Maths

Well the Maths and AI exam is this week so the dissertation is taking a little backseat. However, so far the introduction, some of the lit review, the background and methodology sections have been done. The background knowledge and methodology sections were sent to Dr Lucas for a look over and I have some good notes back. As soon as the exam is over, I will be getting on with that. First thing I will do is finish the lit review so that I can send it to Lucas for a quick look over. After that, the plan is to fix the problems that have been highlighted and then get on with finishing it all.

Week 33: 4th May - 10th May: Video Demonstration

Below is the video demo of my application. It did not work in the presentation but I thought I would add it into here instead.

Of course if still hasn't worked but I will keep trying

Week 33: 4th May - 10th May: Presentation and More Work

This week, I had my presentation. Below is the slides of the presentation I gave on Tuesday.

The remainder of the week I have been writing the dissertation. So far there is 1500 odd words and everything else is planned out. Now its just a matter of writing. While remembering to sudy for the exam

Week 32: 27th April - 3rd May: Where I am now.

OK well, where to start???? The programming is done finally. Not as much as planned. Not as impressive as planned. Not as much techniques explored. However, it is at a good stage to hand in (hopefully). although it is fairly simple and unimpressive looking, I am very very proud of it as I have never been that confident on my programming yet, I completed the programming stage of this project near enough all by myself. The translation problem still exists, however, Dr Lucas got back to my email and told me that it needs to be wrapped up now and unless there is an obvious problem to the translation problem, I am just to leave it there.

On the dissertation side of things, progress is still slow however, some of it has been written. This week coming is the presentations and to say I am completely dreading it, is a massive understatement. I hate talking in front of people but I suppose it is an easy 10% of the module. Just hope I do not fail too badly. Soon, I will add the presentation slides on to this blog and perhaps my script.

Meanwhile, major work needs to be done to the dissertation and revision for the maths/AI exam will need to start soon.

Week 32: 27th April - 3rd May: Fun Programming Morning

Following my earlier list, I have completely so far two out of the three tasks.

• 10.43am - Finished first task- now the program resets the simulation with different rotated plane and the ball back at starting position.
• 10.56am - I have randomised the velocity of the ball to float values in between -5 and 5. the position was also randomised initially this way however, sometimes it was rendered below the plane and although this is easy enough to fix (i.e. place some restrictions) i decided that exactly (0, 10, 0) is the perfect coordinates for it as it will always hit the plane with a good couple of bounces at least. this may change once the translation comes into play. this is what is next on the to do list.
• 12.10pm - OK, the translation is set in the code however, I'm not sure whether to use it or not as the majority of times, the ball never hits the plane. I think I may have to speak to Dr Lucas about this at some point. I could place the initial position of the ball to be exactly 10 above the planes position or give the coordinates of the particle the same translation. Again, this could work, however, more adjustment is needed for the camera too. i shall try this now.
• 12.46pm - It is now mucking up the collision detection. Therefore, an email has been sent to Dr Lucas, updating him on my progress and the problem I have had today. He is not in today but hopefully I will get a reply tomorrow. It has been commented out in the code in the meantime. I have also added code to make sure that when the ball falls below -100 in the y axis, that it stops the simulation, puts the ball back to its original position and then starts the simulation again with new velocities.