Debugging đ
Table of contents
- Cells and the Autograder
- Why does running a particular cell cause my kernel to die?
- How do I quickly run all the cells in a notebook?
- Why does
grader.check_all()
fail, if all previous tests passed? - Why does a notebook test fail now, when it passed before and I didnât change my code?
- Why did a Gradescope test fail, when all the notebookâs tests passed?
- Why do I get an error saying grader is not defined?
- Iâm positive I have the right answer, but the test fails. Is there a mistake in the test?
- Specific Errors
- DataHub
Cells and the Autograder
Why does running a particular cell cause my kernel to die?
If one particular cell seems to cause your kernel to die, your code is probably incorrect in a way that is causing the computer to use more memory than it has available. For instance: your code is trying to create a gigantic array. To prevent from crashing the entire server, the kernel will âdieâ. This is an indication that there is a mistake in your code that you need to fix.
How do I quickly run all the cells in a notebook?
Go to the Cell menu in the top toolbar, then âRun All.â You can also select a certain cell and run all cells before this point, or run all cells after this point. You should run all the cells in your notebook before submitting to confirm that you pass all the tests.
Why does grader.check_all()
fail, if all previous tests passed?
This can happen if you âoverwriteâ a variable that is used in a question. For instance, if Question 1 asks you to store your answer in a variable named foo, and later on in the notebook you change the value of foo, youâll see the test after Question 1 pass, but the test at the end of the notebook fail. Make sure to rename later instances of that variable so youâre not overwriting it.
Why does a notebook test fail now, when it passed before and I didnât change my code?
You probably ran your notebook out of order. Re-run previous cells.
Why did a Gradescope test fail, when all the notebookâs tests passed?
This can happen if youâre running your notebookâs cells out-of-order. The autograder runs your notebook top-to-bottom. If youâre defining a variable at the bottom of your notebook and using it at the top, the Gradescope autograder will fail because it doesnât recognize the variable when it encounters it.
This is why we recommend running Kernel -> Restart and Run All: it âforgetsâ all of the variables and runs the notebook from top-to-bottom, just like the Gradescope autograder will. This will highlight any issues. Find the first cell that raises an error. Make sure that all of the variables used in that cell have been defined above that cell, and not below.
Why do I get an error saying grader is not defined?
If it has been a while since youâve worked on an assignment, the kernel will shut itself down to preserve memory. When this happens, all of your variables are forgotten, including the grader. Thatâs OK: youâll just need to re-run all of the cells. The easiest way to do this is by using Kernel -> Restart and Run All.
Iâm positive I have the right answer, but the test fails. Is there a mistake in the test?
While you might see the correct answer displayed as the result of the cell, chances are it isnât being stored in the answer variable. Make sure you are assigning the result to the answer variable. Make sure there are no typos in the variable name.
Specific Errors
A general rule of thumb when debugging is to look at the very last line of an error message. Thatâs usually the most informative part of the message, and will often tell you directly whatâs wrong.
isinstance(..., numbers.Integral)
This error is telling you that the answer should be an integer, but your answer is not. This often happens when youâve done some intermediate work towards the answer and saved an intermediate result in the answer variable instead of the final result.
Sometimes instead of isinstance(..., numbers.Integral)
, youâll see something like isinstance(..., bpd.DataFrame)
. This is saying that the answer should be a DataFrame, but yours was something else. The rest of the above still applies.
Check the type of your answer variable with type()
. Is it what you expected?
... object is not callable
This often happens when you use a default keyword (like str
or list
) as a variable name, for instance list = [1, 2, 3]
. These errors can be tricky because they donât error on their own, but cause problems when we try to use (for example) the name list
later on in the notebook (e.g. to convert something to a list).
To fix the issue, identify any such lines of code, change your variable names to be something else, and restart your notebook.
No module named 'babypandas'
This can happen if you click the name of a course other than DSC 10 when logging into DataHub. Hereâs how to âswitchâ your DataHub to DSC 10 mode:
- Click âControl Panelâ in the top right
- Click âServicesâ, then click âmanual-resetterâ
- Click âResetâ (if a pop-up box appears, click okay)
- Log back into DataHub and it should allow you to select a course again â select DSC 10
Other errors
It can be difficult to decipher the meaning of error messages in Python. Here is a useful guide. You can also ask in office hours, or on Campuswire, provided you are not posting your code publicly or otherwise giving away the answer in your post. Understanding cryptic error messages is a skill that comes with experience.
DataHub
When I click an assignment link on the course website, I see a black screen with a bunch of text. What should I do?
This is usually whatâs called a âmerge conflictâ, which means that DataHub wasnât able to combine the versions of the assignments we released with the versions you worked on. This should only happen in rare circumstances. Thereâs a fix that prevents you from losing any of your work:
- Go directly to DataHub (datahub.ucsd.edu). After opening DataHub, instead of clicking
dsc10-2022-wi
, click the box next to it, then click rename, then rename it to something else (likedsc10-2022-wi-old
). - Click the assignment link on the course website again. Now youâll have a new
dsc10-2022-wi
folder in your DataHub, but the work in it will be blank. When you click an assignment link on the course website it will always bring you to this folder, but all of your previous work will still be in the old folder. If youâd prefer, you can manually transfer your work to the new folder, but thatâs probably not necessary.
Why canât I log in to Datahub?
Log out of all Google accounts or open an incognito window. When prompted, enter your full UCSD email, username@ucsd.edu
, as your credentials.
How can Extension Students access Datahub?
Extension students may receive separate accounts for the purpose of accessing Datahub. To look up your account information and reset any additional account passwords, visit https://sdacs.ucsd.edu/~icc/index.php and enter your AX account in the username field and your UID in the Student ID field (e.g. âaxNNNNâ, âcs120sp20aaâ, etc.)
My notebook wonât load. Is Datahub down?
Sometimes Datahub does have availability issues. Usually it is back up and running again within an hour. In other instances, there are some things you can do to get the notebook running again: Make sure your internet connection is working. If you can, restart your server by clicking the button at the top right labeled âControl Panelâ, then select âStop My Serverâ, followed by âStart My Serverâ. If that doesnât work, try restarting your computer and using a different browser. Whenever you resume working on a notebook, run all cells youâve previously completed. If your problem persists after trying all these steps, please notify us.