Use Environment Variables
Tick to use the system Environment Variables on the host system for lookup paths.
Tick to select saved variables for the Python Home, Python Path, and Python DLL Path, or enter the text manually (applies when Use Environment Variables is unticked).
Select whether the script will be executed on the CPU Only or GPU Accelerated (GPU option available when this capability is detected).
The location of the standard Python libraries (applies when Use Environment Variables is not ticked).
The location of the Python site packages folder (applies to CPU Only Accelerator only when Use Environment Variables is not ticked).
Path to python**.dll (e.g. python38.dll) for Windows hosts or libpython**.so (e.g. libpython3.8.so) for Ubuntu hosts (applies to CPU Only Accelerator only when Use Environment Variables is not ticked).
The Python script file to be executed.
Input variables from the Python file are auto-populated when it is loaded. Each input variable is mapped to a column or attribute from the input payload.
One or more Python variable names from the Python script file. These are appended to the output payload.
When Accelerator is set to GPU Accelerated, the script should print the output in the following format:
The output values can either be appended to the incoming payload (Append to Existing), or a new payload is created that consists only of the output values (New).
Optional global variables defined in the Python file that are available when next the Data Stream is published (applies to CPU Only Accelerator only).
The value is saved to a Pickle file whenever the Data Stream is unpublished, which allows you to maintain the program state across sessions, e.g. to recall the previous high temperature without waiting on sensor input or a recalculation.