summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt Cooper <matthew_cooper@brown.edu>2016-08-17 14:05:07 -0400
committerMatt Cooper <matthew_cooper@brown.edu>2016-08-17 14:05:07 -0400
commit9177c7e9696b4fbd6feaecb0067ac1fce0cb5bdb (patch)
tree2c426d806cc7e175baa98d28c9c439a2c59a32af
parent94e1fc50eb8324547a5af3a27d3b44642831b5ea (diff)
parent37046985faf7ddc327148f77a6b410e1bc491d5f (diff)
Merge branch 'master' of https://github.com/dyelax/Adversarial_Video_Generation
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 19481a1..2a4b0d1 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,7 @@ While the adversarial network is clearly superior in terms of sharpness and cons
<img src="https://github.com/dyelax/Adversarial_Video_Generation/raw/master/Results/Gifs/rainbow_NonAdv.gif" width="50%" />
-Using the error measurements outlined in the paper (Peak Signal to Noise Ratio and Sharp Difference) did not show significant difference between adversarial and non-adversarial training. I believe this is because sequential frames from the Ms. Pac-Man dataset have no motion in the majority of pixels. While I could not replicate the paper's results numerically, it is clear that adversarial training produces a qualitative improvement in the sharpness of the generated frames, especially over long time spans. You can view the loss and error statistics by running `tensorboard --logdir=./Results/Summaries/` from the root of this project.
+Using the error measurements outlined in the paper (Peak Signal to Noise Ratio and Sharp Difference) did not show significant difference between adversarial and non-adversarial training. I believe this is because sequential frames from the Ms. Pac-Man dataset have no motion in the majority of pixels, while the original paper was trained on real-world video where there is motion in much of the frame. Despite this, it is clear that adversarial training produces a qualitative improvement in the sharpness of the generated frames, especially over long time spans. You can view the loss and error statistics by running `tensorboard --logdir=./Results/Summaries/` from the root of this project.
## Usage