Skip to content

Commit f6e385e

Browse files
authored
Emphasised the necessity to copy into a new file
Copying into a new notebook seems to be a crucial step in solving export problems this year. Even with all problems fixed, the file won't export until it has been copied into a new .ipynb file.
1 parent 7188eb1 commit f6e385e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Export Troubleshooting.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
## Export Troubleshooting:
22
1. Comment out the `%%capture` line in the cell that actually runs the exporting. Towards the bottom of the whole thing you might find something like an error message that may give you a clue as to what is going wrong. Likely it will be a LaTeX issue and say something about adding a missing `$`.
33

4-
2. Check images are all inserted with `Image(...)`.
4+
2. Do a quick check that images are all inserted with `Image(...)`.
55

6-
a. If any images were previously inserted like `![](https://drive.google.com/uc?export=view&id=...)` it may be necessary to COPY ALL WORK into a new notebook because some information gets stored in the background of a `.ipynb` file, and I have seen at least 1 case of this causing problems even once the offending line is removed.
6+
3. Do a quick check of common LaTeX issues (often shows an error like `! Missing $ inserted.`) see below.
77

8-
3. LaTeX issues (often shows an error like `! Missing $ inserted.`) -- See below for LaTeX specific tips.
8+
4. **Make a new `.ipynb` file and copy across cells a few at a time, making sure you can export the new `.ipynb` as you go.** Either you will be able to identify which cell is actually causing the problem, or you will get all the way to the end and it will continue to export in which case the problem is fixed!
9+
(Just copying everything to a new notebook has been the solution for a few people this year, so I think Colab may have added some sort of history to files which can screw up the export process...)
910

10-
4. Make a new `.ipynb` file and copy across cells a few at a time, making sure you can export the new `.ipynb` as you go. That will help narrow down which cell has a problem if it has been difficult to find so far.
1111

1212
<br>
1313

0 commit comments

Comments
 (0)