Reviews
Submission
Due: 11:59 pm ET on the day before class. Late reviews will not be accepted.
Your grade will be based on your top 15 scoring submissions.Â
You need not submit paper reviews during the classes where you are leading discussions on the paper.
Where to submit reviews? Please submit the reviews at the link (to the Google Form) for each paper in the schedule. See submission instructions below.
Submission: Please type out your review in a text editor of your choice and ensure that your review is of appropriate length before submitting. Your grades for each paper review along with comments (if there are any) will be emailed to you. Please keep in mind that the reviews are due at 11:59pm the night before the class. Any reviews submitted after that will be returned with a grade of 0.
Format
Length <=1 page of total text
11 pt Times New Roman, 1 inch margins
Organization of Review:
Summary:
What is this paper about?
What is the main contribution?
Describe the main approach & results. Just facts, no opinions yet.
Strengths:
Is there a new theoretical insight?
Or a significant empirical advance? Did they solve a standing open problem?
Or a good formulation for a new problem?
Or a faster/better solution for an existing problem?
Any good practical outcome (code, algorithm, etc)?
Are the experiments well executed?
Useful for the community in general?
Weaknesses:
What can be done better?
Any missing baselines? Missing datasets?
Any odd design choices in the algorithm not explained well? Quality of writing?
Is there sufficient novelty in what they propose? Minor variation of previous work?
Why should anyone care? Is the problem interesting and significant?
Reflections:
How does this relate to other papers we have read?
What are the next research directions in this line of work?
What (directly or indirectly related) new ideas did this paper give you? What would you be curious to try?
Most interesting thought: Describe what you believe is your most insightful thought about the paper. It could be next research directions in this line of work, (directly or indirectly related) new ideas that this paper gave you, things that you would be curious to try, connections you've made to other work, etc.
Tips
How to write a review (this is a bit specific to systems papers, but hopefully the high-level messages are useful).