Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template

System information

• TensorFlow version (you are using): 2.1
• Are you willing to contribute it (Yes/No): No

(e.g. for links and images), because some of these examples are now being rendered in the docs.

Added by @fchollet in requests for contributions.

It seems the current implementation will cut the tensor to min or max according to their values, which might be a problem when debugging logical errors or typos. Maybe it would be better to just throw an exception? Also it would be nice to note that in the documentation.

>>> import torch
>>> print(torch.__version__)
1.6.0
>>> a

Describe the issue linked to the documentation

Follows from #17387

Suggest a potential alternative/fix

Stop referencing preprocessing functions e.g. :

maxabs_scale
minmax_scale
normalize
quantile_transform
robust_scale
scale
power_transform

in the UG, and only add them e.g. in the "See Also" sections, or even just in the API ref.

In particular right now the first entr

Recent discussions on Discourse suggest that not all users know about apropos (or equivalently, using ?"..." for text search). The startup message currently mentions

Type "?" for help, "]?" for Pkg help.

I suggest that text search is added to this, but I am still looking for a compact way of phrasing it.

Currently, the C++ compiler generates lots of warnings: https://xgboost-ci.net/blue/organizations/jenkins/xgboost/detail/master/516/pipeline/61. It would be great to reduce the number of warnings.

Note to new contributors: Post a comment here if you'd like to work on this issue. Feel free to ping me for help.