blackjack-basic-strategy VS orchest

It’s an easy to use inference server for computer vision models.

The end result is a Docker container that serves a standardized API as a microservice that your application uses to get predictions from computer vision models (though there is also a native Python interface).

It’s backed by a bunch of component pieces:

* a server (so you don’t have to reimplement things like image processing & prediction visualization on every project)

* standardized APIs for computer vision tasks (so switching out the model weights and architecture can be done independently of your application code)

* model architecture implementations (which implement the tensor parsing glue between images & predictions) for supervised models that you've fine-tuned to perform custom tasks

* foundation model implementations (like CLIP & SAM) that tend to chain well with fine-tuned models

* reusable utils to make adding support for new models easier

* a model registry (so your code can be independent from your model weights & you don't have to re-build and re-deploy every time you want to iterate on your model weights)

* data management integrations (so you can collect more images of edge cases to improve your dataset & model the more it sees in the wild)

* ecosystem (there are tens of thousands of fine-tuned models shared by users that you can use off the shelf via Roboflow Universe[1])

Additionally, since it's focused specifically on computer vision, it has specific CV-focused features (like direct camera stream input) and makes some different tradeoffs than other more general ML solutions (namely, optimized for small-fast models that run at the edge & need support for running on many different devices like NVIDIA Jetsons and Raspberry Pis in addition to beefy cloud servers).

[1] https://universe.roboflow.com

* Most of the time I find Roboflow extremely handy, I used it to merge datasets, augmentate, read tutorials and that kind of thing. Basically you just create your dataset with roboflow and focus on other aspects.

For computer vision, there are 100k+ open source classification, object detection, and segmentation datasets available on Roboflow Universe: https://universe.roboflow.com

Solid website and app overall for learning more about computer vision, discovering datasets, and keeping up with advancements in the field: * https://roboflow.com/learn * https://universe.roboflow.com (datasets) | https://blog.roboflow.com/computer-vision-datasets-and-apis/ * https://blog.roboflow.com

If you're lacking training images, you can also use [Roboflow Universe](https://universe.roboflow.com) to obtain them (over 100 million labeled images available)

Roboflow | Multiple Roles | Full-time (Remote) | https://roboflow.com/careers

Roboflow is the fastest way to use computer vision in production. We help developers give their software the sense of sight. Our end-to-end platform[1] provides tooling for image collection, annotation, dataset exploration and curation, training, and deployment.

Over 100k engineers (including engineers from 2/3 Fortune 100 companies) build with Roboflow. And we now host the largest collection[2] of open source computer vision datasets and pre-trained models[3].

We have several openings available, but are primarily looking for strong technical generalists who want to help us democratize computer vision and like to wear many hats and have an outsized impact. (We especially love hiring past and future founders.)

We're hiring 3 full-stack engineers this quarter and we're also looking for an infrastructure engineer with Elasticsearch experience.

[1]: https://docs.roboflow.com

[2]: https://blog.roboflow.com/computer-vision-datasets-and-apis/

[3]: https://universe.roboflow.com

Based on what I do/use when I prepare models: A good framework for creating and improving this dataset faster is to use Roboflow Universe and search “flowers” and “bouquets of flowers” in the search bar (it’s like Google Images for CV Datasets). You can search images by subject, or metadata, and clone them directly into a free public workspace (they house up to 10k images without charge). * https://universe.roboflow.com/ * https://universe.roboflow.com/search?q=flowers * https://universe.roboflow.com/search?q=bouqets

Lots of ideas will come to mind if you look and search through open source datasets: https://universe.roboflow.com/

Open source datasets: https://universe.roboflow.com/ Model training: https://docs.roboflow.com/train Model deployment: https://docs.roboflow.com/inference/hosted-api

You can check out our OSS https://github.com/orchest/orchest

The code example is part of our ELT/data pipeline tool called Orchest: https://github.com/orchest/orchest/

First want to say congrats to the Patterns team for creating a gorgeous looking tool. Very minimal and approachable. Massive kudos!

Disclaimer: we're building something very similar and I'm curious about a couple of things.

One of the questions our users have asked us often is how to minimize the dependence on "product specific" components/nodes/steps. For example, if you write CI for GitHub Actions you may use a bunch of GitHub Action references.

Looking at the `graph.yml` in some of the examples you shared you use a similar approach (e.g. patterns/openai-completion@v4). That means that whenever you depend on such components your automation/data pipeline becomes more tied to the specific tool (GitHub Actions/Patterns), effectively locking in users.

How are you helping users feel comfortable with that problem (I don't want to invest in something that's not portable)? It's something we've struggled with ourselves as we're expanding the "out of the box" capabilities you get.

Furthermore, would have loved to see this as an open source project. But I guess the second best thing to open source is some open source contributions and `dcp` and `common-model` look quite interesting!

For those who are curious, I'm one of the authors of https://github.com/orchest/orchest

Haven't tried it. In its favor, Argo is vendor neutral and is really easy to set up in a local k8s environment like docker for desktop or minikube. If you already use k8s for configuration, service discovery, secret management, etc, it's dead simple to set up and use (avoiding configuration having to learn a whole new workflow configuration language in addition to k8s). The big downside is that it doesn't have a visual DAG editor (although that might be a positive for engineers having to fix workflows written by non-programmers), but the relatively bare-metal nature of Argo means that it's fairly easy to use it as an underlying engine for a more opinionated or lower-code framework (orchest is a notable one out now).

If you’d like to try something for you data workflows that’s vendor agnostic (k8s based) and open source you can check out our project: https://github.com/orchest/orchest

You can find it here: https://github.com/orchest/orchest Convenience install script: https://github.com/orchest/orchest#installation

We automatically provide container level parallelism in Orchest: https://github.com/orchest/orchest

For people in this thread interested in what this tool is an alternative to: Airflow, Luigi, Kubeflow, Kedro, Flyte, Metaflow, Sagemaker Pipelines, GCP Vertex Workbench, Azure Data Factory, Azure ML, Dagster, DVC, ClearML, Prefect, Pachyderm, and Orchest.

Disclaimer: author of Orchest https://github.com/orchest/orchest