24
edits
Changes
Added assignment 1 page for Summer 2023 for NCC
<span id="assignment-1"></span>
= Assignment 1 =
<span id="overview"></span>
== Overview ==
Your assignment will be to create a script that can correctly print future and past dates. The script will divide a typical year by a given value. For example, 365 divided by 2 will be rounded to 182. Your script will then the correct date 182 days into the past and 182 days into the future.
Example:
<code>./assignment1.py 2023-01-25 2</code>
<pre>A year divided by 2 is 182 days.
The date 182 days ago was 2022-07-27.
The date 182 from now will be 2023-07-26.</pre>
<span id="restrictions"></span>
== Restrictions ==
* You may '''only use <code>sys</code> for parsing command line arguments'''.
* No other modules are allowed
<span id="instructions"></span>
== Instructions ==
The assignment will be broken into two milestones and one final submission. Please update your repository for each milestone and complete the final submission in order to earn all marks.
* Milestone 1 will be due on '''February 10'''.
* Milestone 2 will be due on '''February 24'''.
* The Final submission will be due on '''March 10'''.
-----
<span id="preparation"></span>
=== Preparation ===
# Accept the assignment on Blackboard.
# Once you accepted the assignment, you will get access to a starting repo.
# Clone the repo to your local VM.
# Add your code to the ''existing'' <code>assignment1.py</code> file.
# Commit after '''each significant change''' to the code.
# '''You can never have too many commits.''' GitHub is your proof of work and your backup if things go wrong.
<span id="milestone-1"></span>
=== Milestone 1 ===
# You are provided with a function called <code>after()</code>. This function is complete and should successfully return the next day’s date when provided with a starting date in <code>YYYY-MM-DD</code> format. You can experiment with this function by importing it into the Python interpreter:
<syntaxhighlight lang="python">from assignment1 import after
after('2023-01-25')</syntaxhighlight>
<ol start="2" style="list-style-type: decimal;">
<li>Study the <code>after()</code> function and explain how it works. Use '''in-line comments''' for each line of code.</li>
<li>Use the <code>after()</code> function as a guide, and complete the <code>before()</code> function. This function should perform the opposite: it should return the previous day’s date.</li>
<li>Don’t forget to push your code.</li></ol>
<span id="check-your-work"></span>
==== Check Your Work ====
Use the check script to verify your work so far.
<code>python3 CheckA1.py -f -v TestBefore</code>
<span id="feedback"></span>
==== Feedback ====
I will provide you feedback on '''GitHub'''. Check the '''Issues''' tab, and make any changes that are required before the next deadline. You can '''close the issue''' to indicate that you have seen the comment.
-----
<span id="milestone-2"></span>
=== Milestone 2 ===
This Milestone will ask you to ''refactor'' your code. This means modifying existing code to make it more portable.
# Complete the <code>leap_year()</code> function, using the relevant code that’s already inside <code>after()</code>.
# Edit your <code>after()</code> function. Replace any code that calculates leap years with a <code>leap_year</code> function call.<br />
# Verify that <code>after()</code> still works.
# Complete the <code>dbda()</code> function. Given a starting date and number of days, <code>dbda()</code> should call either <code>before()</code> or <code>after()</code> inside of a loop and return the end date. A negative number of days should return a date ''before'' start_date, and a postive number should return a date ''after'' start_date.
<span id="check-your-work-1"></span>
==== Check Your Work ====
Use the check script to verify your work.
* <code>python3 CheckA1.py -f -v TestLeap</code> to test your <code>leap_year()</code> function.
* <code>python3 CheckA1.py -f -v TestAfter</code> to test <code>after()</code> and ensure it’s still working.
* <code>python3 CheckA1.py -f -v TestDBDA</code> to test <code>dbda()</code>.
<span id="feedback-1"></span>
==== Submission====
* Take the screenshots of the output of check scripts. Add the screenshots in the files named: milstone2_leap.jpg, milstone2_after.jpg, milstone2_dbda.jpg
* Commit these three files to repository.
* Commits must be done before the deadline, a 20% deduction of marks applies to late submissions per day.
-----
<span id="final-submission"></span>
=== Final Submission ===
For the final submission you should integrate your functions into a working script, add relevant comments and implement some '''error checking''' so that invalid dates or arguments will cause a '''usage''' message to be displayed.
# In the ''main'' block, check the number of arguments. The first argument should be a valid date, and the second should be a divisor of a typical year (365 days).
# A divisor of '''2''' would mean dividing a year by half. This gives us 182 days. (This is rounded down, use the <code>round()</code> function).
# Print the number of days for the divisor.
# Use one call to <code>dbda()</code> to return the date that’s '''182 days''' before the start date.
# Use a second call to <code>dbda()</code> to return the date that’s '''182 days''' after the start date.
At this point you have a working script. Implement error checking:
# Complete the <code>usage()</code> function. This should print a helpful message to the user when they make a mistake, and exit.
# Complete the <code>valid_date()</code> function. This should use error checking to make sure that any date entered by the user is valid.
# Ensure that the '''divisor''' argument is not zero! This would cause a Divide by zero error.
<span id="final-checks"></span>
==== Final Checks ====
* <code>python3 CheckA1.py -f -v TestValidDate</code> to test your <code>valid_date()</code> function.
* <code>python3 CheckA1.py -f -v TestFinal</code> to test the final version of your script.
<span id="submitting-your-code-for-review"></span>
==== Submitting Your Code For Review ====
# Push your code to GitHub before the deadline.
# In addition, '''submit your code to Blackboard'''. A link will be provided.
-----
<span id="formatting-and-style"></span>
== Formatting And Style ==
A significant amount of your mark will be based on the things that ''aren’t'' your code. Please review the following guidelines to maximise your grade.
<span id="comments-and-documentation"></span>
=== Comments And Documentation ===
'''You need to be commenting your code'''. The following documentation is required:
* '''in-line comments''': Any line of code that is doing something non-obvious should be commented. Explain '''why''' you are doing something, rather than '''what''' you are doing.
* '''function docstrings''': After your <code>def</code> line, you enter a docstring inside ““. Any function that doesn’t already come with a docstring should have one.
* '''top-level docstring''': You will have noticed that the top of your <code>assignment1.py</code> file already has this docstring. Complete the '''Academic Honesty declaration''' and complete the docstring.
<span id="pep"></span>
=== PEP ===
The [https://peps.python.org/pep-0008/ PEP-8 Style Guide] is an official Python document that describes best practices for formatting your code. '''You should follow this guide as much as possible'''. You may find that [https://code.visualstudio.com/docs/python/linting using a linter] to check style to be useful.
<span id="functions-and-variables"></span>
=== Functions and Variables ===
* In addition to the required functions, you may create as many functions as you need.
* Functions should be in lower case, and spaces should be represented with an underscore. For example: <code>function_name</code>.
* Any data used inside of a function should be passed in as a parameter. Avoid global variables.
* Variables should have a sensible name. Avoid naming things <code>x</code>.
* Variables should be in lower case, and spaces represented by an underscore. For example: <code>start_date</code>.
<span id="git-commits"></span>
=== Git Commits ===
A workplace will have its own policy about how often to commit, and how to document commits. For us, '''git commits are your proof of work'''. Assignments that lack commits are subject to '''Academic Integrity review'''.
* A good practice is to create a commit for '''every significant change''' to your code. '''At the very least, commit after completing each of the required functions.'''
* An acceptable commit message needs to short, but should also describe the change. For example: <code>git commit -m "completed the leap_year function"</code>.
<span id="rubric"></span>
== Rubric ==
{|
! Element
!align="right"| Marks
|-
| '''Milestone 1:'''
|align="right"|
|-
| Documentation for <code>after</code> function
|align="right"| 4
|-
| TestBefore Checks
|align="right"| 6
|-
| '''Milestone 2:'''
|align="right"|
|-
| TestAfter Checks
|align="right"| 6
|-
| TestLeap Checks
|align="right"| 2
|-
| TestDBDA Checks
|align="right"| 2
|-
| '''Final Submission:'''
|align="right"|
|-
| TestValidDate Checks
|align="right"| 4
|-
| TestFinal Checks
|align="right"| 12
|-
| Comments and Documentation
|align="right"| 5
|-
| github use
|align="right"| 5
|-
| functions and style
|align="right"| 2
|-
| error checking
|align="right"| 2
|}
<span id="sample-output"></span>
== Sample Output ==
<code>./assignment1.py 2023-01-25 2</code>
<pre>A year divided by 2 is 182 days.
The date 182 days ago was 2022-07-27.
The date 182 from now will be 2023-07-26.</pre>
<code>./assignment1.py 2020-02-14 4</code>
<pre>A year divided by 4 is 91 days.
The date 91 days ago was 2019-11-15.
The date 91 from now will be 2020-05-15.</pre>
<code>./assignment1.py 2023-02-29 3</code>
<pre>Error: wrong day entered
Usage: ./assignment1.py YYYY-MM-DD division</pre>
<code>./assignment1.py 2001-13-01</code>
<pre>Usage: ./assignment1.py YYYY-MM-DD division</pre>
<code>./assignment1.py 2001-13-01 5</code>
<pre>Error: wrong month entered
Usage: ./assignment1.py YYYY-MM-DD division</pre>
<code>./assignment1.py 2011-12-01 0</code>
<pre>Usage: ./assignment1.py YYYY-MM-DD division</pre>
= Assignment 1 =
<span id="overview"></span>
== Overview ==
Your assignment will be to create a script that can correctly print future and past dates. The script will divide a typical year by a given value. For example, 365 divided by 2 will be rounded to 182. Your script will then the correct date 182 days into the past and 182 days into the future.
Example:
<code>./assignment1.py 2023-01-25 2</code>
<pre>A year divided by 2 is 182 days.
The date 182 days ago was 2022-07-27.
The date 182 from now will be 2023-07-26.</pre>
<span id="restrictions"></span>
== Restrictions ==
* You may '''only use <code>sys</code> for parsing command line arguments'''.
* No other modules are allowed
<span id="instructions"></span>
== Instructions ==
The assignment will be broken into two milestones and one final submission. Please update your repository for each milestone and complete the final submission in order to earn all marks.
* Milestone 1 will be due on '''February 10'''.
* Milestone 2 will be due on '''February 24'''.
* The Final submission will be due on '''March 10'''.
-----
<span id="preparation"></span>
=== Preparation ===
# Accept the assignment on Blackboard.
# Once you accepted the assignment, you will get access to a starting repo.
# Clone the repo to your local VM.
# Add your code to the ''existing'' <code>assignment1.py</code> file.
# Commit after '''each significant change''' to the code.
# '''You can never have too many commits.''' GitHub is your proof of work and your backup if things go wrong.
<span id="milestone-1"></span>
=== Milestone 1 ===
# You are provided with a function called <code>after()</code>. This function is complete and should successfully return the next day’s date when provided with a starting date in <code>YYYY-MM-DD</code> format. You can experiment with this function by importing it into the Python interpreter:
<syntaxhighlight lang="python">from assignment1 import after
after('2023-01-25')</syntaxhighlight>
<ol start="2" style="list-style-type: decimal;">
<li>Study the <code>after()</code> function and explain how it works. Use '''in-line comments''' for each line of code.</li>
<li>Use the <code>after()</code> function as a guide, and complete the <code>before()</code> function. This function should perform the opposite: it should return the previous day’s date.</li>
<li>Don’t forget to push your code.</li></ol>
<span id="check-your-work"></span>
==== Check Your Work ====
Use the check script to verify your work so far.
<code>python3 CheckA1.py -f -v TestBefore</code>
<span id="feedback"></span>
==== Feedback ====
I will provide you feedback on '''GitHub'''. Check the '''Issues''' tab, and make any changes that are required before the next deadline. You can '''close the issue''' to indicate that you have seen the comment.
-----
<span id="milestone-2"></span>
=== Milestone 2 ===
This Milestone will ask you to ''refactor'' your code. This means modifying existing code to make it more portable.
# Complete the <code>leap_year()</code> function, using the relevant code that’s already inside <code>after()</code>.
# Edit your <code>after()</code> function. Replace any code that calculates leap years with a <code>leap_year</code> function call.<br />
# Verify that <code>after()</code> still works.
# Complete the <code>dbda()</code> function. Given a starting date and number of days, <code>dbda()</code> should call either <code>before()</code> or <code>after()</code> inside of a loop and return the end date. A negative number of days should return a date ''before'' start_date, and a postive number should return a date ''after'' start_date.
<span id="check-your-work-1"></span>
==== Check Your Work ====
Use the check script to verify your work.
* <code>python3 CheckA1.py -f -v TestLeap</code> to test your <code>leap_year()</code> function.
* <code>python3 CheckA1.py -f -v TestAfter</code> to test <code>after()</code> and ensure it’s still working.
* <code>python3 CheckA1.py -f -v TestDBDA</code> to test <code>dbda()</code>.
<span id="feedback-1"></span>
==== Submission====
* Take the screenshots of the output of check scripts. Add the screenshots in the files named: milstone2_leap.jpg, milstone2_after.jpg, milstone2_dbda.jpg
* Commit these three files to repository.
* Commits must be done before the deadline, a 20% deduction of marks applies to late submissions per day.
-----
<span id="final-submission"></span>
=== Final Submission ===
For the final submission you should integrate your functions into a working script, add relevant comments and implement some '''error checking''' so that invalid dates or arguments will cause a '''usage''' message to be displayed.
# In the ''main'' block, check the number of arguments. The first argument should be a valid date, and the second should be a divisor of a typical year (365 days).
# A divisor of '''2''' would mean dividing a year by half. This gives us 182 days. (This is rounded down, use the <code>round()</code> function).
# Print the number of days for the divisor.
# Use one call to <code>dbda()</code> to return the date that’s '''182 days''' before the start date.
# Use a second call to <code>dbda()</code> to return the date that’s '''182 days''' after the start date.
At this point you have a working script. Implement error checking:
# Complete the <code>usage()</code> function. This should print a helpful message to the user when they make a mistake, and exit.
# Complete the <code>valid_date()</code> function. This should use error checking to make sure that any date entered by the user is valid.
# Ensure that the '''divisor''' argument is not zero! This would cause a Divide by zero error.
<span id="final-checks"></span>
==== Final Checks ====
* <code>python3 CheckA1.py -f -v TestValidDate</code> to test your <code>valid_date()</code> function.
* <code>python3 CheckA1.py -f -v TestFinal</code> to test the final version of your script.
<span id="submitting-your-code-for-review"></span>
==== Submitting Your Code For Review ====
# Push your code to GitHub before the deadline.
# In addition, '''submit your code to Blackboard'''. A link will be provided.
-----
<span id="formatting-and-style"></span>
== Formatting And Style ==
A significant amount of your mark will be based on the things that ''aren’t'' your code. Please review the following guidelines to maximise your grade.
<span id="comments-and-documentation"></span>
=== Comments And Documentation ===
'''You need to be commenting your code'''. The following documentation is required:
* '''in-line comments''': Any line of code that is doing something non-obvious should be commented. Explain '''why''' you are doing something, rather than '''what''' you are doing.
* '''function docstrings''': After your <code>def</code> line, you enter a docstring inside ““. Any function that doesn’t already come with a docstring should have one.
* '''top-level docstring''': You will have noticed that the top of your <code>assignment1.py</code> file already has this docstring. Complete the '''Academic Honesty declaration''' and complete the docstring.
<span id="pep"></span>
=== PEP ===
The [https://peps.python.org/pep-0008/ PEP-8 Style Guide] is an official Python document that describes best practices for formatting your code. '''You should follow this guide as much as possible'''. You may find that [https://code.visualstudio.com/docs/python/linting using a linter] to check style to be useful.
<span id="functions-and-variables"></span>
=== Functions and Variables ===
* In addition to the required functions, you may create as many functions as you need.
* Functions should be in lower case, and spaces should be represented with an underscore. For example: <code>function_name</code>.
* Any data used inside of a function should be passed in as a parameter. Avoid global variables.
* Variables should have a sensible name. Avoid naming things <code>x</code>.
* Variables should be in lower case, and spaces represented by an underscore. For example: <code>start_date</code>.
<span id="git-commits"></span>
=== Git Commits ===
A workplace will have its own policy about how often to commit, and how to document commits. For us, '''git commits are your proof of work'''. Assignments that lack commits are subject to '''Academic Integrity review'''.
* A good practice is to create a commit for '''every significant change''' to your code. '''At the very least, commit after completing each of the required functions.'''
* An acceptable commit message needs to short, but should also describe the change. For example: <code>git commit -m "completed the leap_year function"</code>.
<span id="rubric"></span>
== Rubric ==
{|
! Element
!align="right"| Marks
|-
| '''Milestone 1:'''
|align="right"|
|-
| Documentation for <code>after</code> function
|align="right"| 4
|-
| TestBefore Checks
|align="right"| 6
|-
| '''Milestone 2:'''
|align="right"|
|-
| TestAfter Checks
|align="right"| 6
|-
| TestLeap Checks
|align="right"| 2
|-
| TestDBDA Checks
|align="right"| 2
|-
| '''Final Submission:'''
|align="right"|
|-
| TestValidDate Checks
|align="right"| 4
|-
| TestFinal Checks
|align="right"| 12
|-
| Comments and Documentation
|align="right"| 5
|-
| github use
|align="right"| 5
|-
| functions and style
|align="right"| 2
|-
| error checking
|align="right"| 2
|}
<span id="sample-output"></span>
== Sample Output ==
<code>./assignment1.py 2023-01-25 2</code>
<pre>A year divided by 2 is 182 days.
The date 182 days ago was 2022-07-27.
The date 182 from now will be 2023-07-26.</pre>
<code>./assignment1.py 2020-02-14 4</code>
<pre>A year divided by 4 is 91 days.
The date 91 days ago was 2019-11-15.
The date 91 from now will be 2020-05-15.</pre>
<code>./assignment1.py 2023-02-29 3</code>
<pre>Error: wrong day entered
Usage: ./assignment1.py YYYY-MM-DD division</pre>
<code>./assignment1.py 2001-13-01</code>
<pre>Usage: ./assignment1.py YYYY-MM-DD division</pre>
<code>./assignment1.py 2001-13-01 5</code>
<pre>Error: wrong month entered
Usage: ./assignment1.py YYYY-MM-DD division</pre>
<code>./assignment1.py 2011-12-01 0</code>
<pre>Usage: ./assignment1.py YYYY-MM-DD division</pre>
