This module contains the
Scene class, which serves as a “universe” or context for all actions
performed by a script. The scene object is accessible through the module-level
The scene manages a list of
Pipeline objects, which will be visible in images and videos
when rendering the scene through a
Viewport. Futhermore, you can save the entire
scene to a
.ovito state file, which can be viewed in the graphical OVITO application or stored for later use.
This module-level variable points to the global
Sceneobject, which serves as context for all operations performed by the script. The
Sceneobject represents the program state and provides access to the contents of the visualization scene:
import ovito # Retrieve the output data of the pipeline that is currently selected in OVITO: data = ovito.scene.selected_pipeline.compute()
A module-level attribute reprting the OVITO program version number (as a tuple of three ints).
Module-level attribute reporting the OVITO program version (as a string).
This class encompasses all data of an OVITO program session (basically everything that gets saved in a
.ovitostate file). It manages the list of objects (i.e.
Pipelineinstances) that are part of the three-dimensional scene and which will show up in rendered images.
From a script’s point of view, there exists exactly one universal instance of this class at any time, which is accessible through the
ovito.scenemodule-level variable. A script cannot create another
Sceneinstance by itself.
The list of
Pipelineobjects that are currently part of the three-dimensional scene. Only pipelines in this list will display their output data in the viewports and in rendered images. You can add or remove a pipeline either by calling its
remove_from_scene()methods or by directly manipulating this list using the standard Python
from ovito import scene from ovito.io import import_file pipeline = import_file('input/simulation.dump') # Insert the pipeline into the visualization scene. pipeline.add_to_scene() # It's now part of the 'scene.pipelines' list. assert(pipeline in scene.pipelines) # If needed, we can take it out again. pipeline.remove_from_scene()
Saves the scene including all data pipelines that are currently part of it to an OVITO session state file. This function works like the Save State As menu function of OVITO. Note that pipelines that have not been added to the scene will not be saved to the state file.
filename (str) – Output file path
The saved session state may be loaded again using the -o command line option of ovitos or by opening the file in the OVITO desktop application. After loading the state file, the
pipelineslist will contain again all data pipelines that were part of the scene when it was saved. See also this section for more information.
Pipelinethat is currently selected in the graphical OVITO application, or
Noneif no pipeline is selected. Typically, this is the last pipeline that was added to the scene using
This field can be useful for scripts running in the context of the graphical OVITO application which want to perform some action on the currently selected pipeline, e.g. insert a new modifier.
Calling this function at the beginning of a Python script enables activity logging for OVITO’s internal operations. When performing long-running operations, OVITO will print messages to
stderrindicating the current activity, e.g. file reading and writing, modifier execution, or rendering.