Currently, the vtkRCalculatorFilter expects that its output will be of the same type as its input. For example, if its input is a table, then its output will also be a table. I imagine that this inflexibility will pose a problem once our collaborators start using our "custom analysis" framework.