create_robot
spinnaker_sdk_camera_driver
| create_robot | spinnaker_sdk_camera_driver | |
|---|---|---|
| 2 | 1 | |
| 199 | 126 | |
| 2.0% | -0.8% | |
| 5.3 | 0.0 | |
| 12 months ago | about 2 months ago | |
| C++ | C++ | |
| BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
create_robot
-
Can I use Irobot 675 with ROS ?
ROS = Robotics Operating System , Irobot has a version called "irobot Create" that works with ROS seamlessly. I know there exists projects like https://github.com/AutonomyLab/create_robot I want to verify that the irobot 675 works as intended.
-
Is ROS used in industry on actual project?
You can totally use it for Roombas. The Create 3 (newest one) supports ROS 2: https://edu.irobot.com/what-we-offer/create3. The older ones can be used with ROS 1: https://github.com/AutonomyLab/create_robot.
spinnaker_sdk_camera_driver
-
Torvalds: Shared libraries are not a good thing in general
To be honest, I haven't really tracked it— the product I work on dropped stereo vision in favour of RGBD, so I don't really know where it's landed. I suppose it's not a great sign that the current generation SDK still requires a login to access:
https://www.flir.ca/products/spinnaker-sdk/
And at least one spinnaker-based driver seems to have inherited the "download the SDK from elsewhere" approach, though who knows if that's due to genuine need or just cargo-culting forward what was implemented years ago in the flycapture driver:
https://github.com/neufieldrobotics/spinnaker_sdk_camera_dri...
The "proper" approach here would of course be for Open Robotics (the ROS maintainers) to pull the debs and host them on the official ROS repos, as they do for a number of other dependencies [1], but that clearly hasn't happened [2].
I think a lot of hardware vendors who cut their teeth in the totally locked down world of industrial controls/perception still think they're protecting some fantastic trade secret or whatever by behaving like this.
[1]: https://github.com/ros-infrastructure/reprepro-updater/tree/...
[2]: http://packages.ros.org/ros/ubuntu/pool/main/s/
What are some alternatives?
flatland - A 2D robot simulator for ROS
distroless - 🥑 Language focused docker images, minus the operating system.
pointgrey_camera_driver - ROS driver for Pt. Grey cameras, based on the official FlyCapture2 SDK.
indi-3rdparty - INDI 3rd Party drivers repository
reprepro-updater
mb-sound-jackffi - An unstable Ruby FFI interface for the JACK Audio Connection Kit
bevy - A refreshingly simple data-driven game engine built in Rust
spinnaker_sdk_camera_dri