Generating Code from GRIP

GRIP Code Generation

When running your vision algorithm on a small processor such as a roboRIO or Raspberry PI it is encouraged to run OpenCV directly on the processor without the overhead of GRIP. To facilitate this, GRIP can generate code in C++, Java, and Python for the pipeline that you have created. This generated code can be added to your robot project and called directly from your existing robot code.

Input sources such as cameras or image directories and output steps such as NetworkTables are not generated. Your code must supply images as OpenCV mats. On the roboRIO, the CameraServer class supplies images in that format. For getting results you can just use generated getter methods for retrieving the resultant values such as contour x and y values.

Generating Code

To generate code, go to Tools > Generate Code. This will bring up a save dialog that lets you create a C++, Java, or Python class that performs the steps in the GRIP pipeline.

If generating code to be used in a pre-existing project, choose a relevant directory to save the pipeline to. 

C++ Users: the pipeline class is split into a header and implementation file

Java Users: the generated class lacks a package declaration, so a declaration should be added to match the directory where the file was saved.

Python Users: the module name will be identical to the class, so the import statement will be something like from Pipeline import Pipeline

Structure of the Generated Code

  // Process -- this will run the pipeline
  process(Mat source)
  // Output accessors

Running the Pipeline

To run the Pipeline, call the process method with the sources (webcams, IP camera, image file, etc) as arguments. This will expose the outputs of every operation in the pipeline with the getFooOutput methods.

Getting the Results

Users are able to the outputs of every step in the pipeline. The outputs of these operations would be accessible through their respective accessors.  For example:

Java/C++ getter
Python variable
RGB Threshold getRgbThresholdOutput
Blur getBlurOutput
CV Erode getCvErodeOutput
Find Contours getFindContoursOutput
Filter Contours getFilterContoursOutput

If an operation appears multiple times in the pipeline, the accessors for those operations have the number of that operation: 

Operation Which appearance Accessor
Blur First getBlur0Output
Blur Second getBlur1Output
Blur Third getBlur2Output

0 Report Errors

Use this form to report any errors with the documentation. For help with WPILib, please use the FIRST Forums at For reporting WPILib bugs, please submit an issue on GitHub at