Running

Python runs on Vistazo's servers, so a notebook runs the same from a laptop, a phone or a locked-down browser. Each person gets their own kernel for each notebook. A kernel is the running Python that holds your variables between cells. It can't reach your browser or your sign-in, and nobody else's code runs in yours.

• Run cell runs one cell. Shift+Enter runs it and moves to the next Python or data cell, adding a Python cell if there is none.
• Run all runs every Python and data cell from the top in the same kernel, overwriting values from earlier runs as it goes.
• Restart, in the ⋯ menu, clears every variable and runs nothing. Restart and then Run all to be sure the outputs match the code as written.
• Stop interrupts the running cell and keeps everything else.

A run stops at the first cell that fails, since the cells below depend on what it didn't define. A Python cell is marked outdated when its own code changed after it ran, or when a cell above it was edited or ran again. A data cell is marked outdated only when its own form changes. An outdated cell keeps its output, but that output may no longer follow from the code.

The first run after you open a notebook starts a session, meaning your kernel and the variables it holds. Starting one takes a few moments. When every kernel is in use, the page shows Session queued, and the run starts as soon as one frees up. Stop gives up your place. Your variables are saved as you go and kept for about a day after your last run, so coming back within that time brings them back. After that the session starts fresh, and Run all rebuilds it.

Running a notebook needs edit access, and its outputs are then what everyone reads. A viewer reads the last run and its outputs, and can run the notebook with their own values in the Parameters tab, which saves nothing (Parameters).

Each cell's output sits under it. Tables show as tables, figures as images, and printed text as text.

While a cell's code is open, an Output bar sits between the code and the result. For a table it switches between Table and JSON, with Copy and Download. Those give CSV from the table view and JSON from the JSON view, with the columns in the table's order. Printed text has Copy and Download as a .txt file.

Outputs are saved with the run, so the people you share with read results without running anything. Figures and large tables are stored as files and count against your storage, like any upload. A notebook keeps its five most recent runs, and a run is cleared after 30 days.

A few tools return more rows to a notebook than to the built-in assistant or your agent, because the rows go to pandas rather than a model. Weather's storm_events and earthquakes return up to 10,000 rows, and Countries' get_data up to 12,000. Storm events with include_narrative stay at 1,000. Every other tool returns the same rows either way.

Running cells uses your compute allowance, counted per second of execution. It costs the same whether you, the built-in assistant, your agent or a schedule started the run. Pulling data is free, as every fetch is, and running cells calls no model. See Usage.