External file

../../../_images/file_source_panel.png

The External File panel allows you to configure the data source for the current pipeline, specifying which external file(s) should be used as input. This panel appears automatically after you import a data file using OVITO’s Load File or Load Remote File functions.

To return to this panel at any time, select the topmost entry under the Data Source section in the pipeline editor.

Supported file formats

The External File data source supports various file formats containing different data object types. The program automatically detects the file format and loads the data accordingly.

Toolbar functions

../../../_images/file_source_toolbar.svg
Pick new file

Selects a different file as input for the pipeline while preserving existing modifiers.

When you pick a new file using this function, OVITO will not automatically detect whether it belongs to a numbered file sequence. If necessary, manually re-enable the auto-generate option to load a trajectory made of a series of files.

Pick new remote file

Same as above but allows selecting a file from a remote server instead of the local filesystem.

Reload file

Updates the data for the current animation frame by reloading the external file. This is useful if the file has been modified externally, such as after re-running a simulation.

Update trajectory frames

Refreshes the trajectory sequence by scanning the directory for new files matching the filename pattern or by detecting newly appended frames in a trajectory file.

Load entire trajectory into memory

Loads all trajectory frames into memory to enable smoother animation playback. Ensure your system has sufficient free memory before enabling this option. By default, OVITO loads only a single frame at a time to minimize memory usage.

Data source – Numeric precision

Selects the floating-point precision in which particle coordinates and other continuous particle properties loaded from the file, e.g. velocities, forces, masses, and charges, are stored in memory:

Double (64-bit)

The default. Values are stored with the full precision of 15 to 16 significant digits.

Single (32-bit, memory saver)

Values are stored with a precision of about 7 significant digits, which cuts the memory required for these particle properties in half. Consider this option when working with very large particle systems (tens or hundreds of millions of particles), or when the simulation code wrote the file in single precision anyway.

This setting affects only how data is stored. Analysis modifiers still perform their computations in double precision. New particle properties computed by modifiers in the pipeline, e.g., the displacement vectors, are stored in the precision selected here as well. The default for newly imported files can be changed in the application settings.

File sequence – Search pattern

This section of the UI allows you to specify a filename pattern to load multiple files as a continuous trajectory. The pattern must contain a single * wildcard, which matches any sequence of digits in filenames. All matching files are combined into a single trajectory, displaying simulation frames sequentially.

When importing a file with a numeric name, OVITO automatically generates a default search pattern. To disable this behavior, uncheck auto-generate.

See this section for details on importing simulation trajectories.

Trajectory – Playback ratio

When importing a trajectory with N frames, OVITO synchronizes the animation timeline with the number of imported frames, creating a 1:1 mapping between trajectory and animation frames.

To adjust this playback frame ratio, click Change to open the Configure Trajectory Playback dialog.

Configure trajectory playback

../../../_images/configure_trajectory_playback.png

This dialog lets you modify how simulation trajectory snapshots map to OVITO’s animation timeline. You can change the default 1:1 mapping to:

  • 1:N mapping – Each trajectory frame is duplicated N times to stretch the animation.

  • N:1 mapping – Only every N-th trajectory frame is rendered, reducing the total number of frames.

  • Extract a static frame – Show only one particular snapshot from the trajectory.

A 1:N mapping is useful for extending coarse trajectories and rendering longer animations. The Smooth trajectory modifier can interpolate missing frames to create smooth particle motion.

An N:1 mapping is useful when working with extremely long trajectories, reducing the number of rendered frames for a shorter video.

The Extract a static frame option allows you to isolate a single frame from the trajectory, which is useful for rendering camera animations with a static model (see tutorial Turntable animation of a model).

For more details, see Animating the camera and other parameters.

See also