Difference between revisions of "Class Policies"

From CSE231 Wiki
Jump to navigation Jump to search
 
(37 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
=Academic Integrity and Citations=
+
===Academic Integrity===
−
This is not a group project course.  You are expected to complete all assignments independently.
+
{{:Academic_Integrity}}
  
−
Any act of dishonesty (e.g. cheating, lying) will be referred to the Dean's office in Engineering Student Services.
+
===Attendance/Participation===
−
If found in violation, the student will receive an F in the course and a permanent mark on their record.
+
Attendance is required.  You are expected to attend class on both Tuesdays and Thursdays for the section you are registered for. There are many benefits for coming to class (asking TA questions about assignments, clearing up any concepts with Prof. Cosgrove, etc.), so it is highly encouraged for you to come.
  
−
See the [https://wustl.edu/about/compliance-policies/academic-policies/undergraduate-student-academic-integrity-policy/ Undergraduate Student Academic Integrity Policy] for an non-exhaustive list.  If in doubt ask the Professor for clarification.
+
Attendance/Participation will be assessed via submission of in-class worksheets.   You will only be penalized after missing more than <s>three (3)</s> <b>six (6) in-class worksheets</b>.
  
−
NOTE: ''Withdrawing from the course will not prevent the academic integrity officer or hearing panel from adjudicating the case, imposing sanctions, or recommending grade penalties, including a failing grade in the course.''
+
===S&Q (Synthesis and Question) Forms===
 +
There will usually be an S&Q form due before every class. We expect you to complete these the night before classes. You will only be penalized after missing more than <b>three (3) S&Q forms</b>. If you fail to turn these in on time for class, you can still receive 70% credit by turning them in by 11:59PM Central on Friday.
 +
<!--
 +
===Labs===
 +
Labs come with a list of JUnit tests to help guide students past common problems. Passing all of the tests does not guarantee anything when it comes to a grade on the assignment. Labs are read by the professor and TAs. Students are provided feedback and given an initial grade. Students then have a week from that feedback to turn in revisions which will then be reviewed and given a final grade.
  
−
CSE 131 has some [http://www.cse.wustl.edu/~cytron/cse131/Info/collaboration.shtml|good general advice on academic integrity].
+
====Late Lab Submissions====
 +
Labs have an original submission date. Students then receive feedback on that submission and have a week to make revisions. Students who pass (shenanigans free) all of the JUnit tests by the original submission have the additional benefit of getting their revisions checked out in class to avoid any confusion.
  
−
==Honor Pledge==
+
{| class="wikitable"
−
You will be required to fill out a pledge, acknowledgements, and citations file for each assignment.  To be clear: failure to fill out this pledge will not save you from an academic integrity violation.
+
!
 +
!Portion of Grade
 +
!Evaluation Technique
 +
|-
 +
|Original Submission
 +
|style="text-align:center;"|25%
 +
|Non-shenanigans JUnit Test Passing
 +
|-
 +
|Final Revisions
 +
|style="text-align:center;"|75%
 +
|Quality Assessment
 +
|}
 +
-->
  
−
===Example Pledge===
+
===Exercises===
 +
Exercises are assessed by whether or not the code pushed to bitbucket passes all of the JUnit tests.  Exercises are due the following Saturday one week from their assignment.  If, after human inspection, your solution is deemed insufficient/inappropriate despite passing the JUnit tests, you will be alerted with the specifics and given a week to address the situation.
  
−
''On my honor as a student, the work I am submitting is mine own.  It was created within the acceptable bounds of this course.''
+
It should go without saying that any dishonest effort to pass the tests without solving the problem would be an [[Academic_Integrity|academic integrity violation]].
  
−
(You are free to use this as a pledge.)
+
The Matrix MapReduce exercise is worth 3X as much as the other exercises (which are equally weighted).
  
−
=Attendance=
+
'''Fall 2023 Specific Policy''': all exercises will be granted a one week extension with no penalty.
−
 
 
−
You are expected to attend class (on both Mondays and Wednesdays) and you will lose points if you fail to show up more than three times. We take attendance using either clicker questions or in-class quizzes. If you are caught trying to sign in for an absent friend, we will consider this an academic integrity violation and treat it as such. If your friends ask you to do this for them, tell them you do not want an academic integrity violation on your record. If you need to be absent for more than three classes for any reason, reach out to the instructors.
 
−
 
 
−
=Q&S Forms=
 
−
 
 
−
There will usually be a Q&S form due before every class. We expect you to complete these before class begins. Like attendance, you will only be penalized after missing more than three Q&S forms.
 
−
 
 
−
=Weekly Updates=
 
−
 
 
−
Every week, you will be sent an email updating you about your progress for that week. The update will include how much credit you received on the Q&S forms, your progress on the current assignment, and any comments that TAs might have for you based on the state of your assignment. These weekly updates are only meant to help you and do not represent your final grades. For example, even if you do not get full credit on the Q&S forms because you got quiz questions wrong, as long as we see that the majority of your Q&S forms received full credit, wrong answers from genuine attempts will not be docked.
 
−
 
 
−
=Good Faith Efforts=
 
−
 
 
−
When assignments are first due, the instructors will review your code and send any relevant feedback to you in your weekly update. After you get your feedback, you will have one week to submit your assignment again. The second submission is the only one that is formally graded, but you are expected to put in a good faith effort into your first submission. An example of a good faith submission might be a mostly completed assignment with a couple bugs and comments for graders that detail what went wrong in your implementation. A non-good faith effort would be adding a few spaces and new lines into your code for submission.
 
−
 
 
−
=Late Submissions=
 
−
 
 
−
If you submit an assignment after its due date, we will accept it up to a week after the original due date. However, you will only be able to earn a maximum of 70% of the original amount of points if you choose to submit something late.
 
−
 
 
−
=Office Hours=
 
−
 
 
−
Click here for updated [[office hours]].
 

Latest revision as of 12:33, 1 October 2023

Academic Integrity

This is not a group project course. You are expected to complete all assignments independently.

Any act of dishonesty (e.g. cheating, lying) will be referred to the Dean's office in Engineering Student Services.

If found in violation, the student will receive an F in the course and a permanent mark on his or her record.

There is no statute of limitations for academic integrity violations. If a violation is later discovered after the completion of the course or even graduation, an F will be retroactively applied (even if it means that the offending student's degree would be revoked).

See the Undergraduate Student Academic Integrity Policy for a non-exhaustive list. If in doubt ask the Professor for clarification.

NOTE: Withdrawing from the course will not prevent the academic integrity officer or hearing panel from adjudicating the case, imposing sanctions, or recommending grade penalties, including a failing grade in the course.

While it's policies may or may not be different, CSE 131 has some general advice on academic integrity.

Honor Pledge

You will be required to fill out a pledge, acknowledgements, and citations file for each assignment. To be clear: failure to fill out this pledge will not save you from an academic integrity violation.

Example Pledge (which you are free to use):

On my honor as a student, the work I am submitting is mine own. It was created within the acceptable bounds of this course.

Attendance/Participation

Attendance is required. You are expected to attend class on both Tuesdays and Thursdays for the section you are registered for. There are many benefits for coming to class (asking TA questions about assignments, clearing up any concepts with Prof. Cosgrove, etc.), so it is highly encouraged for you to come.

Attendance/Participation will be assessed via submission of in-class worksheets. You will only be penalized after missing more than three (3) six (6) in-class worksheets.

S&Q (Synthesis and Question) Forms

There will usually be an S&Q form due before every class. We expect you to complete these the night before classes. You will only be penalized after missing more than three (3) S&Q forms. If you fail to turn these in on time for class, you can still receive 70% credit by turning them in by 11:59PM Central on Friday.

Exercises

Exercises are assessed by whether or not the code pushed to bitbucket passes all of the JUnit tests. Exercises are due the following Saturday one week from their assignment. If, after human inspection, your solution is deemed insufficient/inappropriate despite passing the JUnit tests, you will be alerted with the specifics and given a week to address the situation.

It should go without saying that any dishonest effort to pass the tests without solving the problem would be an academic integrity violation.

The Matrix MapReduce exercise is worth 3X as much as the other exercises (which are equally weighted).

Fall 2023 Specific Policy: all exercises will be granted a one week extension with no penalty.

Retrieved from "http://classes.engineering.wustl.edu/cse231/core/index.php?title=Class_Policies&oldid=5047"