The Openness Principle, Your Work, and Privacy
Data science, as a young interdisciplinary field, has fully embraced the principle of open, transparent and collaborative mode of scientific inquiry. The overwhelming popularity of GitHub speaks volumes to this ethos. In this class, we too will adopt the principle of openness in everything we do -- be it coding, data development or linguistic research. As a matter of fact, learning the practice of openness is considered one of the central pedagogical aims of this course. However, I recognize that the course is foremost a learning platform and therefore there exist certain expectations of privacy in the work students submit. In order to balance the two considerations, the course will adopt the following, tiered, privacy policies:
- Fully public. Individual students' term projects will be completely open: projects will be developed and submitted via a GitHub public repository, where they are open to the world to view. Same goes with some exercise-type assignments.
- Private to the world, shared within class. Submission of homework assignments as well as distribution of data sets with limited access will be done via a private GitHubrepository. Students' work therefore will be fully visible to their classmates but won't be shared with the world. This promotes collaborative learning among students while ensuring a reasonable level of privacy for their work.
- Private. Lastly, CourseWeb will be utilized for the aspects of course work that should remain strictly private between a student and the instructor. Those include posting of grades and feedback on student performance.
As a rule, there will always be a form of assignment between classes. Make sure to keep up with them.
- Homework assignments (50-60 points each): Most of these assignments will involve some type of problem solving through coding.
- To-do Tasks (10 points each): These will be mini tasks that are assigned between classes. They will comprise smaller tasks focused more on practical aspects, such as learning new software, information gathering, and peer feedback.
- Readings and Self-Guided Learning: You will have articles to read and various online tutorials and book chapters to study, as outlined in the Learning Resources page.
- Term Project (400 total points): In addition to the assignments and readings, you are expected to make steady progress on your term project. See the Schedule Table for the milestone dates and the Term Project Guidelines page for details of this requirement.
Requirements and grade calculation:
|Term project||40%||400 points|
|Homework assignments||40%||50-60 points each|
|To-do tasks||10%||10 points each|
|Attendance & Participation||10%||70 points (attendance)|
+ 30 points (participation)
|1 missed class allowed;|
-6 points for each absence thereafter
- Late work penalties:
Assignments are due 30 minutes before each class via GitHub. Late homework assignments and project milestones will be penalized as follows: 20% if submitted up to 24 hours late, 10% additional penalty for each late day thereafter. To-do assignments: 50% penalty up to 24 hours, no later submissions will be accepted. One lateness free-pass: life happens, we sometimes forget or get confused, so I am allowing everyone one penalty-free tardy incident of up to 2 days.
Attendance is mandatory.
Roll calls will be taken on a regular basis, which will be reflected on your attendance score.
For information on excusable absences, see this section below.
The participation grade will be based on students' engagement level in classroom and also their activity in the CourseWeb forum.
- To-do tasks: These will be graded on a completion-basis. Full 10 points for satisfactory completion; 5 points for unsatisfactory (70% or below) work; 0 for no credit.
- Homework assignments: Most homework assignments will involve Python programming as a component as well as learning objectives that are specific to them. Some important notes:
- When it comes to the coding component, having a Python script produce the desired, correct output is considered only part of the requirement. That is, correctly functioning code is not enough to garner full points. There are many ways to write a piece of code, and some are more elegant, computationally efficient, better organized and easier to understand than others; unlike in LING 1330/2330, those considerations will be given more weights in this course.
- Homework submissions are meant to be shared in this course, with students encouraged to learn from each other's work. To that end, an emphasis will be placed on the communicative and presentational aspect: a Python script and any other work submitted is expected to be accompanied by well-written and clear documentation designed to present the work to an audience in a way that facilitates their understanding.
- Term project: see the Term Project Guidelines page.
Collaboration on Assignments
If done properly, working together on assignments lead to a better learning outcome for all parties involved. If done improperly, however, it negatively affects learning AND results in cheating. For your learning benefit, I am allowing group work provided that the following conditions are met:
- Equal contribution: one student's contribution must not exceed 150% of other's.
- Individual work before a study group: do not show up to a study session without having worked on the assignment on your own beforehand.
- Individual work after a study group: do not write up your homework assignments while working in group, which leads to copying other's answers. Always finish up your answers by yourself afterwards, using your own words.
- As you can see from the course schedule, this class moves in a rapid pace. It is critical that you attend class regularly and keep up with the course content. If you do not have good time and project management skills, this is not the class for you.
- There is a form of assignment due at every class, and everything we do in class will build on what was learned previously. If you miss a class, make sure to review and catch up before the next class. If you don't, you will be lost and get further behind.
- When doing assignments, make sure to closely follow the provided instructions. The ability to follow instructions is a critical programming skill! Also, when programming, get in the habit of taking your time to get the details right. It will save you much frustration and confusion downstream: in writing a structured program, a seemingly minor detail that was glossed over in a haste has a way of resurfacing and tripping you.
- Get help early: approach the instructor or the TA when you first have trouble understanding a concept or homework problem. Please note that certain problems are not easily communicated via email, especially when the lack of understanding of the very nature of the problem is the first stumbling block. It will be easier to come and see instructors in person.
- Turn off your cell phone in class. Non-class-related activities, including Facebook, twitter, email, web surfing, are strictly forbidden. Violations will incur a penalty on your participation score.
Remediation and Justification
Policies on late work are noted above. Exceptions may be made, at the instructor's discretion, in the case of true emergencies, for which explicit documentation must be provided. Penalties for late work or absences may be waived for documented emergencies.
For planned, justified, absences or late work, advance notice must be provided. Valid reasons for missing class include the following:
- A religious observance: advance written notice is required
- A medical emergency (including mental health emergencies): submit a signed letter from a doctor
- A family emergency (death, birth, natural disaster, etc.): submit a signed letter from an authority
Cheating will not be tolerated. Violations, including plagiarism, will be seriously dealt with, and could result in a failing grade for the entire course. Working together on assignments is allowed strictly under a set of conditions noted above; failing to meet them will amount to a violation of academic integrity and will be handled accordingly. For all other issues of academic integrity, refer to the University Guidelines on Academic Integrity here.
If you have a disability for which you are or may be requesting an accommodation, you are encouraged to contact both your instructor and DRS (Disability Resources and Services), 140 William Pitt Union, 412-648-7890or 412-838-7355 (TTY) as early as possible in the term. DRS will verify your disability and determine reasonable accommodations for this course.