Comments (9)
Hi @chriscarollo -
Thanks for reporting the issue. I have tested the code snippet and reproduces the reported behaviour. Attached gist file for reference.
We will look into the issue and update you the same.
from keras.
Trivially reproduced:
input = keras.layers.Input( (1,), name='input_1' )
output = keras.layers.Dense( 8, name='output_1' )( input )
m = keras.Model( inputs=[input], outputs=[output], name='model_1' )
m.compile()
m.summary()
Model: "model_1"
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┓
┃ Layer (type) ┃ Output Shape ┃ Param # ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━┩
│ input_1 (InputLayer) │ (None, 1) │ 0 │
├──────────────────────────────────────┼─────────────────────────────┼─────────────────┤
│ output_1 (Dense) │ (None, 8) │ 16 │
└──────────────────────────────────────┴─────────────────────────────┴─────────────────┘
Total params: 16 (64.00 B)
Trainable params: 16 (64.00 B)
Non-trainable params: 0 (0.00 B)
>>> m.export( 'test' )
INFO:tensorflow:Assets written to: test/assets
INFO:tensorflow:Assets written to: test/assets
Saved artifact at 'test'. The following endpoints are available:
* Endpoint 'serve'
args_0 (POSITIONAL_ONLY): TensorSpec(shape=(None, 1), dtype=tf.float32, name='input_1')
Output Type:
TensorSpec(shape=(None, 8), dtype=tf.float32, name=None)
Captures:
140410840896736: TensorSpec(shape=(), dtype=tf.resource, name=None)
140410840896912: TensorSpec(shape=(), dtype=tf.resource, name=None)
from keras.
FWIW I'm running Tensorflow 2.16.1 with Keras 3.3.3, but it does seem like this repros with Tensorflow 2.15 as well.
from keras.
Would you mind taking a look @hertschuh? CC: @nkovela1
from keras.
Hi @chriscarollo ,
Thanks for the report. I'm not really clear about what Triton needs from the saved model, but the outputs appear to have a name (more on that below).
but when I model.export() it says:
Output Type:
TensorSpec(shape=(None, 1), dtype=tf.float32, name=None)
Apparently, the only thing that is relevant in this message is the "output type". Unfortunately (and I don't know why) the name is missing.
If I also save as a .keras file, it correctly saves that layer with my "output_1" name.
Correct. Layers and outputs are very different concepts though. Do you need the layer? Or do you care about the output?
It appears that the output is named. It's just numbered starting from zero to support multiple outputs. So in your case, the output is named output_0
(independent of the layer name).
Here's how you can find out by adding this to your code above:
# Reload the model
loaded = tf.saved_model.load('test')
print("Outputs", loaded.signatures['serve'].structured_outputs.items())
Which prints
Outputs dict_items([('output_0', TensorSpec(shape=(None, 8), dtype=tf.float32, name='output_0'))])
But overall, I'm surprised Triton needs more than the name of the function, which is serve
by default.
from keras.
Related Issues (20)
- Custom Generator crash for variable input dimensions HOT 4
- Add `on_epoch_begin` to `utils.Sequence` HOT 1
- Conv3D generates output on Tensorflow backend while crashes on pytorch backend HOT 2
- RNN layer: len is not well defined for a symbolic Tensor. Please call `x.shape` rather than `len(x)` for shape information. HOT 4
- keras.ops.select doesn't accept tuples as input HOT 1
- Recommendation for writing tests for ModelParallel distribution HOT 2
- optimizers.Adam no longer accepts tf.Variable HOT 1
- Please explain label_mode='int' in keras.utils.image_dataset_from_directory HOT 2
- Getting Nan values in prediction HOT 1
- compatibility with pytorch 2.3 HOT 1
- Specifying shape of normal sampling with partially empty keras tensor HOT 3
- Question: Best practice for direct variable initialization HOT 6
- Inconsistent assertion in keras.layers.MultiHeadAttention
- [BUG] keras.layers.StringLookup and Vocabulary of Tensors HOT 3
- ops.linspace broken in Tensorflow when num is a tf.Tensor HOT 4
- Loading model fails: can only concatenate tuple
- model.predict time stdout HOT 4
- Keras `__init__.py` structure isn't readable by a static type checker HOT 5
- [BUG] Conflicting loss_weights implementation in Keras3 for single output case. HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from keras.