diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..f1ee056 --- /dev/null +++ b/.gitignore @@ -0,0 +1,6 @@ +.Rproj.user +.Rhistory +.RData +.Ruserdata +**.DS_Store +/.quarto/ diff --git a/CODE_OF_CONDUCT.qmd b/CODE_OF_CONDUCT.qmd new file mode 100644 index 0000000..c67619e --- /dev/null +++ b/CODE_OF_CONDUCT.qmd @@ -0,0 +1,94 @@ +### Introduction + +We are committed to creating a friendly and respectful place for +learning, teaching and contributing. All participants in our course and +communications are expected to show respect and courtesy to others. + +To make clear what is expected, everyone participating in STAT 306 activities +is required to conform to the Code of Conduct. This Code of Conduct applies to +all spaces managed by STAT 306 including, but not limited to, class meetings, +email communication, and online forums such as Piazza and GitHub. The STAT 306 +teaching team are expected to assist with the enforcement of the Code of +Conduct. + +The STAT 306 Instructor(s) is responsible for enforcing the Code of Conduct. +All reports will be reviewed by the Instructor(s) and will be kept +confidential. + +### The STAT 306 Code of Conduct + +We are dedicated to providing a welcoming and supportive +environment for all people, regardless of background or identity. As such, we +do not tolerate behaviour that is disrespectful to our teachers or learners or +that excludes, intimidates, or causes discomfort to others. We do not tolerate +discrimination or harassment based on characteristics that include, but are not +limited to, gender identity and expression, sexual orientation, disability, +physical appearance, body size, citizenship, nationality, ethnic or social +origin, pregnancy, familial status, veteran status, genetic information, +religion or belief (or lack thereof), membership of a national minority, +property, age, education, socio-economic status, technical choices, and +experience level. + +Everyone who participates in STAT 306 activities is required to conform to this +Code of Conduct. It applies to all spaces managed by STAT 306 including, but +not limited to, class meetings, email communication, and online forums such as +Piazza and GitHub. The STAT 306 teaching team are expected to assist with the +enforcement of the Code of Conduct. + +#### Expected Behavior + +All participants in our events and communications are expected to show respect +and courtesy to others. All interactions should be professional regardless of +platform: either online or in-person. In order to foster a positive and +professional learning environment we encourage the following kinds of +behaviours in all STAT 306 events and platforms: + +- Use welcoming and inclusive language +- Be respectful of different viewpoints and experiences +- Gracefully accept constructive criticism +- Focus on what is best for the community +- Show courtesy and respect towards other community members + +Note: See the [four social rules](https://www.recurse.com/manual#sub-sec-social-rules) for further recommendations. + +#### Unacceptable Behavior + +Examples of unacceptable behavior by participants at any STAT 306 event/platform include: + +- written or verbal comments which have the effect of excluding people on the basis of membership of any specific group +- causing someone to fear for their safety, such as through stalking, following, or intimidation +- violent threats or language directed against another person +- the display of sexual or violent images +- unwelcome sexual attention +- nonconsensual or unwelcome physical contact +- sustained disruption of talks, events or communications +- insults or put downs +- sexist, racist, homophobic, transphobic, ableist, or exclusionary jokes +- excessive swearing +- incitement to violence, suicide, or self-harm +- continuing to initiate interaction (including photography or recording) with someone after being asked to stop +publication of private communication without consent + +#### Consequences of Unacceptable Behavior + +Participants who are asked to stop any inappropriate behavior are expected to +comply immediately. This applies to any STAT 306 events and platforms, either +online or in-person. If a participant engages in behavior that violates this +code of conduct, the teaching team may warn the offender and or engage the DSCI +310 Instructor to investigate the Code of Conduct violation and impose +appropriate sanctions. + +### Incident Reporting Guidelines + +If someone violates the Code of Conduct during a STAT 306 event or in an online +space outside of organised events, we ask that you report it to the +Instructor(s). The current instructor(s) of STAT 306 is(are) Lucy Gao +and Tiffany Timbers. +An email to tiffany.timbers[-at-]stat.ubc.ca will be seen by Tiffany Timbers. +To report a STAT 306 code of conduct violation +that will not be seen by your instructor, an +alternative contact person is Bruce Dunham, Professor of Teaching in the +Department of Statistics at UBC. His email is b.dunham[-at-]stat.ubc.ca. + +## Attribution +- Derived from the [Carpentries Code of Conduct](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html) \ No newline at end of file diff --git a/LICENSE.md b/LICENSE.md new file mode 100644 index 0000000..ebb0c84 --- /dev/null +++ b/LICENSE.md @@ -0,0 +1,41 @@ +# Instructional Material + +Copyright (c) 2024 Lucy Gao & Tiffany A. Timbers + +All instructional material in the `stat-306-student` repository is made available under the **Attribution 4.0 International** ([CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)). + +This is a human-readable summary of (and not a substitute for) the [license](https://creativecommons.org/licenses/by/4.0/legalcode). + +You are free: + +- to **Share**---copy and redistribute the material in any medium or format +- to **Adapt**---remix, transform, and build upon the material + +for any purpose, even commercially. + +The licensor cannot revoke these freedoms as long as you follow the license terms. + +Under the following terms: + +- **Attribution**---You must give appropriate credit (mentioning that your work is derived from work that is Copyright © Software Carpentry and, where practical, linking to http://software-carpentry.org/), provide a \[link to the license\]\[cc-by-human\], and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. + +**No additional restrictions**---You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits. With the understanding that: + +Notices: + +- You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation. +- No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material. + +# Software + +Except where otherwise noted, the example programs and other software provided in the `DSCI_524_collab-sw-dev_students` repository are made available under the MIT license. + +MIT License + +Copyright (c) 2024Lucy Gao & Tiffany A. Timbers + +Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. diff --git a/README.md b/README.md new file mode 100644 index 0000000..dc3c5c1 --- /dev/null +++ b/README.md @@ -0,0 +1,9 @@ +## STAT 306 public course website repository + +Lucy Gao & Tiffany Timbers, 2024 + +- [STAT 306 course website]() + +## License: + +Software licensed under the [MIT License](https://spdx.org/licenses/MIT.html), non-software content licensed under the [Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) License](https://creativecommons.org/licenses/by-nc-sa/4.0/). See the [license file](LICENSE.md) for more information. diff --git a/_quarto.yml b/_quarto.yml new file mode 100644 index 0000000..1c32a13 --- /dev/null +++ b/_quarto.yml @@ -0,0 +1,25 @@ +project: + type: website + output-dir: docs + +website: + sidebar: + style: "docked" + search: true + contents: + - section: "Syllabus" + contents: + - index.qmd + - section: "Code of Conduct" + contents: + - CODE_OF_CONDUCT.qmd + +format: + html: + theme: cosmo + css: styles.css + toc: true + +editor: visual + + diff --git a/about.qmd b/about.qmd new file mode 100644 index 0000000..0c6f4a2 --- /dev/null +++ b/about.qmd @@ -0,0 +1,9 @@ +--- +title: "About" +--- + +About this site + +```{r} +1 + 1 +``` diff --git a/index.qmd b/index.qmd new file mode 100644 index 0000000..f48d277 --- /dev/null +++ b/index.qmd @@ -0,0 +1,231 @@ +--- +title: "STAT 306: Finding Relationships in Data" +--- + +## Time and place + +- See UBC Calendar + +## Course description +Modelling a response (output) variable +as a function of several explanatory (input) variables: +multiple regression for a continuous response, +logistic regression for a binary response, +and log-linear models for count data. +Finding low-dimensional structure: principal components analysis. +Cluster analysis. + +## Prerequisite +One of MATH 152, MATH 221, +MATH 223 and one of STAT 200, STAT 241, STAT 251, STAT 300, BIOL 300, BUSI 291, +COMM 191, COMM 291, ECON 325, ECON 327, FRST 231, PSYC 218, PSYC 278 +and one of MATH 302, STAT 302. + +## Textbook + +We will be using a collection of resources available online. These +include: + +- [DSCI 310 course + notes](https://ubc-dsci.github.io/reproducible-and-trustworthy-workflows-for-data-science) +- [R packages](https://r-pkgs.org/) +- [Python packages](https://py-pkgs.org/) + +## Hardware & software + +Students are required to bring a laptop to both lectures and tutorials. +We will be using the the programming language R, +the Quarto scientific and technical publishing system, +and the RStudio Desktop integrated development environment (IDE). +Visit the links below to download the version of software needed +for your operating system, and install it on your laptop. +- [R programming language](https://cran.r-project.org/) +- [RStudio Desktop](https://posit.co/download/rstudio-desktop/) +- [Quarto](https://quarto.org/docs/get-started/) + +## Objectives +On completing the course, +students should be able to demonstrate an understanding of the techniques +and applications of well known ideas in linear modelling, +including model fitting, model selection, model diagnostics, +as well as basic ideas for generalised linear models and principal +components analysis. + +## Learning outcomes + +1. Understand the principles of model fitting and inference for linear models +involving a response variable with a single explanatory variable. +2. Understand the role of residuals in linear regression, including model +diagnostics. +3. Appreciate and apply key concepts of linear modelling when there is +more than one explanatory variable. +4. Understand and apply linear model theory to cases where at least one +explanatory variable is categorical. +5. Critique studies that involve regression methods, +including identification of any flaws and limitations to inferences. +6. Apply commonly used methods for model selection +in a multiple regression context. +7. Use and interpret common approaches to identifying influential data +points and outliers in a regression context. +8. Apply and interpret linear models that involve the transformation of +one or more variable. +9. Apply and interpret a principal components analysis (PCA). +10. Understand and apply concepts from generalised linear modelling, +including logistic and Poisson regression. +11. Apply linear modelling methods in the software R, using appropriate +R functions and interpreting the output. + +## Teaching Team + +| Position | Name | Email | Office Hours | Office Location | +|:--------------------:|:---------------:|:--------------------------------:|:----------------:|:---------------:| +| Instructor | Lucy Gao | | TBD | See Canvas | +| Instructor | Tiffany Timbers | tiffany.timbers[-at-]stat.ubc.ca | TBD | See Canvas | +| TA | | | TBD | See Canvas | + +## Assessment + +### Grading breakdown + + + +## Schedule at a glance + + + +### Assessment schedule + +In general, assignments will be due 11:59 PM on Saturdays. However, in +the final week of classes, all assignments need to be submitted by the +final day of classes, thus we have two alternative due dates that week. + + + +## Policies + +### Code of Conduct + +All participants in our course and communications are expected to show +respect and courtesy to others. To creating a friendly and respectful +place for learning, teaching and contributing, you are expected to read +and follow the [DSCI 310 Code of +Conduct](https://ubc-dsci.github.io/dsci-310-student/coc.html). + +### Late registration + +Students who register for the class late have 1 week from their +registration date on Canvas to complete all prior assignments. + +### Late assignments / mid-term exam absence + +Students **must be present** at the invigilation venue (in class, on +Zoom, examination centre, etc) to take the mid-term exam; otherwise they +will be considered to have missed the mid-term exam and will be assigned +a grade of zero. + +Students who will miss the mid-term exam **must provide a +self-declaration prior to the mid-term exam** and make arrangements +(e.g., schedule an oral make-up mid-term exam) with the Instructor. +Failing to present a declaration within a reasonable timeframe before +the mid-term exam will result in a grade of zero. + +A late submission is defined as any work submitted after the deadline. +For a late submission, the student will receive a 75% scaling of their +grade for the first occurrence, 50% scaling of their grade for the +second occurrence, and will receive a grade of 0 for subsequent +occurrences. + +Students who miss an assignment or quiz can request an academic +concession. From the [UBC Senate policy on academic +concession](https://senate.ubc.ca/sites/senate.ubc.ca/files/downloads/20190515_V_135_Academic_Concession-Approved.pdf), +grounds for academic concession can be illness, conflicting +responsibilities, or compassionate grounds. Examples of compassionate +grounds, from the above policy, include “a traumatic event experienced +by the student, a family member, or a close friend; an act of sexual +assault or other sexual misconduct experienced by the student, a family +member, or a close friend; a death in the family or of a close friend.” + +To request an academic concession, students should immediately email a +completed and signed [academic concession form to the course +Instructor](https://github.com/UBC-MDS/UBC-MDS.github.io/blob/master/img/Template%20-%20In-Term%20Academic%20Concessions%20Self%20Declaration.pdf?raw=1). +Upon receiving the form, the Instructor will make a decision about how +to proceed. Failure to present valid documentation may result in a +failing grade. + +### Re-grading + +If you have concerns about the way your work was graded, please contact +the TA who graded it within one week of having the grade returned to you +through Piazza. After this one-week window, we may deny your request for +re-evaluation. Also, please keep in mind that your grade may go up or +down as a result of re-grading. + +### Missed final exam + +Students who miss the final quiz must report to their faculty advising +office within 72 hours of the missed exam, and must supply supporting +documentation. Only your faculty advising office can grant deferred +standing in a course. You must also notify your instructor prior to (if +possible) or immediately after the exam. Your instructor will let you +know when you are expected to write your deferred exam. Deferred exams +will ONLY be provided to students who have applied for and received +deferred standing from their faculty. + +### Academic concession policy + +Please see [UBC's concession +policy](http://www.calendar.ubc.ca/vancouver/index.cfm?tree=3,329,0,0) +for detailed information on dealing with missed coursework, quizzes, and +exams under circumstances of an acute and unanticipated nature. + +### Academic integrity + +The academic enterprise is founded on honesty, civility, and integrity. +As members of this enterprise, all students are expected to know, +understand, and follow the codes of conduct regarding academic +integrity. At the most basic level, this means submitting only original +work done by you and acknowledging all sources of information or ideas +and attributing them to others as required. This also means you should +not cheat, copy, or mislead others about what is your work. Violations +of academic integrity (i.e., misconduct) lead to the breakdown of the +academic enterprise, and therefore serious consequences arise and harsh +sanctions are imposed. For example, incidences of plagiarism or cheating +may result in a mark of zero on the assignment or exam and more serious +consequences may apply if the matter is referred to the President’s +Advisory Committee on Student Discipline. Careful records are kept in +order to monitor and prevent recurrences. + +A more detailed description of academic integrity, including the +University’s policies and procedures, may be found in the Academic +Calendar at +. + +### Plagiarism + +Students must correctly cite any code or text that has been authored by +someone else or by the student themselves for other assignments. Cases +of plagiarism may include, but are not limited to: + +- the reproduction (copying and pasting) of code or text with none or + minimal reformatting (e.g., changing the name of the variables) +- the translation of an algorithm or a script from a language to + another +- the generation of code by automatic code-generation software + +An "adequate acknowledgement" requires a detailed identification of the +(parts of the) code or text reused and a full citation of the original +source code that has been reused. + +The above attribution policy applies only to assignments. **No code or +text may be copied (with or without attribution) from any source during +a quiz or exam. Answers must always be in your own words. At a minimum, +copying will result in a grade of 0 for the related question.** + +**Repeated plagiarism of any form could result in larger penalties, +including failure of the course.** + +## Attribution + +Parts of this syllabus (particularly the policies) have been copied and +derived from the [UBC MDS +Policies](https://ubc-mds.github.io/policies/). \ No newline at end of file diff --git a/stat-306-student.Rproj b/stat-306-student.Rproj new file mode 100644 index 0000000..8e3c2eb --- /dev/null +++ b/stat-306-student.Rproj @@ -0,0 +1,13 @@ +Version: 1.0 + +RestoreWorkspace: Default +SaveWorkspace: Default +AlwaysSaveHistory: Default + +EnableCodeIndexing: Yes +UseSpacesForTab: Yes +NumSpacesForTab: 2 +Encoding: UTF-8 + +RnwWeave: Sweave +LaTeX: pdfLaTeX diff --git a/styles.css b/styles.css new file mode 100644 index 0000000..2ddf50c --- /dev/null +++ b/styles.css @@ -0,0 +1 @@ +/* css styles */