9 Glossary

A structure where information about all documents under the root is saved, and used for cross-referencing. The environment is pickled after the parsing stage, so that successive runs only need to read and parse new and changed documents.
source directory
The directory which, including its subdirectories, contains all source files for one Sphinx project.
Application Path
The installation folder for a 3D or compositing application. This path typically contains the absolute path to the rendering application’s rendering program.
Application Profile
Contains a list of nodes and the application paths for rendering applications.
Command Line Interface. For SquidNet, this is the “sqn” command line interface.
A workstation computer used to submit job requests to the render farm. Clients can be configured to optionally render jobs.
Background service on Linux or mac OS platforms. Each SquidNet server runs as a daemon on these operating systems. On WINDOWS platforms, daemons are called services.
A numbered image within an animation clip. The output of a rendered frame is an image file.
Frame Check
A feature that automatically creates single frame jobs for images that are missing or incorrectly rendered.
GUI Graphical User Interface
The main SquidNet interface used on clients and the master node. Slave nodes don’t need access to the GUI.
A processing request within a render farm. Typically, it’s a request to render a single frame or image sequence.
The render farm computer that manages all render farm operations. Can be configured to optionally render jobs (although, depending on workflow, this is not recommended)
Multiple Document Interface. SquidNet’s main GUI is based on an MDI application format.
Network Attached Storage. NAS drives are recommended for storage of all rendering content and image output.
A computer configured to run within a render farm configuration. Can be a client, master or slave computer. Synonymous with an individual computer system. A node can be a Windows, Mac or Linux computer system.
Pickup Frame
Jobs created by SquidNet (as apposed to user requests) and added to the render farm queue. Typically, these types of jobs are created when the Frame-Check feature is enabled.
Groupings of render nodes that are associated by a common name and perform specific processing operations.
Render Farm
A multi-computer network that’s dedicated to the processing (rendering) of computer-generated imagery (CGI) for the film, television, gaming, architectural and multi-media industries.
Render node
A computer that processes user requests. Typically, this is a slave node but client and master nodes can be configured to process jobs as well.
Rendering Application
A 3rd party program used to process (render) scene content. Example rendering applications include Maya, 3DSMAX, mod, LightWave and Terragen.
SAN Storage Area Network
Typically used in high-performance environments.
Skip Frame
A feature that prevents the re-processing of frames for images that have already been rendered.
A computer selected to only perform rendering operations.
The portion of a job that gets distributed to render nodes. Slices contain processing instructions for render nodes.
SquidNet command line interface program. Avalailable on all supported platforms.
SquidNet Service Account. The administration account that the SquidNet service runs under (Windows only).
An open window within the client area of the main user interface.
Wake-on-Lan network protocol that sends messages to computers to bring them out of a sleeping or hibernating state.