General Comments for Micro-Reviews
Style, Spelling, Grammar, Punctuation, and Format
Take the time to write high-quality micro-reviews. They are short, so you should be able to re-read them at least once to make sure there are no spelling errors or types, and that your sentences are grammatically correct.
Here is a check list you can use:
-
Do not use contractions in academic writing. For example, “didn’t” should be “did not”, “wouldn’t” should be “would not”, “it’s” should be “it is”.
-
The possessive form of “it” is “its”, not “it’s”.
-
Remember your articles. For example, “… recognizing user’s hand …” should be “… recognizing the user’s hand …” and “In evaluation part …” should be “In the evaluation part …”
-
We are in Canada, so you should use Canadian spelling. For example, “color” should be “colour” and “behavior” should be “behaviour”.
-
Avoid using a slash in academic writing. For example, “and/or” can be writing simply as “or” and multiple terms like “student/teacher” can be linked like “student and teacher”.
-
Avoid using “etc.” when listing several points, and write your sentence to make it clear you are only providing a few examples. For example, “uses the colours red, blue, green, etc.” can be written as “uses colours like red, blue, or green.”
-
Use consistent terminology and spelling. For example, stick with “smartphone” rather than sometimes calling it a “smart phone” or a “cellphone”.
Critique
Focus on strengths, weaknesses, and extensions that involve both HCI and computer vision. Avoid comments strengths or weaknesses are solely focused on the performance of the computer vision algorithm, unless you can explain what repercussions such poor performance might have for HCI. Avoid extensions focused on improving or testing the algorithm, such as using deep learning or similar. An exception is if you can provide a clear tie to how the HCI is also enhanced using that new algorithm.
Other points:
-
Focus on one thing for your strength, one thing for your weakness, and one thing for your extension. Those things do not need to be related.
-
Your strength should not be so high level that it essentially summarized the main contribution of the paper. Pick something specific that you liked about the research and focus on that.
-
Try to think of weaknesses other than pointing our flaws in the study, or the fact that there was no study.
-
Try to think of weaknesses thaat are not simply related to things like the prototype size, battery life, or cost. These really are not important for this line of research, and in most cases, they can be improved with further engineering and economies of scale. Focus on the HCI and CV research.