School of Computer Science and Software Engineering

2003 Research Conference

Search

A-Z Staff Research Profiles

Publications


Seminars


Technical reports

Our technical report series includes the early publication of research and extended versions of research papers.

The 12th School of Computer Science & Software Engineering Research Conference

Conference details

Dates: 9-10 June 2003

Venue: Club Capricorn, Yanchep

Keynote speaker: Professor Richard Hartley, ANU

Final paper: 9 May

Draft papers to supervisors: 28 April

Titles submitted: 28 April

Registration: Anthony Prior and Marisa Gulluni

Conference committee: Rachel Cardell-Oliver, Adam Dunn, Amer Filipovic, Anthony Prior and Marisa Gulluni

Conference programme

View the conference programme.

Call for papers

Papers are invited from all members of the School. The conference proceedings will include both full research papers and and short papers on new research directions.

The expectations on research students at various stages of their studies are clarified below. Contributions are also encouraged from staff, and from participants from other W.A. universities and industry or government organisations.

Beginning Postgraduates [Those starting after 1st January 2003] You should submit a short (1 or more pages) abstract or research proposal outlining the area that you wish to study, and present a short talk (up to 10 minutes). The proposal and discussion need not be very detailed, and are in no way binding. Its purpose is simply to give others some idea of your planned area of research, and allow them to share with you the benefit of any experience they may have in related areas. For example, it may be that some of the staff or students can help with some pointers to literature, software, and resources within the Department that have been used on previous projects in related areas.

Postgraduates [Full-time PhD students within their first 3 years, part-time PhD students within their first 4 years, MSc students within their first 2 years.] You are expected to submit a paper related to your work for inclusion in the proceedings, and to present a talk on the work at the conference. For those who have completed one year this might be oriented more towards surveying the state of the art in your chosen field, discussing of problems you plan to address, and your progress so far. For those in later years it is likely to include more of your own contributions, and might be used as a practice paper for a conference or journal. If you'd like to discuss further what is expected please see your supervisor or one of the organisers.

Finishing Postgraduates [Postgraduates outside the above categories.] You are strongly encouraged to give a talk on your work, but since it is recognised that you may be finishing off and writing up according to fairly tight deadlines, a single abstract page may optionally be submitted in place of a written paper. The page should contain title, author(s) and abstract (title and authors centred and abstract in a centred block flush left and right as it would appear on the front of a paper).

Staff, Visitors, Research Fellows, etc You are invited to give a talk on a subject of interest, and submit either an abstract page (see above) or a paper for the proceedings. These may be technical research talks, or talks on topics of broader interest (eg. the future of computer science, etc).

Honours Students If you have some work that you would like to present you are welcome to submit a paper. But otherwise you are invited to just come along, observe, question, discuss, and have fun!

Information for authors and speakers

Papers should be prepared using the ACM SIG templates provided and should be no more than 10 pages in length in this format. The Author Guide provides detailed information about the preparation of manuscripts. A sample conference paper in the required format is also available.

You will get the best results and your files will be easiest to handle if you use LaTeX2e for the preparation of your camera-ready manuscript together with the corresponding class file CSSEtemplate.cls. Use bibliography style {plain} and see the sample bibliog sigproc.bib for example entries. Using MS Word is not encouraged, since the layout of the pages (the position of figures and paragraphs) can change from printout to printout. Having said this, we do provide the template CSSEtemplate.doc to help MS Word users to prepare their camera-ready manuscripts.

Submissions should be emailed to the conference co-ordinator rachel[at]csse.uwa.edu.au. This email address can also be used for any inquiries concerning the conference.

Please note the deadlines for papers submitted to the conference. These deadlines are necessary in order to allow time for reviewing, collating and printing the proceedings before the event. Note that even if your draft paper is not complete you should still submit what you have so far to your supervisor at this time.

It is anticipated that each speaker will be allocated 25 minutes. The talks themselves should be up to 20 minutes in length, leaving 5 minutes for questions and discussion. Facilities available will include an overhead projector and computer projector. Please contact one of the organisers if you require any special equipment.

A pdf of your camera-ready copy should to be sent to Adam or Amer no later than 3pm on Friday 16th May

Having gone through all the papers, the review board has noticed that there are many discrepancies in the formatting. The purpose of this email is to let you know exactly what the papers MUST look like if you want them to be printed. You can collect your papers from Marisa from 12PM on Wednesday the 14th. Please have a look through the comments. Students, you need to speak to your supervisors to make sure that we have their review forms.

If you have any problems with formatting or the deadline, you need to see either Adam, Tone, Rachel or me before the cut-off date. If you don't and we do not receive your paper by Friday, it will not be included in the proceedings.

Please check below for some comments on the inconsistencies throughout the papers.


Abstracts
If you are submitting an abstract (whether it be a short or a long one) do NOT just have an ABSTACT title with the remaining text all bundled together. You should still have appropriate headings and structure.

If you are writing a full paper, see that your abstract is of a reasonable length. When your topic is placed on the web, your abstract will be there as well, so about 50-100 words is recommended. Remember that abstracts should not have any references.

Author field:
Use only the author{...} clause to format your name and affiliation. Do NOT change the font size for address, emails etc. They should all be the same.
Affiliations for this school should all be the same, ie
School of Computer Science & Software Engineering
The University of Western Australia
35 Stirling Highway, Crawley, W.A. 6009, Australia.

If the paper has multiple authors, and they are all from the same department (same affiliation) then one author block will suffice. For example, this would be at the top of the page

Amer Filipovic, Adam Dunn, Tone Prior
School of Computer Science & Software Engineering
The University of Western Australia
35 Stirling Highway, Crawley, W.A. 6009, Australia.
email: {amer, adam, tone}@csse.uwa.edu.au

If the paper has multiple authors AND they have different affiliation then two columns should be used.

If your supervisor is a co-author then format the names as above. If you only wish to state who your supervisor is, then do so in the
acknowledgements section just before references. Either way, do NOT put something like this in your author block:
Supervisor: Luigi Barone

Classification and Keywords
Full sized papers MUST have the following after the abstract:
Keywords:
CR Classifications:
in BOLD. For short abstracts this is NOT required.

References
Use plain style bibliography and not the ACM style, ie ibliographystyle{plain} in Latex

Formatting When you run latex over your source, please make sure that you address the lines that have gone beyond the margin as this looks very unprofessional.

For the rest of you using MS Word please make sure that your paper is formatted exactly like the sample one provided in this email. Make sure that the fonts are the same, margins align and that the section titles are ALL CAPS.

It is extremely important that our Conference Proceedings look uniform. So please make sure that all of the above issues are addressed.

Venue

The conference venue is the beautiful Club Capricorn , which is a simple 1 hour drive from Perth. It's on the ocean and has a pool so don't forget your bathers if you like to swim in June.

 

 

School of Computer Science and Software Engineering

This Page

Last updated:
Wednesday, 13 February, 2013 8:20 AM

http://web.csse.uwa.edu.au/1076686