4 ms·
Just today I googled "torch normalize -1 1" and it said "zero documents matches your query". Insane stuff. (Censorship with crazy high false positives? Incompet
by hwers 5y ago
Just today I googled "torch normalize -1 1" and it said "zero documents matches your query". Insane stuff. (Censorship with crazy high false positives? Incompetence?) I went to duckduckgo and immediately found a useful answer.
- deleted 5y ago[deleted]
- anarazel 5y agoIsn't that just because -1 is treated as a negative match? Which you then also request as a match?
- modeless 5y agoUm, just in case you don't realize, "-1" selects pages that don't include "1". You just asked Google for pages that both include and don't include "1", and that's the empty set. I'm not aware of any way to search for negative numbers. This is really a UI problem. Google should probably use the context in this query to infer that you didn't literally want to exclude "1" from your results. However, half the comments here are complaining about Google not taking their queries extremely literally. This problem is a good demonstration of why inferring user intent can be useful and taking user input literally all the time is not actually a great idea.
- melenaboija 5y agoI tried just to see what is returning for just '-1 1' and is able to understand it, as latitude and longitude. But I use 'minus' for these cases.
- omegalulw 5y agoTry torch normalize "-1" 1 It gets me to https://pytorch.org/docs/1.9.1/generated/torch.nn.functional.normalize.html https://pytorch.org/docs/1.9.1/generated/torch.nn.functional... Note that that will only normalize to (-inf, 1]. Tweaking the formula on that page You want (v - vmin) / (vmax - vmin + eps) with vmin and vmax produced along th dimensions you care normalizing against.