Writing a good ISMAR paper

目录

Writing a good ISMAR paper:

What problem are you addressing?

What were the previous approaches?

How well did you address your stated problem?

What does this work contribute to the field?

Is the paper complete?

Does the paper contain too much information?

Can this paper be presented well?

Should a video also be included?

---

http://www.ismar19.org/news/164.html

Writing a good ISMAR paper:

A good ISMAR submission will result in both a respectable document for the proceedings and a good conference talk. As an author, you should ask yourself the following questions while writing your paper. Submissions that do not provide good answers to these questions are unlikely to be accepted.

 

What problem are you addressing?

The most common motivation for publishing a paper is to present a solution to a problem. When doing so, try to state all your constraints and assumptions. This is an area where it can be invaluable to have someone who is not intimately familiar with your work read the paper. Include a crisp description of the problem in the abstract and try to suggest it in the title. Note that the program chairs depend almost completely on the abstract and title when they determine which program committee member to assign to the paper.

ISMAR papers often focus on a certain aspect of Mixed and Augmented Reality systems. The following list includes some example topics, but does not represent an exhaustive list of all topics. We welcome any new idea beyond the usual range of areas.

•  Interaction Methods: Does the paper propose a novel interaction method? Does it present different use cases and applications for it? Can it demonstrate that the method performs better than other known ones?

• User Interface & Human Factors: Does the paper describe how Mixed and Augmented Reality is improving a user interface design, human task performance or perception?

• Tracking and Pose Estimation: Does the paper describe a novel method that is more robust in difficult conditions (lighting, outdoor, fast motion)? Is it a new, clever combination of different sensors? Does it provide more information for use in interaction and rendering?

• Rendering and Visualization: Does the paper describe a novel, improved method for realistic integration of virtual graphics into a mixed scene? Is it faster or more accurate than known methods? Does it present a novel way of presenting information about the real world?

• Displays and Input Devices: Does the paper describe a novel display (e.g., visual or aural)? Does it describe a novel input device that provides different input modalities, is easier to use and deploy or more precise?

• Applications: Is the paper proposing a new application of Mixed and Augmented Reality in a specific domain? Are you providing a new understanding of usage patterns and social behavior of a deployed AR application?

 

What were the previous approaches?

What are the relevant published works in your problem area? What deficiencies in their approaches are you trying to overcome? How does the new approach differ from previously published results? Don't expect the reviewers to know this information without telling them in the paper, as they are unlikely to remember the precise details of all the relevant literature. Make specific comparisons between your work and that described in the references; don't just compile a list of vaguely related papers.

 

How well did you address your stated problem?

Based on your problem statement, what did you accomplish? You are responsible for arguing that the problem is sufficiently addressed. Include pictures, statistics, or whatever is required to make your case. If you find this part of the paper difficult to write, perhaps the work is not yet finished and the paper should be deferred until next year. (And, perhaps, submitted as a poster this year).

The following describes some typical evaluations methods for different kinds of papers. This list is not exhaustive, but provides some hints as to what can help to present your contribution.

• Interaction Methods: How usable is the method or system? What is the performance of users (e.g. completion time, error rate, learning curve) compared to a previous interface developed for a similar task?

• User Interface & Human Factors: Is the improvement or effect described well supported through evaluations? Was the experimental design appropriate to your solution? Were sample size, statistical evaluation, and presentation and conclusions appropriate?

• Tracking and Pose Estimation: How robust is your system? Can it deal with difficult input including light conditions, fast motion, occlusions? How fast is it and on which hardware? How does it compare to known state-of-the-art systems? It is also a good idea to use a standard data set to make the results comparable to other publications, or make your test data sets available for other authors.

• Rendering and Visualization: Is the output quality of your system superior to previous methods? Is it faster or capable to operate at real-time rates? What hardware and sensors does it require? For visualization, what use cases does it cover? What amount or complexity of data can it deal with?

• Displays and Input Devices: What are the performance specifications of the display? For example, for a visual display does it work in indoor/outdoor, strong light conditions, what is the field of view, and is it multi-user capable? What is the hardware/software required to recreate it? What are the specifications of the input device? Can it be used in a mobile setting?

•  Applications: How did you design the system, what was the input from the application domain? Was the system tested by end users in the application domain? Did it improve their performance? Did it create new opportunities to improve the work methods?

 

What does this work contribute to the field?

What are your new ideas or results? If you don't have at least one new idea, you don't have a publishable paper. Can your results be applied anywhere outside of your project? If not, the paper is probably too special-purpose for ISMAR. On the other hand, beware of trying to write a paper with too large a scope.

 

Is the paper complete?

The question that generates a large amount of discussion at the program committee meeting is whether a paper is complete. If the paper presents an algorithm or technique, an experienced practitioner in the field should be able to implement it using the paper and its references. If the paper claims to present a faster or more efficient way of implementing an established technique, it must contain enough detail to replicate the experiment on competing implementations. When you quote numbers, be sure that they are not misleading—state clearly whether they were measured, simulated, or derived, and how you did the measurements, simulations, or derivations. For example, CPU time measurements are meaningless unless the reader is told the machine and configuration on which they were obtained.

 

Does the paper contain too much information?

Many large, poorly written papers contain a good paper trying to get out. It is the author's responsibility, not the reviewer's, to discover this paper and turn it into the submission. If you have addressed a single, practical problem, don't try to generalize it for the purposes of publication. If you have a formal theory or elaborate architecture, don't include all the vagaries of the implementation unless they are critical to the utility of the theory. Don't include the contents of your user's manual; instead, describe the model or functionality achieved. You should assume your audience has a working knowledge of user-interface development and access to the major journals in computer science, electrical engineering, and psychology. A short conference paper can only present a few concise ideas well.

 

Can this paper be presented well?

While ISMAR papers are judged primarily as technical papers, some consideration is given to how suitable the topic is for a conference presentation. Think of how you would present your ideas, and how big the audience is likely to be. Papers that have a small number of concisely stated new ideas and that are visually interesting tend to appeal to a large audience and be easy to present. As recent conferences clearly show, these criteria do not eliminate papers that have taxonomies or strong theoretical content, or appeal to a specialized audience, if they contain significant new ideas.

 

Should a video also be included?

A video can be very helpful for communicating technical results, especially when the paper discusses an interaction technique. However, do not try to save space in the paper by putting essential information into the video. The paper must stand on its own.