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
Describe the feature and the current behavior/state
TensorBoard images should be logged in the [0, 1] range when float.
Currently, we do not provide any type of automatic handling of this scaling, so if you are training on [-1, 1] and using our callbacks, images will be logged without scaling.
Will this change the current API? How?
Small change to ashpy.utils.log() and all the callbacks using it, they will now accept a new boolean argument auto_tb_scaling controlling this behavior.
Who will benefit with this feature?
Anyone using the default logging facilities.
Any Other info
The text was updated successfully, but these errors were encountered:
If the input is float tensorboard wants the range [0,1] so we need to scale the image if the range is [-1, 1] or if the range is [0, 255] (Are there people using the range [0, 255] and float dtype?).
In this case we can accept an enum describing the input range.
If the image dtype is tf.uin8, then we expect values on [0-255] (follow the tensorflow convention)
If the image dytpe is tf.float* then the image should be in the range [0.1] (tensorflow convention). We can support only the most common scenario that's an image with values squashed in [-1,1]. Thus a boolean for this case is enough IMHO
System information
Describe the feature and the current behavior/state
TensorBoard images should be logged in the [0, 1] range when float.
Currently, we do not provide any type of automatic handling of this scaling, so if you are training on [-1, 1] and using our callbacks, images will be logged without scaling.
Will this change the current API? How?
Small change to
ashpy.utils.log()
and all the callbacks using it, they will now accept a new boolean argumentauto_tb_scaling
controlling this behavior.Who will benefit with this feature?
Anyone using the default logging facilities.
Any Other info
The text was updated successfully, but these errors were encountered: