Open JRegimbal opened 1 year ago
@rianadutta Moving to next sprint, but if not realistic to complete, let's move to backlog?
Moving to backlog as this does not currently impact user experience. It should be fixed for non-photo collages just because this would set expectations appropriately for this preprocessor, but I'm not sure what it currently does with non-photo collages. Will need some testing before deciding.
@AndyBaiMQC The debate here is from several issues, which make it unclear what we should do overall. Two options, maybe there are others:
Open to other possibilities. @AndyBaiMQC let me know if need to discuss, but this tangle seems like a great way to get up-to-speed on the preprocessor pipeline.
2 aspects of investigation: model + category definitions. For both collage detector and content categorizer, here are some updates from local tests:
Content detector:
Collage detector:
The preprocessor assumes that a request will always have a raster graphic embedded in the
graphic
key of the request. This is not true. It also is positioned to run in priority group 1, which may be too early unless this is truly a preprocessor intended for all collages of graphics (e.g., collages of charts, diagrams).