You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With TorchServe integration in place (see #19 and #122), it would be nice to have a CLIP and DINO implementation that could be used via TorchServe. This requires some integration effort on the model side
Solution
Basically, we need implementations of CLIP and DINO features that can be registered via TorchServe and respective adapters on the vitrivr side. The adjusted models could be maintained in a dedicated repository. The following steps are involved:
Prepare CLIP model for serving via TorchServe.
Prepare DINO model for serving via TorchServe.
Add TorchServe implementations to the existing torch serve module. The implementations can inherit from the existing, abstract classes.
Description
With TorchServe integration in place (see #19 and #122), it would be nice to have a CLIP and DINO implementation that could be used via TorchServe. This requires some integration effort on the model side
Solution
Basically, we need implementations of CLIP and DINO features that can be registered via TorchServe and respective adapters on the vitrivr side. The adjusted models could be maintained in a dedicated repository. The following steps are involved:
TorchServe
implementations to the existing torch serve module. The implementations can inherit from the existing, abstract classes.Dependencies
Wait for #122 to be merged.
Context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: