Comment (by Gabriele Bozzola):

Thank you very much for your taking the time to type the reasoning behind what is being done. It all makes sense.

My comment comes from putting myself in the shoes of a new user, so the use I had in mind for the notebook is “document to describe the first steps to someone that wants to try out the code”. For this use case, I think that the notebook (primarily the visualization section) obfuscates some points by adding complexity. For instance, when I tell people how to make a visualization of timeseries with kuibit, I tell them “cd into the directory of your data, and run plot_timeseries.py --variable "rho" --reduction "maximum"”, but this is what we have (in the PR at least):

%%bash
# See comment before
export PYTHONUSERBASE="$HOME/Cactus"

# Here we define a bash variable that contains the path where
# the simulation data lives. We do so to keep this tutorial general.
# Normally you would just input the path or you would run the
# script directly from the data directory.
datadir=$(dirname $(./simfactory/bin/sim get-output-dir tov_ET))

# Plot a timeseries with the maximum of the density
./utils/Analysis/kuibit/examples/bins/plot_timeseries.py --datadir $datadir \
--variable "rho" --reduction "maximum" --outdir $datadir


from IPython.display import Image

# datadir is the top-level directory that contains that data for
# a given si
--

Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2577/cactustutorialipynb-contains-code-only