Change input value in examples of BCEWithLogitsLoss

[nai62]

In the examples of BCEWithLogitsLoss, 0.999 is passed as the prediction value. The value 0.999 seems to be a probability, but actually it's not. I think it's better to pass a value that is greater than 1, not to confuse readers.

[dr-ci]

💊 CircleCI build failures summary and remediations

As of commit a093c3b (more details on the Dr. CI page):

---

✅ None of the build failures appear to be your fault 💚

---

• 4/4 broken upstream at merge base a500491 since Mar 02

  Please rebase on the viable/strict branch (expand for instructions)

  If your commit is newer than viable/strict, you can try basing on an older, stable commit:

  git fetch origin viable/strict
  git rebase --onto viable/strict $(git merge-base origin/master HEAD)
  

  If your commit is older than viable/strict:

  git fetch origin viable/strict
  git rebase viable/strict
  

  Check out the recency history of this "viable master" tracking branch.

---

🚧 4 upstream failures recognized by patterns:

These were probably caused by upstream breakages:

• pytorch_windows_vs2019_py36_cuda10.1_build from Mar 02
• caffe2_onnx_py2_gcc5_ubuntu16_04_test from Mar 02
• caffe2_onnx_py3_6_clang7_ubuntu16_04_test from Mar 02
• pytorch_linux_backward_compatibility_check_test from Mar 02

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker.

This comment has been revised 2 times.

[ezyang]

Some more context: https://discuss.pytorch.org/t/bceloss-vs-bcewithlogitsloss/33586/9

[facebook-github-bot]

@ezyang is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[facebook-github-bot]

@ezyang merged this pull request in a57a7b4.