VRST
The ACM Symposium on Virtual Reality Software and Technology (VRST) is an international forum for the exchange of experience and knowledge among researchers and developers concerned with VR/AR software and technology.
ARCHIVES
STEERING COMMITTEE
MEMBERS
Yoshifumi Kitamura,
Chair
Tohoku University, Japan
Steven Feiner
Columbia University, USA
Daniel Thalmann
Nanyang Technological
University, Singapore
Mark Green
University of Ontario
Institute of Technology,
Canada
Morten Fjeld
Chalmers University of
Technology, Sweden
Yuichi Itoh
Aoyama Gakuin University, Japan
Rob Lindeman
University of Canterbury, New Zealand
CALL FOR PROPOSALS TO HOST FUTURE VRSTs
The Steering Committee welcomes proposals for hosting and organizing future VRSTs (http://vrst.acm.org). It is typically held in October or in November, and care should be taken to avoid date conflicts (with regard to the event and submission deadlines) with international conferences or other events such as SIGGRAPH Asia, UIST, ISS, ISMAR, ICAT, and EGVE, that attract a similar audience and overlap regarding topics. VRST is sponsored by ACM SIGCHI and SIGGRAPH. VRST attracts an interdisciplinary audience from HCI and VR, engineering, science, design, psychology, education, medicine, and the arts, and provides a platform for discussion and meeting people. We value diversity and aim to learn from other perspectives. VRST customarily had a single presentation track for all oral presentations of papers (full and short) and other presentation categories (typically posters and demos). But they come to be presented in parrel sessions recently.
After receiving the proposal, the VRST Steering Committee will make a decision within approximately two months. Please email your proposal as a pdf document to steeringcommittee@vrst.hosting.acm.org.
- People involved in the bid and their roles (at minimum, a symposium and papers chair). Please include a short bio for core people and highlight involvement in previous VRSTs and with the VR/HCI community
- Commitment to publish the proceedings with ACM and to apply for ACM sponsorship (carefully read Conference Planning Guide )
- Likely sponsors and subsidies
- Budget overview (venue hire, etc.) and anticipated financial model. For this purpose, look at the ACM Technical Meeting Request Form (TMRF) requirements and include a sketch of the answers to the main questions, and an idea of how your overall budget will map onto the ACM issues. Note that a Preliminary Approval Form (PAF) is expected to be submitted by 18 months prior to the conference, and the TMRF needs to be approved at least 12 months prior to the conference.
- Rough idea of likely costs for visitors (estimates only): registration rates for students and non-students (including the dinner)
- Proposed location, how to reach it and details about a possible venue
- Potential date(s) for the conference
- Estimated time for issuing the CFP, submission deadlines and registration deadlines
- Arguments for why VRST as proposed by you will be attractive to the VR/HCI community (e.g. accessibility, international rotation, location, relation to specific sub-communities, ability to attract both new and 'old' conference visitors)
- Organizational support at the hosting location
- Any direction/theme change you would envisage and any new features/tracks you would like to include
- Carefully read Organizer Resources.
- Effectively use community supports for different types of Conference Support, Community Support and Student Support for members, conferences and student members. We would suggest a link from your website to this information so your delegates can find it.
- ACM affirms the principle that its conferences shall be accessible to any and all persons, and will make every reasonable effort to accommodate their needs for attendance and participation. (Read ACM Accessibility Statement) The ACM Special Interest Group on Accessibility (SIGACCESS) has issued an Accessible Conference Guide with information on digital and physical accessibility standards.
- VRST history is appeared at VRST history page.