Running code is critical to finding new insights in Zepl. Wether you are using the notebook to explore a sample data set for the first time or running a trained model on billions of records, you are running code. Zepl primarily bills by tracking how long compute resources are running for, since so much of the value and cost of running Zepl come from running cloud compute resources, so it is important to understand how to manage the lifecycle of these resources.
The purple Run button in the upper left of the notebook can be used to run all of the paragraphs in the notebook in order. Many people interact with notebooks paragraph by paragraph as well - to run a single paragraph at a time, you can click on the small arrow play button at the upper right of any paragraph. Additional notebook operations, such as stopping a notebook container, are also available from the top control menu of the notebook.
Run button at the top of the notebook
Every time you run a notebook, you are spinning up a container resource which contains an "image", which is a prebuilt environment with all the libraries and settings your team needs for reproducible data science. When you spin up a container, you lock in these runtime settings (image and container resource). You can learn more about these settings here.
When you have developed a notebook that you want to run end to end at regular intervals, you can schedule it to run automatically with the Job Scheduling feature.