diff --git a/autograder_gradescope/autograder_gradescope.md b/autograder_gradescope/autograder_gradescope.md index 675c28b..3b75111 100644 --- a/autograder_gradescope/autograder_gradescope.md +++ b/autograder_gradescope/autograder_gradescope.md @@ -45,16 +45,16 @@ The best course of action is to find the test case that failed and use that as a
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. The easiest way to fix this is by restarting your kernel and rerunning all the cells. To do this, in the top left menu, click Kernel
-> Restart and Run All Cells
.
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. The easiest way to fix this is by restarting your kernel and rerunning all the cells. To do this, in the top left menu, click Kernel
-> Restart and Run All Cells
.
While you might see the correct answer displayed as the result of the cell, chances are your solution isn’t being stored in the answer variable. Make sure you are assigning the result to the answer variable and that there are no typos in the variable name. Finally, restart your kernel and run all the cells in order: Kernel
-> Restart and Run All Cells
.
While you might see the correct answer displayed as the result of the cell, chances are your solution isn’t being stored in the answer variable. Make sure you are assigning the result to the answer variable and that there are no typos in the variable name. Finally, restart your kernel and run all the cells in order: Kernel
-> Restart and Run All Cells
.
grader.export(run_tests=True)
fail if all previous tests passed?You probably ran your notebook out of order. Re-run all previous cells in order, which is how your code will be graded.
+You probably ran your notebook out of order. Re-run all previous cells in order, which is how your code will be graded.
Note that you may loose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend saving your work as often as possible.
+Note that you may loose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend saving your work as often as possible.
If this does not fix the issue, it could be a problem with your code, usually the last cell that executed before your kernel crashed. Double check your logic, and feel free to make a private post on Ed if you’re stuck!
It is normal for a cell to take a few seconds – sometimes a few minutes – to run. If it’s is taking too long, however, you have several options:
pandas
function?This often happens when you use a default keyword (like str
, list
, range
, sum
, or max
) as a variable name, for instance:
sum = 1 + 2 + 3
These errors can be tricky because they don’t error on their own but cause problems when we try to use the name sum
(for example) later on in the notebook.
-To fix the issue, identify any such lines of code, change your variable names to be something more informative, and restart your notebook.
+To fix the issue, identify any such lines of code, change your variable names to be something more informative, and restart your notebook.
Python keywords like str
and list
appear in green text, so be on the lookout if any of your variable names appear in green!
diff --git a/jupyter_datahub/jupyter_datahub.md b/jupyter_datahub/jupyter_datahub.md
index 75a8098..d0bc8e4 100644
--- a/jupyter_datahub/jupyter_datahub.md
+++ b/jupyter_datahub/jupyter_datahub.md
@@ -38,7 +38,7 @@ When you see a message like this:
2. [Restart your kernel](https://ds100.org/debugging-guide/jupyter101/jupyter101.html#restarting-kernel)
3. [Rerun your cells](https://ds100.org/debugging-guide/jupyter101/jupyter101.html#running-cells)
-Note that you may loose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend [saving your work](https://ds100.org/debugging-guide/jupyter101/jupyter101.html/saving-your-notebook) as often as possible.
+Note that you may loose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend [saving your work](https://ds100.org/debugging-guide/jupyter101/jupyter101.html#saving-your-notebook) as often as possible.
If this does not fix the issue, it could be a problem with your code, usually the last cell that executed before your kernel crashed. Double check your logic, and feel free to make a private post on Ed if you're stuck!
diff --git a/pandas/pandas.md b/pandas/pandas.md
index 2652c6b..c00ed7c 100644
--- a/pandas/pandas.md
+++ b/pandas/pandas.md
@@ -24,7 +24,7 @@ This note is (mostly) structured around the error messages that show up at the b
## My code is taking a really long time to run
It is normal for a cell to take a few seconds -- sometimes a few minutes -- to run. If it's is taking too long, however, you have several options:
-1. Try restarting the kernel. Sometimes, Datahub glitches or lags, causing the code to run slower than expected. [Restarting the kernel](https://ds100.org/debugging-guide/jupyter_shortcuts/jupyter_shortcuts.html#restarting-kernel) should fix this problem, but if the cell is still taking a while to run, it is likely a problem with your code.
+1. Try restarting the kernel. Sometimes, Datahub glitches or lags, causing the code to run slower than expected. [Restarting the kernel](https://ds100.org/debugging-guide/jupyter101/jupyter101.html#restarting-kernel) should fix this problem, but if the cell is still taking a while to run, it is likely a problem with your code.
2. Scrutinize your code. Am I using too many for loops? Is there a repeated operation that I can substitute with a `pandas` function?
## Why is it generally better avoid using loops or list comprehensions when possible?
@@ -44,7 +44,7 @@ This often happens when you use a default keyword (like `str`, `list`, `range`,
These errors can be tricky because they don’t error on their own but cause problems when we try to use the name `sum` (for example) later on in the notebook.
-To fix the issue, identify any such lines of code, change your variable names to be something more informative, and [restart your notebook](https://ds100.org/debugging-guide/jupyter_shortcuts/jupyter_shortcuts.html#restarting-kernel).
+To fix the issue, identify any such lines of code, change your variable names to be something more informative, and [restart your notebook](https://ds100.org/debugging-guide/jupyter101/jupyter101.html#restarting-kernel).
Python keywords like `str` and `list` appear in green text, so be on the lookout if any of your variable names appear in green!