Generated GRIP code not working as expected.
 

My team is experimenting with GRIP's generate code feature and we are having some problems with the data we are getting back. While running the pipeline on my computer gives the data we expect, the generated code is returning different numbers at the same time. Here is the pipeline that was generated and here is where we are calling it from.

Re: Generated GRIP code not working as expected.
 

How different are the numbers? They won't be exactly the same that you see in GRIP, but should be pretty close.

Also, this line will throw an exception and cause your robot to crash if no contours are found. You need to check the number of contours before trying to use them.

Re: Generated GRIP code not working as expected.
 

I ran out of time today to test to give you exact numbers. I will retest the generated code vs the computer pipeline tomorrow to make sure we didn't mess anything up.

Re: Generated GRIP code not working as expected.
 

Nevermind, I realized that we were calling the wrong function. We were calling findCountoursOutput() instead of filterContoursOutput() ... I'm not sure how both our software mentor and I missed that. It's working great now!