Python session

The Python session runs short Python on the server, next to the simulation you have open. Use it to inspect fields, try a small VTK operation, or run a snippet amAIra suggested. A skill that runs Python follows the same limits.

Where it is

Sign in on the home page, then open Python session on the right side of the viewer. amAIra is the other tab in that panel. Those tabs stay hidden if you open the viewer without that sign-in.

Before a cell will run

What to use it for

• Read arrays, bounds, and field names on the simulation you loaded
• Run a small VTK snippet the session allows
• Try an idea before it exists as a sidebar filter

Everyday clip and warp belong in Filters. Those update the scene tree and the view together. A Python result does not replace that path.

What happens to the session

You load a file or an example
    → the server keeps that simulation
    → you open Python session
    → each cell runs on the server and the output comes back
    → a new upload, or closing the viewer, starts a new context

A cell waits until the server finishes. On a shared cloud account, keep cells short.

For questions beside the editor, use amAIra. Sign-in is covered in Antinode.

Limits

The session is limited on purpose.

• You cannot use import. The names you can use are session, np, vtk, and sometimes scipy.
• A cell is about 8 KB, with about a 10 second limit, and shared cloud accounts are rate limited.
• The session cannot read files on your computer. It sees the simulation on the server.

Troubleshooting