Blog Post 2: Writing Style
This second post is describing, what makes a writing output a good (or bad) piece of text, especially regarding the organization of the paper, wording without looking at the content.
I chose the paper Generative Adversarial Networks from Ian J. Goodfellow (https://arxiv.org/pdf/1406.2661.pdf), as I am very interested in this topic, my master thesis is about GANs and this paper is already familiar with me. It propose a new framework for estimating generative models via an adversarial process, in which the researchers simultaneously train two models: a generative model G that captures the data distribution, and a discriminative model D that estimates the probability that a sample came from the training data rather than G. This paper is often cited and is also the starting point for anyone who learns about GANs, even though that paper is from 2014!
Paper Title
The title is short and sweet, at it is called "Generative Adversarial Nets". Everybody who reads this tile knows what this paper is about. Looking back, as this paper is the first paper for GANs, it could have been a bit more specific, like "Generative Adversarial Network: how it works"
Abstract
The abstract is mainly describing how the framework for GANs work in a very simple way, with easy words, so even people who are not too familiar with it have an easy start. It doesn't really state the problem they want to solve with their new framework and also they already mention the outcome, which I am not sure if it is allowed or not.
Introduction
The introduction clearly describes the problem, why it is interesting to solve it and the potential benefits to it, and what the key components are. It also shortly describes how their implementation is different to the other state of the art solutions.
Related Work
They show the two most used frameworks which are similar to their solution.
Main body
The logic of how they describe the framework makes sense and it follows the same principle as if you would implement it, which I quite like as a Computer Scientist. For each additional element added to the framework, a paragraph describes why it is needed and how it interacts with the others. This is super helpful, as it makes the paper much easier to read and you get the idea faster. Also this is needed as the content is quite difficult.
Furthermore, they use helpful graphics, which are very well described (partly half a page long) and they describe the algorithm with pseudocode (Latex algorithm group).
Conclusion and future work
Dear Antonio,
ReplyDeleteThanks for the concise comments about your paper of interest. In your blog post you have gone through all main sections of your paper and reflected on them with short sentences, which I really like. And the part with References, I get your point of view about it and it's usual to cite your own papers, on one side for the visibility and the other, for not repeating previously presented material in your text, if the new paper is in line with the previous ones.
Keep up with good work!
Best
Mohsen
Dear Antonio,
ReplyDeleteI think it is a great idea that you started your review with a little introduction on the subject of your paper and why you have chosen it. Your analysis of the paper was well-written, and I was quite impressed by the fact that you also commented on the use of Latex for some parts of the paper. To be honest I also haven't seen many papers with high self-citations and I really don't know why some researchers do that.
All in all, your review was very interesting and comprehensive and gave me all the information I needed to have a general idea how the paper is written.
Nice job!
Kind regards,
Kiavash