Gaffer’s Box node is a staple building block sharing chunks of node graph (via the Reference system), or quickly building tools via expressions and promoted plugs.
The Gaffer docs have a page covering Box nodes and how to use them. In this post we take a quick look at how to re-create a simple GroundPlane tool made in the UI, using only Gaffer’s python API.
Continue reading “Scripting Box nodes”Like many other applications that calculate data on-demand, Gaffer has a memory cache that can increase performance in UI sessions if you have RAM to spare.
The default size (1GB) is somewhat conservative as to ensure we don’t use up all the resources of more modest machines when Gaffer is used out-the-box. It is easy to increase the limit though, which can bring performance gains in real-world production scenarios.
Continue reading “Gaffer for pipeline – part 3 – Compute cache size”Continuing our bottom-up look at Gaffer from a pipeline perspective, in this instalment we look at the fundamentals of how to Gaffer is configured. We will cover:
It can be hard to know where to start when you first start integrating a new application into a pipeline. This post is the first part in a series that takes a bottom-up approach and brings together a few helpful links for getting started with Gaffer configuration, scripting and development.
In this part, we take a look at how the gaffer application is structured, and what happens at startup.
Continue reading “Gaffer for pipeline – part 1 – App structure and startup”
