College FINISHED!

Hello!

This will be my last blog in terms of academic applications. 

Coming into college today, I only had two resubmissions to do. These were quite difficult because of my limited knowledge/new field of study. Nonetheless, with a bit of help and dedication, I have managed to complete and resubmit these throughout the day. 

I am incredibly happy with what I have achieved. 2 years after studying at Develop, I am proud to announce I have achieved a D*D*D*! Very happy, pleased and satisfied with all the effort put in. Now to celebrate.

This Monday I will be at Develop's End of Year Show to set up the exhibition/show and stay there for practically the last day. This is also irrelevant but I'm on holiday the very next day after! 

It has been an exciting journey. I will be give a good review and put a link to my new blog when I begin university at the Norwich University of the Arts.

Thank you all!

Completing Outstanding Work!

Hello!

I have come into college today on behalf of my choice to complete outstanding work. I firstly completed U26_A3T3 which is the Maths distinction work. This was about network addressing such as CIDR notations. A strength was attempting it and watching videos/reading websites about it. A weakness was struggling, but nonetheless I have a resubmission.

Additionally, I also tidied up my folders and completed resubmissions that were major. The only work I have to do now is to resubmit some U24 tasks as U14. This is a simple job I can do at home. By reflecting today, I have been productive but have been slowed down by my annoying cough/illness.

On Friday I will come back and submit everything, fill the SoAs, complete the end of unit surveys, send my CV to Catherine to check and complete the Maths resubmission.

Getting Work Done!

Lesson Aims:

*Demonstrate a program that meet requirements.
*Test a solution.
*Consider suitable improvements that could be made to a system.
*Evaluate your design and creation process.
*Refine an existing program to improve the UX.
*Understand addressing schemes for networks.

A	M	S	Learning Aims (what the learner will be able to do)
/			Build a system with 4 sensors
/			Produce readable code
/			Produce readable  good quality code
/			Complete a detailed test table
/			Write a program to meet requirements
	/		Describe key elements that support a UX
	/		Identify improvements your system could have
		/	Know what subnets are
		/	Identify the difference between classes and CIDR
A	M	S	Learning Objectives (skills, knowledge & attitudes)
/			Carryout suitable tests
	/		Consider weaknesses in a design/solution
	/		Identify factors that contribute to a good UX
	/		Identify factors that contribute to a bad UX
		/	Create addressing scheme using CIDR

Hello!

Coming into college (ill once again), John firstly showed us the same video he did a while ago -- of car-building robots building and transporting car resources/materials. This was interesting as he explained how the robot-task we did relates to it in an industrial manner.

I then cracked on with work, I started, completed and resubmitted U24_A4T3 and U14_A4T1 resub. This was relatively simple and a strength was being quick. I also moved onto the technical documentation for U14_A4T2 and have finally completed this which took quite some time due to perfection, then submitted.

Due to being ahead, I was able to fill in more of the SoA for U26, tell Catherine about me being off for Thursday (holiday form//busy), and I also managed to help Adam progress further with the EoYS presentation. At the end of the day, John went over the U26_A3T3 with us again, which is the final task I will look over and practice over the weekends. With 10 days until holiday, it's been really hectic but I am certain I will get everything done.

To reflect on today, it has been a really productive day. I will be working on submitting U14 work from home and practising the Maths to get further ahead and attempt to complete almost everything by Monday.

It is so close yet so far.

Working Whilst Ill!

Lesson Aims:

*Demonstrate a program that meet requirements.
*Test a solution.
*Consider suitable improvements that could be made to a system.
*Evaluate your design and creation process.
*Refine an existing program to improve the UX.
*Understand addressing schemes for networks.

Hello!

Today I'm ill, but I came in because I wanted to further my outstanding work and to at least get to grips with the Math's unit's distinction criteria. The first thing I did was create a list of what I needed to do, both outstanding work and resubmission.

I firstly completed U24_A4T2 resubmission, the end of term summer survey, and U24_A4T4. This means I have completed U24 the unit as an overall; except for future resubmissions, this is a strength.

John also went through the Maths distinction work with myself, Matthew T and Tom S. A weakness was struggling to understand the difficult knowledge but as I re-read the document, it became clearer slowly. 

For reflection, I did well despite being ill. After college, I attended the final Learner Forums meeting for the EoYS discussion. I will attempt to complete more work soon, bye! 

Assignment after Assignment!

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.
*Refine an existing program to improve the UX.

Hello!

Coming into college, the first thing John did was talk about U14_A4 as this assignment is the only part different to U24 (everything else is similar). Moreover, he also mentioned what we have to do left, and so I created a quick to-do list that helped throughout the day.

I firstly started and completed U24_A4T3, which is a document where I wrote about how I could improve my robot and whereabouts. This was relatively simple as I used the test document to identify and clarify where the errors were - this was a strength. At the end, I submitted U24_A4T2 and T3. I have also gotten my U24_A4T1 resub back, meeting the criteria. I am very pleased. I also got my observation sheet back (about my robot's performance) and used it to slightly begin U24_A4T4, the last document. However, I left it as for now.

Instead, I started and finished U14_A4T1. This is a document about how my Painter Program from U06_A3 (last year) helps and assists users. A strength was being able to complete and submit this too. I felt very accomplished and ahead. Then, for the last part of the day I spoke to Catherine about getting my CV made soon (for University part-time jobs), I emailed Adam about the End of Year Show priorities (things left to do) and started U24_A4T2 to a good considerate spot. I have also helped Adam M on his resubmissions, and despite it is good to exercise my memory, it made me pause my work and therefore I believed this to be a weakness/distraction.

Nonetheless, reflecting on today I have been able to complete all the work I have desired, and if not, more! Tomorrow is my birthday therefore I'm not doing any work! And returning on Thursday, I will complete U14_A4T2 and U24_A4T4, completing both units and ready to start the Maths. 

Bye!

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