All presenters are requested to report to the chair of their respective sessions way in advance. Presenters should test their slide, video etc. on the provided A/V facilities during the breaks and before their sessions. Volunteers would be available to help, however, presenters are responsible for setting up their slides and collecting them after the presentations. Following A/V facilities will be provided:
fg96-oral-presenters@media.mit.edu -> Jim.Crowley@imag.fr, Joelle.Coutaz@imag.fr, Thomas.Maurer@neuroinformatik.ruhr-uni-bochum.de, ajh@scs.leeds.ac.uk, bim@sv1.smb.man.ac.uk, brand@media.mit.edu, ccohen@ariel.cybernet.com, charles@umich.edu, costen@hip.atr.co.jp, covell@interval.com, wren@media.mit.edu, dnm@central.cis.upenn.edu, drew@media.mit.edu, elwin@media.mit.edu, fcmk@watson.ibm.com, freeman@merl.com, geiger@cs.nyu.edu, hpg@research.att.com, jochen@neuroinformatik.ruhr-uni-bochum.de, juxuan@vis.toronto.edu, kcy@eng.cam.ac.uk, mbichsel@ifi.unizh.ch, mlew@wi.leidenuniv.nl, nagaya@trc.rwcp.or.jp, otoole@utdallas.edu, quek@eecs.uic.edu, tonebone@ai.mit.edu, vetter@mpik-tueb.mpg.de, wechsler@cs.gmu.edu, weng@cps.msu.edu, wilder@caip.rutgers.edu
Carefully and completely prepare your poster well in advance of the conference. There will be no time nor materials available for last minute preparation at the conference. Try tacking up the poster before you leave for the conference to see what it will look like and to make sure that you have all of the necessary pieces.
Your poster should cover the key points of your work and should be complimentary to the publication in the proceedings. It need not, and should not, attempt to include all the details; you can describe them to people who are interested. The ideal poster is designed to attract attention, provide a brief overview of your work, and initiate discussion.
The title of your poster should appear at the top in CAPITAL letters about 25mm (1 inch) high. Below the title put the author(s)' name(s) and affiliation(s). The flow of your poster should be from the top left to the bottom right. Use arrows to lead your viewer through the poster.
Use color for highlighting and to make your poster more attractive. Use pictures, diagrams, cartoons, figures, etc., rather than text wherever possible.
Use text sparingly. Try to state your main result in 6 lines or less, in lettering about 15mm (5/8 inch) high. This way people can read the poster from a distance.
People will not read a lot of text, and certainly won't read typewriter-sized text. The smallest text on your poster should be at least 9mm (3/8 inch) high, and the important points should be in a larger size. If possible, use a "sans serif' font, for example "cmss" in the Computer Modern family or the "Helvetica" Postscript font. It will be easier for people to read from a distance.
Make your poster as self-explanatory as possible. This will save your efforts for technical discussions.
We request that posters should be put up either the night before the day of presentation or in the morning of the day of the session and should remain up the whole day. This will allow for informal interaction between the authors and the attendees during the whole day.
If possible, more than one author should attend the session to aid in presentations and discussions, and to provide the presenters with the chance to rest or briefly view other posters.
You may bring additional battery operated audio or visual aids to enhance your presentation. If you need to use additional A/V equipment for your poster presentation, please let us know by sending us an email at fg96@media.mit.edu. We will provide you with contact info on companies that can rent you such equipment. We do not guarantee availability of all desired A/V facilities for your poster presentation.
Title: Author(s)' Name(s): Author(s)' Affiliations(s): 25 word or less description of the poster: 3 keywords that describe the work.This information will be used to introduce your poster to the Attendees.
fg96-poster-presenters -> Richard.Lengagne@inria.fr, TakacsB@aol.com, alex@cs.uow.edu.au, antonio@ifp.uiuc.edu, collobem@lannion.cnet.fr, dkroy@media.mit.edu, dmachin@bt-sys.bt.co.uk, edp@bell-labs.com, fcmk@watson.ibm.com, franklin@cs.uchicago.edu, gje@sv1.smb.man.ac.uk, h.demirel@ic.ac.uk, herpers@gsf.de, hienz@techinfo.rwth-aachen.de, jonh@cogs.susx.ac.uk, kakusho@sanken.osaka-u.ac.jp, kcy@eng.cam.ac.uk, mturk@microsoft.com, nishi@trc.rwcp.or.jp, reinders@et.tudelft.nl, rhoogenb@wi.leidenuniv.nl, saxe@asel.udel.edu, sgg@dcs.qmw.ac.uk, sobottka@zeus.csd.auth.gr, sourabh@media.mit.edu, stephen@dcs.qmw.ac.uk, wechsler@cs.gmu.edu, weng@cps.msu.edu, wuhy@yachi-lab.sys.es.osaka-u.ac.jp, yaser@cs.umd.edu