v0.16.2
🚀 Added
Segment Anything 2 in workflows 🥳
We prepared great amount of changes to workflows, could not really decide which update to start with, but at the end we found onboarding of SAM 2 model as most exciting.
Thanks to @hansent effort we have introduced SAM 2 workflow block.
You can use SAM2 standalone, or you can ground it's predictions with other detection models which is the true power of workflows. Thanks to grounding, you can generate instance segmentation masks for each bounding box predicted by your object detection model
❗ We do not support SAM2 at Roboflow Hosted Platform yet, but it is possible to use inference server start command to run local server supporting SAM2 model and connect it to workflows UI to run examples.
workflows 🤝 SAHI
We've added set of blocks that let people apply SAHI technique based on utilities provided by supervision.
We are going to work to simplify SAHI usage in workflows UI, but now you need to use three blocks to effectively apply technique:
Classical Computer Vision methods in workflows 🔥
We do not forget about old good friends - that's why we also added bunch of blocks with classical Computer Vision algorithms:
- Dominant Color block by @NickHerrig in #578
- SIFT, SIFT matching, classical pattern matching and others by @ryanjball in #581
🌱 Changed
- Added encoding='utf-8' to setup.py by @Bhavay-2001 in #556
- Move landing static assets to
/static/namespace by @iurisilvio in #577 - add exclusion rules for dedicated deployment authorizer by @PacificDou in #576
- Workflow private block properties by @EmilyGavrilenko in #579
🔨 Fixed
- Fix security issues with landing page by @PawelPeczek-Roboflow in #584
- Fixed a Regression in the Custom Metadata Block that was introduced in
v0.16.0- PR with fix by @chandlersupple (#573) - we kindly ask clients relying on the Custom Metadata Block, running their workflows on-prem to updateinferenceorinferenceserver - Bug in
workflowsExecution Engine that was making it impossible to feed the same block with two identical selectors (fixed in #581)
❗ In release 0.16.0 we introduced bug impacting workflows and inference_sdk
The mistake was introduced in #565 and fixed in #585 (both by @PawelPeczek-Roboflow 😢 ) and was causing issues with order of results - regarding specific workflows blocks:
- blocks with Roboflow models, whenever used with batch input (for instance when workflow was run against multiple images, or Dynamic Crop was used) were mismatching order of predictions with respect to order of images
- the same was true for OpenAI block and GPT-4V block
- the problem was also introduced into
inference_sdk, so whenever client was called with multiple images - results may have been missmatched
We advice all our clients to upgrade to new release and abandon usage inference=0.16.0
🏅 New Contributors
- @Bhavay-2001 made their first contribution in #556
Full Changelog: v0.16.0...v0.16.1
