|
9 | 9 | "**Background**: Anagram Checker is a program that takes two words and determines if an anagram can be made from it. If so, the program will return `true`, otherwise `false`." |
10 | 10 | ] |
11 | 11 | }, |
| 12 | + { |
| 13 | + "cell_type": "markdown", |
| 14 | + "metadata": {}, |
| 15 | + "source": [ |
| 16 | + "## Submission Information\n", |
| 17 | + "\n", |
| 18 | + "🚨**Please review our [Assignment Submission Guide](https://github.com/UofT-DSI/onboarding/blob/main/onboarding_documents/submissions.md)**🚨 for detailed instructions on how to format, branch, and submit your work. Following these guidelines is crucial for your submissions to be evaluated correctly.\n", |
| 19 | + "\n", |
| 20 | + "### Submission Parameters:\n", |
| 21 | + "* Submission Due Date: `11:59 PM - 05/05/2024`\n", |
| 22 | + "* The branch name for your repo should be: `assignment-1`\n", |
| 23 | + "* What to submit for this assignment:\n", |
| 24 | + " * This Jupyter Notebook (assignment_1.ipynb) should be populated and should be the only change in your pull request.\n", |
| 25 | + "* What the pull request link should look like for this assignment: `https://github.com/<your_github_username>/python/pull/<pr_id>`\n", |
| 26 | + " * Open a private window in your browser. Copy and paste the link to your pull request into the address bar. Make sure you can see your pull request properly. This helps the technical facilitator and learning support staff review your submission easily.\n", |
| 27 | + "\n", |
| 28 | + "Checklist:\n", |
| 29 | + "- [ ] Created a branch with the correct naming convention.\n", |
| 30 | + "- [ ] Ensured that the repository is public.\n", |
| 31 | + "- [ ] Reviewed the PR description guidelines and adhered to them.\n", |
| 32 | + "- [ ] Verify that the link is accessible in a private browser window.\n", |
| 33 | + "\n", |
| 34 | + "If you encounter any difficulties or have questions, please don't hesitate to reach out to our team via our Slack at `#cohort-3-help`. Our Technical Facilitators and Learning Support staff are here to help you navigate any challenges." |
| 35 | + ] |
| 36 | + }, |
12 | 37 | { |
13 | 38 | "cell_type": "markdown", |
14 | 39 | "metadata": {}, |
|
92 | 117 | "anagram_checker(\"Slient\", \"Listen\", True) # False" |
93 | 118 | ] |
94 | 119 | }, |
95 | | - { |
96 | | - "cell_type": "markdown", |
97 | | - "metadata": {}, |
98 | | - "source": [ |
99 | | - "### Part 3: Expanding the functionality once more\n", |
100 | | - "\n", |
101 | | - "Given an array of words, check to see if they are anagrams of each other.\n", |
102 | | - "\n", |
103 | | - "```python\n", |
104 | | - "anagram_checker([\"Slient\", \"night\"], [\"thing\", \"listen\"], False) # True\n", |
105 | | - "anagram_checker([\"Slient\", \"thing\"], [\"night\", \"slient\"], True) # False\n", |
106 | | - "```" |
107 | | - ] |
108 | | - }, |
109 | | - { |
110 | | - "cell_type": "code", |
111 | | - "execution_count": null, |
112 | | - "metadata": {}, |
113 | | - "outputs": [], |
114 | | - "source": [ |
115 | | - "def anagram_checker(words_a, words_b, is_case_sensitive):\n", |
116 | | - " # Modify your existing code here\n", |
117 | | - "\n", |
118 | | - "# Create your own words of potential anagrams and use your checker to check it" |
119 | | - ] |
120 | | - }, |
121 | 120 | { |
122 | 121 | "cell_type": "markdown", |
123 | 122 | "metadata": {}, |
|
127 | 126 | "|Code Execution|All code cells execute without errors.|Any code cell produces an error upon execution.|\n", |
128 | 127 | "|Code Quality|Code is well-organized, concise, and includes necessary comments for clarity. E.g. Great use of variable names.|Code is unorganized, verbose, or lacks necessary comments. E.g. Single character variable names outside of loops.|" |
129 | 128 | ] |
130 | | - }, |
131 | | - { |
132 | | - "cell_type": "markdown", |
133 | | - "metadata": {}, |
134 | | - "source": [ |
135 | | - "## Submission Information\n", |
136 | | - "\n", |
137 | | - "🚨**Please review our [Assignment Submission Guide](https://github.com/UofT-DSI/onboarding/blob/main/onboarding_documents/submissions.md)**🚨 for detailed instructions on how to format, branch, and submit your work. Following these guidelines is crucial for your submissions to be evaluated correctly.\n", |
138 | | - "\n", |
139 | | - "### Submission Parameters:\n", |
140 | | - "* Submission Due Date: `HH:MM AM/PM - DD/MM/YYYY`\n", |
141 | | - "* The branch name for your repo should be: `assignment-1`\n", |
142 | | - "* What to submit for this assignment:\n", |
143 | | - " * This Jupyter Notebook (assignment_1.ipynb) should be populated and should be the only change in your pull request.\n", |
144 | | - "* What the pull request link should look like for this assignment: `https://github.com/<your_github_username>/python/pull/<pr_id>`\n", |
145 | | - " * Open a private window in your browser. Copy and paste the link to your pull request into the address bar. Make sure you can see your pull request properly. This helps the technical facilitator and learning support staff review your submission easily.\n", |
146 | | - "\n", |
147 | | - "Checklist:\n", |
148 | | - "- [ ] Created a branch with the correct naming convention.\n", |
149 | | - "- [ ] Ensured that the repository is public.\n", |
150 | | - "- [ ] Reviewed the PR description guidelines and adhered to them.\n", |
151 | | - "- [ ] Verify that the link is accessible in a private browser window.\n", |
152 | | - "\n", |
153 | | - "If you encounter any difficulties or have questions, please don't hesitate to reach out to our team via our Slack at `#cohort-3-help`. Our Technical Facilitators and Learning Support staff are here to help you navigate any challenges." |
154 | | - ] |
155 | 129 | } |
156 | 130 | ], |
157 | 131 | "metadata": { |
|
0 commit comments