You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your in-class, code-writing, code-executing Midterm is coming up this Monday, February 5, in Saieh 247 from 11:30am to 1:20pm. Below are the details of the logistics of taking this in-class computational midterm.
We will begin class by downloading a Jupyter notebook template for writing, saving, and turning in your answers. You will also download any datasets that are required by the exam questions.
Once everyone has done this, we will have everyone turn OFF their Wi-fi and begin the exam.
The exam will be "open computer" in the sense that you can use any resources of code, notebooks, or notes that are on your HARD DRIVE. No internet resources can be used. You can also use paper notes.
Once you have finished your exam, you will signal for one of the TA's to come to your desk as you turn your Wi-fi back on and upload your Jupyter notebook (or R markdown doc) solution file to Canvas.
Your Jupyter notebook should include clear indication of your proposed solutions to each exam question. It should also include your code that produced the solution as well as any extra commentary about how you got that solution.
Good luck. I am having a lot of fun teaching this class this term with you.
The text was updated successfully, but these errors were encountered:
Dear MACS 30100 students,
Your in-class, code-writing, code-executing Midterm is coming up this Monday, February 5, in Saieh 247 from 11:30am to 1:20pm. Below are the details of the logistics of taking this in-class computational midterm.
Your Jupyter notebook should include clear indication of your proposed solutions to each exam question. It should also include your code that produced the solution as well as any extra commentary about how you got that solution.
Good luck. I am having a lot of fun teaching this class this term with you.
The text was updated successfully, but these errors were encountered: