Florence2 workflows block #661
Conversation
| """ | ||
|
|
||
| TaskType = Literal[ | ||
| "<OCR>", |
There was a problem hiding this comment.
This is change in favour of clients using UI, probably would decrease code readability, but I would still choose that tradeoff - let's change the literal entries into this style:
ocr-with-region instead <OCR_WITH_REGION> and change it in prompting into f"<{value.upper().replace('-', '_')}>"
There was a problem hiding this comment.
Sorry, this was still draft -- I added legible english descriptions and mapped them to tasks... that ok?
| ) | ||
| type: Literal["roboflow_core/florence_2@v1"] | ||
| images: Union[WorkflowImageSelector, StepOutputImageSelector] = ImageInputField | ||
| task_type: TaskType = Field( |
There was a problem hiding this comment.
let's change into this style: #659 following what @EmilyGavrilenko did
| prompt=prompt, | ||
| ) | ||
| elif self._step_execution_mode is StepExecutionMode.REMOTE: | ||
| raise NotImplementedError( |
There was a problem hiding this comment.
just exploratory question - am I correct that for base model we could run it in core models lambda given special endpoint is created?
There was a problem hiding this comment.
Yes, I believe so. We'd need to enable it with envvar also. It might be pretty dang slow depending on the task.
There was a problem hiding this comment.
yeah, true that
|
and if possible, could u add support on parsing block - VLM as detector |
|
sorry, missclick |
probicheaux
requested review from
grzegorz-roboflow,
yeldarby and
hansent
as code owners
…ence into florence2-workflows-block
Description
Adds florence 2 model block and adds florence 2 parsing to VLM_as_detector block
Type of change
Please delete options that are not relevant.
How has this change been tested, please provide a testcase or example of how you tested the change?
Deployed locally and tested with prod workflows UI
Any specific deployment considerations
No
Docs