F(x) List

../../../../../_images/fx.svg

The F(x) nodes all have a similar role as the Calculator Tables node. But where the Calculator Tables node shines when the calculations are simple, the f(x) nodes are better suited for more advanced calculations since the code is kept in a separate python file. You can place this python file anywhere, but it might be a good idea to keep it in the same folder as your workflow or in a subfolder to that folder.

The script file

When writing a “function” (it is actually a python class) you need to inherit from FxWrapper. The FxWrapper provides access to the input and output with self.arg and self.res respectively. These variables are of the same type as the input on port2 consult the API for that type to figure out relevant operations.

The field arg_types is a list containing string representations of types (as shown in port tooltips) that you intend your script to support and determines the types for which the function is available.

For example:

from sympathy.api import fx_wrapper

class MyCalculation(fx_wrapper.FxWrapper):
    arg_types = ['table']

    def execute(self):
        spam = self.arg.get_column_to_array('spam')

        # My super advanced calculation that totally couldn't be
        # done in the :ref:`Calculator Tables` node:
        more_spam = spam + 1

        self.res.set_column_from_array('more spam', more_spam)

The same script file can be used with both F(x) and F(x) List nodes.

Debugging your script

F(x) scripts can be debugged in spyder by following these simple steps:

  1. Open the script file in spyder and place a breakpoint somewhere in the execute method that you want to debug.
  2. Go back to Sympathy and right-click and choose Debug on the f(x) node with that function selected.
  3. Make sure that the file node_fx_selector.py is the active file in spyder and press Debug file (Ctrl+F5).
  4. A third python file will open as the debugging starts. Press Continue (Ctrl+F12) to arrive at the breakpoint in your f(x) script. From here you can step through your code however you want to.

Configuration

When Copy input is disabled (the default) the output table will be empty when the functions are run.

When the Copy input setting is enabled the entire input table will get copied to the output before running the functions in the file. This is useful when your functions should only add a few columns to a data table, but in this case you must make sure that the output has the same number of rows as the input.

By default (pass-through disabled) only the functions that you have manually selected in the configuration will be run when you execute the node, but with the pass-through setting enabled the node will run all the functions in the selected file. This can be convenient in some situations when new functions are added often.

class node_fx_selector.FxList[source]

Apply functions to a list of items.

Functions based on FxWrapper will be invoked once for each item in the list with each item as argument. The functions available are the ones where arg_types of the function matches the type of the individual items from the list port (port2).

Ref. nodes:

F(x)

Inputs:
port1
: datasource

Path to Python file with scripted functions.

port2
: [<a>]

List with data to apply functions on

Outputs:
port3
: [<a>]

List with function(s) applied

Configuration:
Copy input

If enabled the incoming data will be copied to the output before running the nodes.

Select functions

Choose one or many of the listed functions to apply to the content of the incoming item.