Thread: Grip running out of memory
View Single Post
  #7   Spotlight this post!  
Unread 25-01-2016, 14:12
ThomasClark's Avatar
ThomasClark ThomasClark is offline
Registered User
FRC #0237
  
Join Date: Dec 2012
Location: Watertown, CT
Posts: 146
ThomasClark has much to be proud ofThomasClark has much to be proud ofThomasClark has much to be proud ofThomasClark has much to be proud ofThomasClark has much to be proud ofThomasClark has much to be proud ofThomasClark has much to be proud ofThomasClark has much to be proud ofThomasClark has much to be proud ofThomasClark has much to be proud of
Re: Grip running out of memory
Quote:
Originally Posted by SLAB-Mr.Thomas View Post
I wonder if the WPI GRIP team is monitoring these posts. I've mentioned 2 errors I haven't seen posted elsewhere. Those random occasional out of memory are a real pain and could be a deal breaker for us using GRIP and I really want to use it. Incorrect labeling of report variables needs attention, too.

Other errors I've gotten have been mentioned elsewhere, I think.
I really recommend running GRIP on a coprocessor if you're running out of memory a lot. The roboRIO only has 256 MB of RAM, and most of it's taken up the LabVIEW runtime and your robot program. The Kangaroo PC is a really good option, although people have also gotten GRIP to run on a Raspberry Pi.

Can you describe the incorrect labeling problem? I do monitor Chief Delphi for GRIP-related stuff, but you'll get a faster response if you open an issue.
__________________
GRIP (Graphically Represented Image Processing) - rapidly develop computer vision algorithms for FRC