Viam Collaboration

[danic85]

Viam has very kindly offered to collaborate with me on the migration of the existing python modules into Viam to determine benefits and challenges. I will be creating a few guides and videos to explain the process.

Following a recent call with the team at Viam, I have a few actions that I'd like to document here, with a view to creating separate topics for each that can be shared and discussed with the Viam team.

This is just my to-do list.

• Possibility to collaborate on early feedback for camera functionality and object tracking.
• Provide more information on experience with the registry, pain points.
• Challenges around using the logging tool.
• More information on how pub sub is used in current project, to discuss best approach when migrating to Viam.
• Possibility of switch the Arduino for an ESP32. Feedback on Viam MicroRDK, possibility of using in body.
• Discussion around best practices for restarting process when code changes are made. Better approach to module creation to block re-installation of dependencies after each restart? dotfile creation? Kill process so that viam restarts it (workaround).
• Best practice for shutting down script, what happens when the server stops? How can we ensure that hardware is reset to starting state?
• What are the best practices for iterative development on custom modules?
• How do we use os.getenv?
• Are there improvements to the log UI planned so we can focus on what we're interested in? Some configuration that allows for verbose logging on specific modules?
• Provide list of modules in framework, and which API I assume they would map to. Share for discussion.