Robert Talbert
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    --- tags: mth225, course-documentation --- # Specifications for Satisfactory Work in MTH 225 ## Overview As the syllabus details, your work in MTH 225 is graded on a two-level scale: Either 1 or **Satisfactory** if the work meets our class' standards for quality, or 0 or **Unsatisfactory** if it does not meet those standards. **This document gives the details of those standards for every piece of work in the course.** Next to the syllabus and the calendar, this is therefore the most important document for the course. You need to make sure you read it carefully and refer back to it regularly as you work. **Use this document as a "pre-flight" checklist** to self-evaluate your work before you hand it in; this will improve your work dramatically and save you lots of time having to revise Unsatisfactory work. ## Standards for Daily Prep assignments Daily Prep assignments have two parts: a **pre-class** exercise set based on videos and reading, and an **in-class** group quiz over the same material. | Part | Earn **1** if: | |:---: | :-----------: | | Pre-class | The work is **submitted before the deadline** and <br> **every non-optional item has a response representing a good-faith effort to be right**. | | In-class | At least 2/3 or 3/4 of the items have a correct answer. | :::warning Please note that on the pre-class portion, a **0** is given if *any* of the following occur: - The work is submitted after the deadline; or - A required item has been left blank, even if accidentally; or - A required item has been given a response that indicates low effort in attempting to be right, such as an obvious guess, a frivolous answer, or an "I don't know". ::: ## Standards for Weekly Challenges Weekly Challenges typically consist of three kinds of work: practice exercises on basic computations, application or extension problems, and writing prompts. **Practice Exercises** are optional and are not graded. However, answers (or a tool for checking your answers) will be provided, and any work submitted for a practice exercise (even if it's partial or just a question) will receive feedback you can use to help you learn. These are for your own growth. **Application/Extension Problems** are graded on the basis of the correctness of the result and, especially and primarily, on the correctness and clarity of the explanation. **Writing Prompt** responses are evaluated based on whether you gave given a good-faith effort to provide an honest and substantive response. :::warning When grading a Weekly Challenge, the entire body of work you submit is considered and given a mark of either **Satisfactory** or **Unsatisfactory**. A Weekly Challenge is considered **Satisfactory** if all of these standards are met: - Every Application/Extension Problem has a solution that **demonstrates strong understanding of the concepts involved**, is **complete and well-communicated**, and contains **at most only a few minor errors**, none of which demonstrate gaps in understanding or communication. - Every writing prompt has a response that represents a **good-faith effort at honest communication** regarding the subject and is **well-communicated**. ::: Some items may contain additional expectations or requirements (for example, if a problem involves computer code), and **Satisfactory** will require meeting those expectations as well as the two baseline expectations above. **Incomplete (IC) work on Weekly Challenges:** A special designation of **Incomplete** (abbreviated **IC** in the Blackboard gradebook) may be given to Weekly Challenge submissions. A Weekly Challenge is graded **IC** if: - All or part of a required item is blank, only partially complete, or has a response that is not a good-faith effort at a complete response. For example, completing part of a problem and then explaining that you didn't know how to complete the other parts will result in an **IC**. Or, - There are significant and numerous major errors or misconceptions on mathematics or logic that occur throughout the work. Or, - The submission is disorganized, illegible, messy, or unprofessionally written up. Written responses for Weekly Challenges are acceptable, but all writeups *must* show good-faith effort to present the work in an orderly, professional-looking manner. Weekly Challenges that are marked **IC** will receive feedback only on why it was so marked; little to no feedback will be given on the content of the submission. You may revise and resubmit an **IC** Weekly Challenge, but ~~**you must spend a token** to do so, and~~ you will be doing it without the benefit of feedback on the math content of your work. *(Update: We removed the token requirement in the October update.)* ## Standards for Learning Target work Becoming "fluent" on a Learning Target, in the language of the syllabus, requires **two successful demonstrations of skill** on that target that can be done in various ways, all detailed in the syllabus. A "demonstration of skill" typically means working out a problem or small group of problems that have something to do with the skills in the learning target. Those problems will vary throughout the semester but will always focus on the same set of skills. For example, no matter how you choose to demonstrate skill on Learning Target L.3, you will always be asked to do work involving determining whether a predicate is true, determining whether a quantified predicate is true, and stating the negation of a quantified predicate --- because that's what the Learning Target says (*"I can identify the truth value of a predicate, determine whether a quantified predicate is true or false,and state the negation of a quantified statement."*) :::warning **Regardless of the precise work you do, a demonstration of skill is considered "successful" if**: - All parts of the work you are asked to do have an attempted response. That is, you may not skip or decline to respond to a part of a problem. - The response contains **no more than two simple errors** (see below for a definition) and **no non-simple errors**. That is, the work can contain no significant errors that cast doubt on your skill. - The response cannot *just* consist of a correct answer, unless it specifically says so --- you must also clearly communicate the thought processes that led to the answer, through clearly-written mathematical work, verbal explanations, or both. ::: For MTH 225, a "simple" error is defined to be **an error in logic, computation, or communication that does not pertain to the learning target and does not oversimplify the problem**. **Example:** In a hypothetical Algebra II class using our grading system, students are demonstrating their skill at solving quadratic equations ($ax^2 + bx + c = 0$) using the quadratic formula ($x = \frac{-b \pm \sqrt{b^2 - 4ac}}{2a}$). On a quiz, the class is asked to do this by finding the solutions to $3x^2 + 4x + 1 = 0$. (The correct answers are $x = -1$ and $x=-1/3$.) Here are some errors that students might commit, and whether they are considered "simple" or "non-simple". | Error | Simple? | Why | | :---: | :--------: | :---: | | Alice copies the problem down incorrectly as $3x^2 - 4x + 1 = 0$ (changing $+4x$ to $-4x$), then *correctly* solves this incorrect problem to get $x=1$ and $x=1/3$. | SIMPLE | The copy error doesn't pertain to the learning target (being able to show skill with the quadratic formula) and doesn't make the problem any harder or easier. | | Bob copies the problem down incorrectly as $3x + 4x + 1 = 0$ (dropping the square on $3x^2$), simplifies this to $7x + 1 = 0$, then solves without the quadratic formula to get $x=-1/7$. | NOT SIMPLE | The copy error oversimplifies the problem, and it no longer demonstrates skill on the learning target. | | Chuck copies the problem down correctly but mistakenly uses $b^2 + 4ac$ in the quadratic formula instead of $b^2-4ac$. | NOT SIMPLE | That's a fundamental error directly related to the learning target. | | Diane copies the problem down correctly and starts the solution correctly, but at one point she mistakenly switches a plus/minus sign, which leads to an incorrect answer. | SIMPLE | A basic sign error made in the process of a correctly-set up solution does not pertain to this learning target and does not make the problem trivially easy. | Note that **an error that is considered "simple" in one situation may be "non-simple" in another**. For example, Learning Targets SF.5 and C.2 both involve the factorial function. Making an error in computing this function, for example computing $10! = 1000$, would be *non-simple* for SF.5 since the entire target is about computing these functions correctly; but might be simple in C.2 since the emphasis there is in using the factorial as part of a larger problem-solving process.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully