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.
Generally, this is not a good idea. While content is indeed on-line, a large part of the course is on-campus. Office hours, project group work and of course the CBTF-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 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 make sure you are using your university account, e.g.
not your personal account, e.g.
email@example.com. If you have not yet claimed your Google
university account, please consult the appropriate Technology Services guide:
For additional assistance, STAT385 has this nice walkthrough guide for undergraduate students.
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.