[TODO] Adjust with latest notes.

Author: Murilo Marinho

README.md

@@ -1,5 +1,9 @@
 # Open Executable Books in Robotics
 
++++ {"part": "abstract"}
+This is my abstract!
++++
+
 ## Link for the website
 
 https://marinholab.github.io/OpenExecutableBooksRobotics/

TODO.md

@@ -2,13 +2,24 @@
 
 ## Known issues in `dqrobotics` lessons
 
-1. Originally, the lessons written in `MATLAB` did not allow the use of latex macros. This means that the conversion from those to Jupyter notebooks brought notation as-is, which is not entirely compliant with the [latest notation](https://github.com/IncompleteGuides/lyx-macros). This is a very time consuming task so it will only be attempted with community support or further funding sources.
-1. The current `plot` method using `dqrobotics-pyplot` in the Jupyter notebook is generating a phantom image besides the animation videos. There are instructions online that allow us to tackle this issue, but I haven't been able to find one
+1. Originally, the lessons written in `MATLAB` did not allow the use of latex macros. This means that the conversion from those to Jupyter notebooks brought notation as-is, which is not entirely compliant with the [latest notation](https://github.com/IncompleteGuides/lyx-macros). This is a very time-consuming task, so it will only be attempted with community support or further funding sources.
+2. The current `plot` method
+   using `dqrobotics-pyplot` in the Jupyter notebook is generating a phantom image besides the animation videos.
+   There are instructions online that allow us to tackle this issue, but I haven't been able to find one
 that properly shows the video but not the image.
+3. The latex macros in all lessons do not seem to render well in `jupyterlab`. It's not yet clear to me why.
 
 ## Text-based notebooks
 
 - Converting from traditional Jupyter notebooks to text-based notebooks might be an interesting topic to explore. See
   [link](https://myst-nb.readthedocs.io/en/latest/authoring/text-notebooks.html#authoring-text-notebooks). Classic notebooks
   store cell output on themselves, with implications on version control software. While classic Jupyter notebooks are more
-  easily usable without extensions, `jupytext` seemingly allows for the conversions. See [link](https://jupyterbook.org/en/stable/file-types/myst-notebooks.html).
+  easily usable without extensions, `jupytext` seemingly allows for the conversions. See [link](https://jupyterbook.org/en/stable/file-types/myst-notebooks.html).
+- The so-called [paired notebooks](https://jupytext.readthedocs.io/en/latest/paired-notebooks.html) are possibly the solution. 
+  Given that the latex macros sometimes do not render well in `jupyterlab`, this could become indirectly a solution.
+  The latex support for `myst` is much less hacky, so it is likely that the notebooks exported from the text version
+  are more likely to be compatible with `jupyterlab`.
+
+## Notes
+
+- `jupyterbook2` documentation is at https://next.jupyterbook.org.

loc.py

@@ -0,0 +1,14 @@
+#!/usr/bin/env python
+## From: https://stackoverflow.com/questions/45382122/how-to-count-lines-of-code-in-jupyter-notebook
+from json import load
+from sys import argv
+
+def loc(nb):
+    cells = load(open(nb))['cells']
+    return sum(len(c['source']) for c in cells)
+
+def run(ipynb_files):
+    return sum(loc(nb) for nb in ipynb_files)
+
+if __name__ == '__main__':
+    print(run(argv[1:]))

myst.yml

@@ -26,12 +26,13 @@ project:
   license:
     content:
       id: CC-BY-NC-SA-4.0
-  #exports:
-  #  - format: pdf
+  exports:
+    - format: pdf
+    - template: ieee-typst
   #    date: 10 May 2023
       # https://github.com/myst-templates
   #    template: plain_latex_book
-      #article: basic_lessons/README.md
+      articles: README.md
   #    output: exports/basic_lessons.pdf
 
   toc: