 |
|
| |
Submission Procedure Checklist
Use the checklist below to ensure that your submission is complete and meets
all applicable program requirements.
1. Complete the online SIGGRAPH 2004 Courses Submission Form. There you will find instructions on how to complete the online form. When you begin the form, your submission will be assigned a submission ID number that will be used to identify your submission throughout the review process.
2. Course proposals must be submitted electronically via the SIGGRAPH 2004
online submission system. No other method of submission will be accepted. Fax
submissions are not accepted. Submission procedures are specified in the
online submission process.
3. If your course proposal is accepted, all other speakers in your course must sign and send in the online
SIGGRAPH 2004 Acceptance Agreement. If we do not receive all of the appropriate
acceptance agreements before SIGGRAPH 2004, your course cannot be presented.
4. Your course proposal should include:
- Course title
- Category
- Course organizer
- Proposed length (full-day, half-day, tutorial)
- Proposed presentation venue (regular session room or a wireless facility)
- A summary statement. A two- or three-sentence description
(50 words or less) of the course suitable for pre-conference publicity.
Publication deadlines preclude revision of this statement.
- Names of lecturers.
- A course abstract. 300 words or less describing your
course. The abstract must be suitable for for publication.
- A list of prerequisites. This should explicitly convey to prospective
attendees the type of background material that they need to know in order to
follow the course presentation (50 words or less). Prerequisites might
include specific mathematics, experience with graphics, and/or particular
application areas, etc. They will be used in SIGGRAPH 2004 promotional
materials and on the web site.
- Level of difficulty (beginning, intermediate, advanced). If your course
level of difficulty is beyond beginning, what pre-knowledge is assumed?
- Intended audience. Who is most likely to benefit from this course? What
will they learn? What tools
will you provide to help them achieve the learning goals of your course?
- A detailed course syllabus. This is the heart of the submission. It should present a logical flow of the materials. It should give the precise time schedule of the course and of each individual section within the course. It should include who is teaching what and when, and sub-titles of the course sections.
- Sub-titles of the course sections. Use the sub-titles
of the course sections exactly as they appear in your syllabus.
- Redesigned course length. Can your course be redesigned to fit into a shorter time frame (Tutorial or Half-Day Course)? If not, that's okay. If yes, please tell us specifically how you might achieve this. Which sections and lecturers would be cut and/or reduced in presentation time?
- Use of extant materials. Will you make use of any extant materials (bibliographies, annotated bibliographies, relevant web links, etc.)? If yes, what are those materials, and how are they relevant to the syllabus? Also, how will these materials be delivered to the audience?
- Course history. Has your course been taught at previous SIGGRAPH conferences? If yes, when was it presented, and how is this proposal different from what you've taught before? Why should it be taught again? If no, has it been taught elsewhere? If yes, when and where, and why present it at SIGGRAPH 2004 as well? If no, explain the importance of this course to SIGGRAPH 2004 attendees.
- An example of the course notes. An example of the type and style of course notes that the organizer plans to provide. Think about what you would want as a record if you were taking this course. In most cases, Course Notes are not simply a reiteration of presentation slides. They augment the presentation. Think of these as the learning tools beyond the classroom that you will offer your students. Though you are not required to submit your completed course notes when you submit your course proposal (in fact, we discourage that), you should give specific examples of what your notes will look like. Sparse textual descriptions of your notes will not be sufficient for the reviewers to evaluate.
A good example of Course Notes submitted with a course proposal
(10 Mb PDF)
A good example of final Course Notes prepared after a course proposal is accepted
(12 Mb PDF)
- Special notes requirements. Explain requests, if any, to include
auxiliary materials, such as textbooks, videos, slides, or software with the
SIGGRAPH 2004 published course notes. Important: SIGGRAPH 2004 does not pay
for the cost of including auxiliary materials with course notes.
-
Special presentation requirements. Explain requirements for hands-on
demonstrations, special equipment, or unusual presentation techniques.
Course organizers are required to provide any equipment beyond the standard
SIGGRAPH 2004 configuration.
- Course presenter information. Name, title, affiliation, and a short
biography (100 words or less) for the organizer and each lecturer.
- Organizer contact information. Occasionally there is a need to contact
the course organizer shortly before, during, or immediately after the jury
meeting, so SIGGRAPH 2004 needs to have accurate contact information
(including phone numbers) for January and February of 2004.
5. OPTIONAL: Use the English Review Service to help with the text of your submission.
|
|
| |
|
|
|
