Robot Observations!

Lesson Aims:

Follow designs to build a system.

Create a program to meet requirements.

Test a solution.

Consider suitable improvements that could be made to a system.

A	M	S	Learning Aims (what the learner will be able to do)
/			Build a system with 4 sensors
/			Consider how you will make your code readable
/			Consider how you will make your code good quality
/			Use a detailed test table
	/		Identify the advantage of version control
		/	Write a program to meet requirements
	/		Identify improvements your system could have
A	M	S	Learning Objectives (skills, knowledge & attitudes)
/			Be able to connect lego parts together
/			Create a robust robot following a design.
/			Consider accessibility when building a robot
/			Carryout suitable tests
	/		Consider weaknesses in a design/solution

Hello!

Today has been stressful and frustrating. I had spent almost the entire day on re-tuning my robot again and again, this has been a struggle due to it working yesterday and not today, bizarre.

A strength of today was being able to test my robot clearly, identify where it goes wrong and attempt to improve it. John has also supported and assisted me in creating a failsafe, which worked slightly, but then I scrapped it and decided to make the robot go straight as the robot tend to go off course on the right side, correction will make it go left and then the motors will go forward -- however the issue is that the robot does not go out of failsafe when the robot's light sensor lands on the actual white line, and I cannot understand why as it keeps going straight and past it, these were my weaknesses. Another issue I have is that the motor's speed change, sometimes it's quicker and sometimes it's slower, I blame the battery but it must also be my code.

At the end of the day, I got my robot observed. I had made sure it goes round a few times before I show it to John, however when he actually looks that's when the robot messes up. I refer to my code and I cannot comprehend what causes these distortions, and therefore experimented with the values. Eventually, the robot almost managed to go round the course -- it was very very close but the failsafe set off and like again, the above issue took place where it will constantly loops despite it being in a void.

Nonetheless, the day had been tough but what's done is done. I am looking forward to my weekend and getting back to work on Monday!

More Robot Stuff!

Hello!

Just updating on what I've been up to. Essentially, I won't be here Friday, therefore I have came in yesterday and today to catch up on any work and to get ahead.

Yesterday and today has been a straight forward process: program robot, test robot, clean up the code and complete any resubmissions. Now it's the end of Wednesday, I have been able to do that.

A strength of today was being able to complete all my work and get my robot following the line properly. A weakness was not being able to understand how to do a failsafe on my own at all. Another factor that changes my robot's movements are the battery life, which dictates the power in the motor. A slight difference can make a huge impact, I experienced.

For tomorrow, I will get it observed after a few certain tests, then complete the improvement and evaluation document so I can submit and 

Building & Programming NXT Lego Robots

Lesson Aims:

Follow designs to build a system.
Create a program to meet requirements.

Hello!

To reflect on Friday, I came in with Adam M later the day and cracked on with building our robot. We encountered various issues with the build, became frustrated and decided to take everything apart -- including our beloved base of the robot. We wanted to stick to the original design and therefore we decided to spend longer building trial and error. At the end of the day, Adam left whereas I stayed an hour later and had John nice enough to help me! This was great and I watched how he built the robot, this helped me today and was a strength. 

As starter, John did a warm up to let us remember the different factors for readability and quality. This was relatively easy as I understand what makes a code simple to understand. However, programming the robot is obviously the challenge and the difficult part.

Back to today, once again John wasted no time and allowed us to get on with work. I firstly built the robot with Adam M; all was left was to tidy the wires (cable management), add the sensors and make sure it was robust in terms of sturdiness. An hour or so later, this was a success. A strength was being able to build the robot as a pair. A weakness was struggling and stressing.

Next, John showed us examples of how to lay out a test table when we test our robots with our own codes. One in particular caught my attention and therefore I based my layout on that. There, I created a table for the different objectives I am testing, a tab for objectives as well as the marks/tasks and a version history. I did all of this on Google Excel Spreadsheets for a change. 

I then began to code and dedicated my entire day on it. By the end, I have managed to complete 4 out of 7 objectives with three remaining - these ones are either uncompleted due to not having e.g. an obstacle and I have planned to work on this by coming in tomorrow. The biggest issues I have faced today would be on the programming side - such as forgetting a line or accidentally missing parenthesis... common issues.

As for reflection, Adam has been my inspiration because he has managed to get his robot and testing to a good standard -- I had to do more testing due to having more errors but nonetheless I have managed to catch up to him and get the robot working. Right now, it can follow a straight line, listen to a clap and spin 540 then follow the line, wait four seconds then continue and then complete tasks one after another.

Specification of My NXT Lego Robot!

Lesson Aims:

*Design a system for a given set of requirements.
*Write Pseudo code.

A	M	S	Learning Aims (what the learner will be able to do)
/			Design a system with 4 sensors
/			Consider a test strategy
	/		Justify a test strategy
/			Be able to use the correct shapes for flow charts
/			Able to identify key rules for Pseudocode
	/		Can write correct Pseudocode
A	M	S	Learning Objectives (skills, knowledge & attitudes)
/			Create a system diagram
/			Identify possible solutions
/			Consider limiting / restricting factors

Hello!

Over my independent study time on Tuesday and Wednesday, I was able to complete and submit U24_A3. I struggled a bit but with a bit of a challenge I was able to get it done.

Upon coming in today, the starter was to make a pseudo code of an alarm clock that shows the time, enables the user to set an alarm, to play the alarm sound and for the user to hit the snooze button. This was a challenge because I was a little rusty on whether I am doing it in the correct format, this was a weakness. A strength was being able to do it to a good standard (compared against other people when John showed on screen).

Next, I cracked on with the sketches for A4T1. This is a sketch of the robot I will be building and working with Adam M hopefully. This was all apart of the specification which includes: What I am doing, why, how, solution, approach, testing, sketches, pseudo code and flowchart. Since this is a big list, I spent the entire day working on this and have gotten everything done apart from the pseudo code. This is a strength and puts me in a good spot ahead.

As for tomorrow, I will be coming in once again to complete the remaining pseudo code. I have then planned to build the hardware/structure of the robot and then create a basic code using the approach from my specification to get my NXT Lego robot functioning at a good state. This will put me in a really good position for Monday.

An inspiration has been everyone around me; by looking at their mistakes and the good aspects of their robots, I was able to see what is a good and bad thing. A big struggle today was understanding some parts as my design conflicts with the robot, but with the help of John I have worked my way around this.

See you tomorrow!

John Master Race!

Lesson Aims:

*Make a robot react to 3 different event triggers.
*Understand how signal conversion occurs.

A	M	S	Learning Aims (what the learner will be able to do)
/			Create a program to control a 3 sensor automated system
/			Understand how data is converted between analogue and digital
/			Be able to use the correct shapes for flow charts
/			Able to identify key rules for Pseudocode
	/		Can write correct Pseudocode
A	M	S	Learning Objectives (skills, knowledge & attitudes)
/			Write code that compiles
/			Solve errors
/			Use 3 sensors and motors to make an autonomous system
	/		Convert analogue to digital signals

Hello!

This morning as a starter, John went through analogue and digital conversion. This took quite long but this was actually an activity that produced work we could use later on in our assignments. We looked at binary conversion again and converted the samples into bits across a wavelength. A strength of this was being able to follow instructions and complete the work as well as understanding why and how it is important. A weakness was being tired.

Afterwards, we continued with the work we left off from. I installed Windows Movie Maker and edited the clips I recorded for my assignment where I explained the three different sensors. I then proceeded to explain about the three triggering-event-driven-executing-code-madness whilst showing my code. I also talked about the tools and techniques from the software such as IDE, compiler and readability such as white lining and indentation. This was a strength as I almost finished this.

Moreover, John explained the different types of things we need by creating a simplified checklist of the SoA. However, before I could finish my work I had promised to attend a lesson Adam is hosting - about employability skills, attributes and soft-skills. For this, I went with Ben R and Jordan B after lunch and had a good freshening lesson whilst Adam was being observed. A strength of this was being able to be aware of some skills I have not developed as much and aim to improve it. I spoke to the inspector and had a good chat too as well as creating a SMART target to achieve.

At the end, I went back upstairs to John's lesson. He recapped everything with me (thank you) and even explained additional work we could do (Assignment 4). As for the reflection, today has been a really productive day at getting things done -- I just couldn't sleep so I felt exhausted. My goals to accomplish over my independent study time is the U24_A3T1 and T2 which is due tomorrow midnight. This is the document explaining the code and techniques/tools used as well as analogue/digital conversion, why it is used/benefits etc. I also have to design a cover sheet for work in regards to EoYS and update my profile with the SMART target I created in mind.

I believe I can achieve this because I will be effectively planning and managing my time with a flexible mind set.

Robots!

Lesson Aims:
*Make a robot react to 3 different event triggers.
*Identify how the design of a robot can affects its performance.

A	M	S	Learning Aims (what the learner will be able to do)
/			Can explain how precede and mutex commands work in NXC
/			Identify the order of execution in NxC
/			Write readable code
/			Write quality code
	/		Design ideas for robot
		/	Understand the requirements for U14 A2 and U24 A3

Hello! 

I am merging yesterday's blog with today simple because the aims and objectives are identical. As for yesterday, we worked and messed with the NXC robots in order to get a better understanding of it as well as looking at what needs to be done over these last two joint units for U14 and U24.

As for today, the starter was a game John introduced to us. It is essentially a game where we control where the robot goes in order to light up all the ties within a specific amount of instructions. This became challenging, but it was fun and I managed to get my head around it. A strength was being logical as everything is procedural. The game can be found here. In addition to this, John also showed us a bunch of links and examples of how automated systems and sensor-machines are used in everyday life and in the industries. A particular video of a car being constructed purely by robots was the most interesting of all. We have also been filling in a document of the top 10 tips we have learnt for NXC programming throughout the day - this is a good area to put my reminders.

For the rest of the day, we continued to program our assigned robots to react to three different event triggers: sound, ultrasonic and impact. At the beginning, the code was tough to understand but it became easier as I practices and re-used working code, finding the structure easier to dissect. A strength was managing to complete the code by experimenting with it as well as making it readable by including indentation, comments and more. By the end of the day, I managed to repeatedly test my robot into reacting to three different sensors with a good difference in reaction. I then recorded myself talking about the three sensors and how it works - particularly with the sound as analogue is converted to digital as a signal. 

As for reflection, I find these units somewhat challenging but I am focusing on doing as best I can to achieve the specific grade I would like. As of now I am up to date with work. On Monday I will complete any unfinished work, including the edit of the video I recorded. Additionally, I will also be seeing Adam with other peers after lunch to help him with his lesson/work.

Below is a section of the code I have recorded today:

Snippet of my code for the NXC robot

Work & Games!

Aim
To explain the key features of event driven programs (P1).
To discuss how an operating system can be viewed as event driven (M1).
To evaluate the suitability of event driven programming for non-graphical applications (D1).

Objectives
State the key features of event driven programming, including the advantages and disadvantages.
Explain that modern programming languages are event driven.
Discuss, with examples, how Windows 7 can be viewed as an event driven application.
Describe in detail five examples of a system that is event driven but does not have a GUI.

Hello!

Today has been productive, I'd say? The starter was about robots and whether or not they can take our future jobs. In my opinion, I'd say basic jobs are replaceable with event driven programming - but jobs like Games Art & Design - possibly not due to the creativity needed. Can robots think creatively and create new ideas? Without the use of algorithms...

Next, Zoë once again did another recap of the work we needed to do. I cracked on by adding a conclusion to U14_A1T2, then I started and completed the distinction work for U14_A1T3. I submitted this and had completed all outstanding work.

I then spoke to Adam, Fergal and Connor more about the End of Year Show. We planned more, prioritised things and even managed to persuade most of the class to go, hopefully! I am excited and will explain more in future.

For the rest of the day, I played games. I then played games. Next, I played games and lastly, I played games. Due to completing work quickly (strength), I will stay at home until Thursday. My goals will be to complete any given resubmissions in the meantime. If I need help, I'll come in. 

Event Driven Parenting?

Aim: To evaluate the suitability of event driven programming (EDP).

Objective:
State the features of EDP.
Explain how OS can be considered event driven.
Understand that not all event driven programs have a GUI implemented.
Name some systems that are event driven but do not have a GUI.
Explain at least one example of a system that is event driven but does not have a GUI.
Describe in detail examples of a system that is event driven but does not have a GUI.

Hello!

On Wednesday, I visited NUA's show - I walked around the Games Art & Design area the most for around two hours with a good PAL friend (senior in NUA). It was really interesting and I had learnt a lot about the course I will be starting in September.

As for today, we had a quiz starter on how event driven programming can be taken in a parent way - parodied to 'event driven parenting' as a joke for raising a baby and that the parent tends to the baby's needs when it inputs a call. I found this to be quite interesting as it is applied to a real life concept but it would be better if it was a Kahoot quiz because there were definitely cheaters. Ah, rather not point out names. You can watch it here.

Next, Zoë recapped what we had previously covered on Monday which was about event driven programming's main features, advantages and disadvantages etc - she also covered a part we had not put in, so I had amended this quickly. Moreover, Zoë also helped me on a piece of work where I had also forgot to insert an important table, therefore that was amended as well and was resubmitted quickly.

This meant that I could continue with the merit work I promised to complete (but ended up being too busy). At the same time, the distinction part was covered and this felt like it was definitely doable and achievable. I used my time effectively to complete the merit work and thus begun on the distinction work of U24_A1 (T3). 

By reflecting on today, a strength was being able to complete a lot of the work set and stay ahead of time. A weakness was leaving the merit till today, although it posed no threat. I also spoke to Adam about learner forums, the NUA show as well as me being invited with other peers to his lesson in a fortnight. As for my goals, I will complete the distinction work tomorrow and any other outstanding work like Maths. This means I do not need to come in Monday which results in 5 days off... nice, cool, I like.

That's all, bye!

P.S: There's a lot of people distracting. People constantly on their phones, playing games,watching live-streams and chit-chatting. A bit annoying to be fair.

EDIT: No maths till next week!

Return - Last Term!

Aim: To understand the features of event driven programming.

Objectives:
*Explain the features of event driven programming.
*State some advantages and disadvantages of event driven programming.
*Describe, with examples, how an operating system can be viewed as an event driven application.

Hello!

Throughout my half term, I have dedicated the majority of the time into art. This is because I have been creating concept art for a game competition - BAFTA YGD. Last year I got nominated that's why this year I want to try again for the experience and confidence boost. I also received my U24_A1 resubmission.

The starter for today was a video about hoverboards that Zoë showed us. Although irrelevant as she mentioned, it was pretty interesting. I have no idea how it would revolutionise the world - if so, new traffic lanes would be needed! Afterwards, Zoë gave us a recap on U14_A1T1. This was about the key features of event driven programming. To finish it off, I typed up about the advantages and disadvantages that she went through with us. A strength was being able to get this work done early. As I wait for Zoë to cover merit section for U14_A1T2, I did my resubmission for U24_A1. This was relatively easy although I needed some reassurance. An improvement is to become even more independent.

After lunch, Zoë briefly covered the merit criteria. It is relatively easy as all I need to is write about how Windows 7 Operating System is an event driven application entirely. This task is very simple too and this was a strength. I believe I can do it easily. An inspiration for today has been blogs and articles I researched online. My aim is to complete this task by Thursday!