About this book#
How to use this book#
Executing and editing code#
Press the button on the toolbar, then the button to edit and run the code.
Note
This might take a while to load after new releases of the book.
How to contribute#
Converting Markdown files to Jupyter notebooks#
All V&V cases are tracked as Markdown files in the {MyST}NB format, which allows
us to use useful MyST directives and track the code in the same raw text file.
You can run jupytext --sync on the .md MyST-NB file to convert it to a jupytext notebook.
Running the same command will sync all changes between the files.
You can also download any case as a Jupyter notebook by clicking the button on the toolbar and selecting the .ipynb option.
Adding a case#
Create a Jupyter notebook for editing the case.
Run
jupytext --set-formats ipynb,myston the.ipynbnotebook file. This creates a āpairedā Markdown file which we will be tracking on git.Add the path to the case to the table of contents located at
./report/_toc.ymlunder the appropriate chapter.Note
The files in the table of contents lack an extension. This is useful for testing since jupyter-book will prioritize
.ipynbfiles over.mdfiles when building the book.
You can build the book locally by running jupyter-book build ./report.
Coding Guidelines#
TODO
Final Touches#
Add category tags by using the {tags} directive below the case title as follows:
```{tаgs} tag1, tag2 ```Add āhideā tags to the code cells in the case where appropriate. Ideal visible outputs only contain figures.
Format the code using black on the notebook file as follows
black notebook.ipynb.Note
Jupyter notebook support for black can be installed with
pip install black[jupyter].