Catalyst 2 scripts need to account for data operations internal to readers
When creating Catalyst scripts from readers that perform certain data operations such as selecting only some blocks to read and applying a displacement field to points, we are missing those data operations in the recorded script. When it is used in a Catalyst run, the data comes in untransformed, leading to incorrect data. We need to capture the data transformations inside the reader in the Catalyst pipeline somehow.