--- tags: mth350 --- # MTH 350 Proof Portfolio guidelines ## Purpose The purpose of the Proof Portfolio in MTH 350 is twofold: 1. To isolate your best work on the hardest problems that you do in the course, and package it into a showcase for how much you have learned; and 2. To reflect on what you've learned in the area of mathematical problem solving and make that thinking visible. The Proof Portfolio is not just another assignment; it's something you can carry with you once the course is over and show to employers, graduate schools, and others who might be interested in your problem-solving and learning skills. ## What goes in the portfolio On each of our six Problem Sets, there is at least one and usually more than one **starred problem**. The Portfolio will consist of the following: **NOTE: This was updated on 2021-03-26.** - A collection of **six starred problems** selected from the Problem Sets, that you consider to be your best work. You have free choice as to which problems are included, but *you must include at least one starred problem from each of the six problem sets*. - Additionally, if you are attempting to earn a **High Pass** mark on the portfolio (see below), then you will choose **two more** starred problems from the Problem Sets and include those as well. These two additional problems *may not* be selected from the same problem set. - The portfolio will also ask you to include some reflections on the work that you are including, especially regarding how you improved your work over time through the revision process and what you learned by doing so. Details on this added material will be given around week 9--10 of the semester. **(NEW: [See below](https://hackmd.io/DvziySGGTKm_jPPXRVLgSw?both#Reflection-Items-to-include-with-your-portfolio) for these reflection items.)** The entire package of your portfolio problems and the additional material will be submitted as a PDF on Blackboard, with a deadline of **11:59pm Eastern on Tuesday, April 27**. ## How to put your portfolio together (**UPDATED 2021-03-26**) You have six Problem Sets to do throughout the semester, due roughly every two weeks. Each one has at least one starred problem on it, and you will be asked to do just one starred problem per Problem Set. This means that the basic six problems for your portfolio will simply be pulled from the work on problem sets you are already doing. If you are opting into earning a **High Pass** grade, you'll be choosing two more problems from this group to do. Again, those two additional problems must be picked from different sets. You will be evaluated and get feedback on the six problems that come from your Problem Set work, in the normal course of getting a mark on those Problem Sets. If you are attempting a **High Pass** mark and are submitting additional problems, **you may submit your work on those to me (Talbert) at any time through email**, and I will evaluate them and give you constructive feedback and a mark of E, M, P, or X just like Problem Set problems; this mark does not count toward any grade, but is just for your information to get a sense of what you might need to improve on your work. There are no deadlines for completing those two additional problems other than the April 27 deadline. ## How your portfolio will be evaluated As [mentioned in the syllabus](https://hackmd.io/@rtalbert235/HyqkgcE0P#How-do-I-earn-a-grade-in-the-course), Portfolios are marked **High Pass**, **Pass**, or **No Pass**. The criteria for each mark are as follows: (**UPDATED 2021-03-26**) | Mark | Criteria | | ---- | -------- | | **High Pass** | Eight problems are submitted, including one from each Problem Set and no more than two from any single Problem Set. Each of the eight problems meets the standard for a mark of **M** on Problem Sets, and additionally at least four of the problems meet the standard for a mark of **E**. Finally the additional reflection material is well written. | | **Pass** | At least six problems are submitted, one from each Problem Set. Each problem submitted meets the standard for a mark of **M** on Problem Sets, and the additional reflection material is well written. | | **No Pass** | The requirements for **Pass** are not met. For example: there are fewer than eight problems submitted; or the reflection material is incomplete or poorly written; or at least one of the problems submitted does not meet the requirements for a mark of **M**. | Specific criteria for the additional reflection material (what constitutes "well written") will be given when that material is announced later. **How do I know if my work is good enough to Pass, or earn High Pass?** For the problems that you turned in as part of a Problem Set, you can look at the mark that the set earned: If you have earned a mark of **M** on a Problem Set, then every problem on that set is individually at least at "M" level; similarly if your entire Problem Set has earned an "E". However, if your Problem Set earned a mark of "M", it's possible that your starred problem is at "E" level; if you are considering including a starred problem from a set that earned "M" but you think the starred problem is better than an "M", let me know and I will evaluate it separately. As for the two additional problems, as mentioned above you can submit those at any time to get individual evaluation on those. ## Reflection Items to include with your portfolio :::info **NEW -- ADDED 2021-04-06** ::: Along with the problems you submit for your portfolio, include the following: 1. **For each** problem you submit, write a brief overview of about 100-200 words that explains *why* you picked that problem and chose to include it and *what you learned* in the process of solving it, either in terms of mathematics or in terms of your problem solving skills. [For reference, this is what 200 words of text looks like](https://gist.github.com/RobertTalbert/9e0d6328ec97e6d8aa36b4ec7ae0c7b1). I won't be counting words here, but rather looking for substantive and authentic responses that show evidence of serious thought. 2. Then also submit one, longer-form reflection that addresses the question: **How did you grow as a problem-solver by doing these problems, and where do you think you still have room for growth?** You should aim for around 400 words on this one. Precise word count isn't that important; what matters is whether you're giving an authentic account of yourself that tells your story well. ## Questions *Additions to this list might be made during the semester as they come up; watch this space for updates.* **What if I didn't turn in one or more of the Problem Sets?** If this is the case, you can still go back and do at least one and no more than two starred problems from each of the Problem Sets you did not submit. Just treat them like the two additional problems mentioned earlier; submit your work on them to me when you're ready to have it evaluated. **If I did a starred problem as part of a Problem Set submission, do I *have* to include it in the portfolio, or can I change my mind and do another one from that set instead for the Portfolio?** ~~To keep things simple and to encourage you to stick with a problem once you've chosen to do it, the answer here is **no**. In other words, once you do a starred problem as part of a Problem Set that you turn in, you are committed to that problem for the semester, and it needs to go in your portfolio~~. (**UPDATED 2021-03-26**) If you turned in a starred problem on a Problem Set but you no longer want to include it in your portfolio (because you're tired of working on it, are making no progress, etc.) then you are allowed to change your problem. If you do so, you will need to do the following: (1) let me know by email or Campuswire DM about the change (what problem are you dropping and what problem are you adding in its place) and (2) submit your work on the new problem ASAP by email, as if it were an additional problem being done for a **High Pass** mark, so I can give it an initial evaluation. + **If you change a problem:** (1) the new problem *must* come from the same Problem Set as the old one, and (2) *you are not allowed to change back*, otherwise we might enter a cycle of switching back and forth that will make it impossible to evaluate your work. + **Changing problems is not recommended.** This is because it shortens the amount of time you have for doing revisions of work. If you do a problem in Problem Set 3, then you have half the semester to revise and resubmit your work repeatedly until it meets the grading standard; but if you abandon it and switch to a new problem in week 12, then you have *two weeks* to do so. It's better to simply persist with a problem until you've cracked it. [![hackmd-github-sync-badge](https://hackmd.io/DvziySGGTKm_jPPXRVLgSw/badge)](https://hackmd.io/DvziySGGTKm_jPPXRVLgSw)
Last changed by  
 
Robert Talbert
Professor of Mathematics, Grand Valley State University. Writer (http://rtalbert.org, http://rtalbert.org/book), speaker, researcher.
561

Read more

MTH 201-04: Calculus, Winter 2021

:::info Welcome to MTH 201! I'm Dr. Robert Talbert, Professor of Mathematics, and I am grateful that you are signed up for the course and am looking forward to working with you this semester. ::: What's MTH 201 all about? MTH 201 is a first course in Calculus, which is all about modeling and understanding change. Change is maybe the most important facet of the world around us, and we care about it more than we realize. For example, we care a lot about the number of Covid-19 cases in our community, but we might care even more about how fast the number of cases is changing (either up or down). In MTH 201, you'll learn the mathematical language of change and apply it to models that you build to draw conclusions, make predictions, and give meaningful answers to real problems. MTH 201 goes beyond just computation. In MTH 201, you'll build skills with understanding complex concepts, communicating those concepts and the meaning of your results to appropriate audiences, using professional tools to help you in your work, and practice working with others to improve your learning (and theirs). These are valuable skills no matter where you go next. Success in this course doesn't come easy, and you can expect to be pushed and stretched intellectually. But the struggle you experience is normal and healthy, a sign of growth and that you are doing things the right way. And you will receive tireless support from me and your classmates in the process. Above all, my top priority is to support you in your work and help you succeed.

11/11/2023
Miniproject 8

Initial due date: Sunday, April 9 at 11:59pm ET Overview Our final miniproject reaches back into linear algebra to look at diagonalizable matrices and their uses in solving systems of differential equations. Prerequisites: You'll need to be able to solve basic systems of differential equations and find the eigenvalues and eigenvectors for a small matrix. You'll also need a basic comfort level with concepts of linear independence and matrix arithmetic from earlier in the course. Background This entire problem comes from Section 3.9.1 in your textbook. Here is a rephrased version of the introduction to that section.

3/29/2023
Miniproject 7

Initial due date: Sunday, April 9 at 11:59pm ET Overview This miniproject will teach you about the Runge-Kutta method, a standard numerical solution technique for differential equations. Prerequisites: A strong grasp of Euler's Method for single DE's is needed. You will also need to be comfortable using a spreadsheet. Miniproject 6 (Euler's Method for systems) is also recommended. Background A description of the Runge-Kutta method along with an example is given in this tutorial. Read it carefully and make sure you can work along with the example before proceeding.

3/29/2023
Miniproject 6

Initial due date: Sunday, April 9 at 11:59pm ET Overview This miniproject introduces a version of Euler's Method as a numerical solution technique for systems. Prerequisites: You will need to be comfortable with using Euler's method for single differential equations. You'll also benefit from some familiarity with spreadsheets or Python in order to automate the calculations. Background This tutorial gives you the background you need for this assignment. Please read it and make sure you understand the concepts and the example: https://github.com/RobertTalbert/linalg-diffeq/blob/main/assignments/Euler's_Method_for_Systems.ipynb

3/22/2023
Read more from Robert Talbert
Published on HackMD