Define output shape in signature file about multi-model-server HOT 3 CLOSED

I'm not sure what you mean by this. Is option optional then? Or you ignore it if the output of the model doesn't actually match the signature and return it anyway?
Can you provide some examples?

from multi-model-server.

For example:
In SSD example, output shape in signature file is [1, 6132, 6].
This is actually the shape of NDArray that we get after forward pass (inference).

However, final output from the SSD server is a list of tuples - [(class, x1,y1,x2,y2)..] depending on how many objects were detected.

A new user can be confused thinking input and output in signature talks about input and output to the service rather than knowing it is the signature of MXNet model.

So we need to clarify somehow in the documentation

from multi-model-server.

The signature.json file contains a mix of two: (1) Model input and output shapes (in inputs and outputs) (2) Service input and output data types (MIME types) (in input_type and output_type)

This can indeed be confusing for users and we need to clearly document it.

@aaronmarkham can you please address this confusion?

from multi-model-server.