Thursday, 9 July 2026
For a machine builder, integrating machine vision without depending on a black box is a real question of control. This week, an OEM partner spent five days at our premises getting to grips with our Python SDK. On the program: • Discovering the Psycle SDK — default features and custom developments — through […]
For a machine builder, integrating machine vision without depending on a black box is a real question of control.
This week, an OEM partner spent five days at our premises getting to grips with our Python SDK.
On the program:
• Discovering the Psycle SDK — default features and custom developments — through a series of vision skill-building exercises.
• Data architecture on our Psycle Assistant Qualité quality platform, and machine fleet management.
• Code architecture: laying down the standard building blocks, distinguishing recurring utilities from one-off needs.
• Hands-on practice with real customer cases.
The goal is clear: to help OEMs become more autonomous in vision. No black box, but fully open code that belongs to them.
A session led by Natan Danous, Julien P. and Baptiste A.
For many machine builders and large groups with vision teams, this skills development is often the starting point for a broader collaboration. We now run nearly one training session a month, on complementary topics: optics and image capture, introduction to AI for vision, application development in Python with the SDK, and annotation best practices for supervised AI.
Have a team to train in machine vision? Write to us: formation@psycle.io
