Tuesday, 30 September 2014

LESSON 4 While Loops






Learning Objectives
You wil learn to:
Describe Python while loops

CLASS ACTIVITY

We will work at the following section of Using Python

http://usingpython.com/python-while-loops/



Your teacher will go through the introduction with you but your job is to carefully read the examples which have been provided before completing the challenge.

TASK 1 and HOMEWORK

Complete the 'double or quit' game challenge.

Bài 4 Trong khi Loops
Mục tiêu học tập
Wil bạn học cách:
Mô tả Python trong khi các vòng
CLASS HOẠT ĐỘNG
Chúng tôi sẽ làm việc tại bộ phận sau đây của việc sử dụng Python
http://usingpython.com/python-khi-loops/
Giáo viên của bạn sẽ đi qua việc giới thiệu với bạn, nhưng công việc của bạn là để đọc kỹ các ví dụ đã được cung cấp trước khi hoàn tất thử thách.
NHIỆM VỤ 1 và Bài Làm Ở nhà
Hoàn thành trò chơi thách thức 'đôi hoặc bỏ'.



Posted by at

33 comments:

  1. Matthew Gavin 1 October 2014 at 12:00

    Double or Quit Game
    https://docs.google.com/document/d/16Zutest6KLiQd3YvnlMBfuDhmM_6QxcVcp4z0C84Upg/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T8 October 2014 at 04:28

      Two targets:

      1. Write an algorithm using osuedocode
      2. Annotate your final code

      Overall take care with you QWC ie introduce every sub-section.

      Delete
    2. Matthew Gavin 8 October 2014 at 11:01

      I have completed these improvements.
      https://docs.google.com/document/d/16Zutest6KLiQd3YvnlMBfuDhmM_6QxcVcp4z0C84Upg/edit?usp=sharing

      Delete
  2. Unknown4 October 2014 at 06:15

    Double or Quit
    https://docs.google.com/document/d/1s_FV2-VHfQz9z8RBdQi-S9Oi2rriBBkOXHsXLRlvorQ/edit

    ReplyDelete
    Replies
    1. Mr T8 October 2014 at 06:49

      Domi, please repeat imoproving the following:

      1. Detailed introudtion
      2. Under planning include an algorithm written in psuedocode
      3. Show testing results after code
      4 ANNOTATE CODE and explain the variables you have used
      5. Evbaluate your work suggesting improvements.

      Delete
    2. Unknown11 October 2014 at 08:06

      Improved 'Double or Quit' game report

      https://docs.google.com/document/d/1s_FV2-VHfQz9z8RBdQi-S9Oi2rriBBkOXHsXLRlvorQ/edit

      Delete
  3. Unknown6 October 2014 at 02:46

    double or quit project
    https://docs.google.com/document/d/1Sd15IweV-UBSk457WOf6dhM0cVwTvGdIHyYtcwKt7bw/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T8 October 2014 at 06:52

      Repeat after a thorough proof read correcting grammar errors.

      ANNOTATE and explain your code and the variables that you have used.

      Delete
    2. Unknown11 October 2014 at 08:29

      Here is the improved version:
      https://docs.google.com/document/d/1Sd15IweV-UBSk457WOf6dhM0cVwTvGdIHyYtcwKt7bw/edit?usp=sharing

      Delete
  4. Unknown6 October 2014 at 10:32

    https://docs.google.com/document/d/1j7iXhFb6_XT0W_7Tfnf5AJja-D20Ri4iaA3TBUqJpcM/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T8 October 2014 at 06:55

      Elliot please improve by adding:

      1. A detailed introduction
      2. Code which has been annotated with explanations including an analysis of all the variables that you have used
      3. An evaluation suggesting improvem,ents

      Delete
  5. Unknown6 October 2014 at 11:11

    Double or Quit Project
    https://docs.google.com/document/d/1FdeEtKHlcWJxEa_-3G6MwlfeVZH5ViiRf3_owZeQuHY/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T8 October 2014 at 07:06

      Improve by:
      1. Adding an algorithm written as psuedocode under Planning
      2. Annotate final code and also include a detailed description of each of the variables that you have used.

      Delete
    2. Unknown12 October 2014 at 10:34

      Improved Double or Quit Project
      https://docs.google.com/document/d/1FdeEtKHlcWJxEa_-3G6MwlfeVZH5ViiRf3_owZeQuHY/edit?usp=sharing

      Delete
  6. Novac6 October 2014 at 13:00

    Lachlan Bone:
    https://docs.google.com/a/gillotts.org.uk/document/d/1jnh9DU3qvS40CQvQczjpDHEq8wyoM0tVGa3OQiIyDmI/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T8 October 2014 at 07:04

      Please improve by including:

      1. A detailed introduction
      2. An algorithm written in psuedocode under planning
      3. ANNOTATE final code including an explanation of the variables that you have used
      4. Show screenshots of the tests being carried out.
      5 Include an evaluation of how you work can be improved.

      Delete
    2. Novac13 October 2014 at 12:59

      https://docs.google.com/document/d/1jnh9DU3qvS40CQvQczjpDHEq8wyoM0tVGa3OQiIyDmI/edit?usp=sharing

      Delete
  7. Unknown6 October 2014 at 16:00

    https://docs.google.com/document/d/107YNapAUik6vtwJAyPcOIaTd0FNjG9Iqco5wW_2Qv6k/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T8 October 2014 at 07:12

      Improve by:

      1. Sub -headings
      2. Adding a detailed introduction
      3. Add a written algorithm under planning alongside flow chart
      4. Annotate code and provide a detailed description of the variables that you have used.
      5. An evaluation suggesting improvements that you could mark

      ALWAYS FINISH YOUR WORK

      Delete
  8. Unknown7 October 2014 at 01:54

    https://docs.google.com/a/gillotts.org.uk/document/d/1jXmuc4mCAr-jjPrNanV4tW93m0IBEQEKssNCGuPZEqE/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T8 October 2014 at 07:16

      1. Proof read and improve grammar
      2. Annotate your final code with explanation and descriptions of what the code does also add an analysis of the variables that you have used.

      Delete
  9. Unknown7 October 2014 at 01:57

    https://docs.google.com/document/d/1rhCIMQDBPOmtL7xQeAKXKfZeW7VDMJ6dC5UvrXgglDE/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T8 October 2014 at 07:22

      Two improvements:

      1. Written algorithm under planning
      2. Annotate code with description of what each section and also describe the variables that you have used.

      Delete
    2. Unknown12 October 2014 at 08:34

      https://docs.google.com/document/d/1rhCIMQDBPOmtL7xQeAKXKfZeW7VDMJ6dC5UvrXgglDE/edit

      Delete
  10. Unknown7 October 2014 at 02:47

    https://docs.google.com/document/d/1ik41X18HvORySoL3t6tVTrRJza6AIi4ljkF9pYR0rRw/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T9 October 2014 at 10:00

      Please repeat with the following:

      1. Your user requirements
      2. Final code annotated and explanation of the variables you have used

      Delete
  11. Unknown7 October 2014 at 06:57

    https://docs.google.com/document/d/1-N1SMb_6q9umIr_vzBrboYK01n0EGlLx8Yg0Dr3Anvo/edit?usp=sharing

    ReplyDelete
  12. Anonymous8 October 2014 at 06:54

    https://docs.google.com/a/gillotts.org.uk/document/d/1MIWoH-FNR81s58hMTHYyFUBIJVaNcmw9fW4T6ZvlCVc/edit?usp=sharing
    adam garrod

    ReplyDelete
  13. Unknown8 October 2014 at 06:58

    https://docs.google.com/document/d/1E8MhgklLZ4OfCnUc6147TFkDLGpVMxrvpv473DqFuIE/edit

    ReplyDelete
  14. Anonymous8 October 2014 at 07:21

    https://docs.google.com/document/d/1sc2yj0tIfIEWX8GOuD44IPtqWGKcXYxspz-QS3gwur4/edit?usp=sharing
    Here is my actual code

    ReplyDelete
  15. Mr T8 October 2014 at 07:28

    Please resubmit with the correct 'Double or Quits' report.

    ReplyDelete
  16. Mr T9 October 2014 at 10:01

    I need permission to access this

    ReplyDelete

Subscribe to: Post Comments (Atom)