This has come up before. Aaron Thompson had the following to offer:
With the course currently filled, you unfortunately will not be able to register for it until a seat does become available. We also do not do waitlists for our courses. As we approach the beginning of […] term, if a seat remains available on the graduate side of the course, we can move a seat over for undergraduates, but we typically will not do that until at least one week before the term begins.
My suggestion is to just keep monitoring the registration system for fellow students to drop as they make changes in their schedules and try to register at that time.
There is also some more information at the registration page of the department.
Per another email from the departmental stat-undergrad account:
There is no schedule for seat changes. Students can only enable the Notification setting for a desired course in their Course Explorer account, and enroll once alerted that seats are available in their desired section.
Please contact the Statistics Department, and do not contact the instructors.
As the instructors, we are actually ‘outside the loop’ as far as admission is handled. The department handles this with a preference for within-degree students. If there is availability once the term started students from other departments can register on a first-come first-served basis, so please keep an eye open for it. There is nothing more we can do now by the standard process.
For more, see the registration page of the department.
Instruction for this course is on-line. But examinations are in-person, and that make this course an in-person course (which may matters for some other administrative aspects …). So generally, taking it and its CBTF-based exams on-campus is preferred. While content is indeed on-line, a large part of the course is (or: was) on-campus. Office hours, project group work and of course the PrairieTest-administered exams / quizzes. So it is best to think of the course as a regular course best taken during a term in which one is present on campus. If truly needed, exceptions can be made, please contact us with a sufficient reason and ideally some sort of confirmation that you will be away from campus the full term.
In short, no. It is recognized that there is some overlap between the content of STAT 385 and STAT 447. But the overall view of the department is this is still a possible choice for students as STAT 447 goes a little further that STAT 385 and digs a little deeper. Students who are interested in both or either may also consider one of the many other course in the catalogue to broaden their learning experience and knowledge beyond this pair. That said, the combination of taking both is possible.
No. The course has a strong focus of programming methods for use in data science and statistics, and as such there is no direct lead-in or requirement. While STAT 410 was listed as a requirement in the past, it has been decided that we can do away with a formal requirement.
No. The course aims to be suitable for everybody including those with, and without, prior programming experience or classes. Now, given the content of the course, it is likely helpful but anybody willing and able to learn the material should be able to do so during the course.
If you wish to hire a private tutor to assist you with the course content, please see the Department of Statistics tutoring page. This page provides the ability to submit a request for assistance from registered tutors.
Please don’t.
Unless an error or omission can be demonstrated for the grade, it should be considered final.
Please make sure you are logged into GitHub. In addition, please make sure that you have paired your GitHub username with us, i.e. the course admins. Pairing is not instanteanous. The process is automatically triggered each evening during the first two weeks.
For additional assistance, please see the GitHub page not found guide, also courtesy of STAT385.
Two requirements have to be met:
Please see TechServices if you still have issues.
Yes, a known issue. See the good writeup in Happy Git With R, Section 10 ‘Cache credentials for HTTPS;. One of the methods mentioned there for Linux works perfectly well for us in RStudio Cloud. The shell command
git config --global credential.helper "cache --timeout=10000000"
or, equally, from R as this command:
system("git config --global credential.helper \"cache --timeout=10000000\"")
will set a timeout of that many seconds – or about sixteen weeks which should get you through the term. The other method is fancier and more powerful: register ssh keys. But that is beyond our scope here.