Difference between revisions of "2006:MIREX 2006 Submission Instructions"

From MIREX Wiki
Line 11: Line 11:
 
## Meets whatever task-specific requirements were laid down by the task organizers.
 
## Meets whatever task-specific requirements were laid down by the task organizers.
 
## Provides the team at IMIRSEL with a set of''' clear and complete''' instructions on how to run your program.
 
## Provides the team at IMIRSEL with a set of''' clear and complete''' instructions on how to run your program.
# Create a first-draft extended abstract that outlines the basic methods and techniques being deployed in your submission. These extended abstracts:
+
# Create a first-draft extended abstract that outlines the basic methods and techniques being deployed in your submission. See Extended Abstract Details below.
 +
 
 +
 
 +
 
 +
==Extended Abstract Details==
 +
The extended abstracts provide the outside world with a general understanding of what each submission is trying to accomplish. The extended abstracts need NOT be cutting edge/never-before-published materials. The extended abstracts will be revised by the authors after the data has been collected (to allow for commentary on results data); however, we at IMIRSEL we still need the first-pass drafts at submission time to help us understand what is happening in the submission. Like last year we will post the final versions of the extended abstracts as part of the MIREX 2006 results page (see MIREX 2005 Results; https://www.music-ir.org/evaluation/mirex-results/).
 +
 
 +
 
 +
These extended abstracts:
 
## Are two to four pages long (think ISMIR poster/demo papers).
 
## Are two to four pages long (think ISMIR poster/demo papers).
 
## Must be created using the ISMIR 2006 template set: http://ismir2006.ismir.net/info_authors.html .
 
## Must be created using the ISMIR 2006 template set: http://ismir2006.ismir.net/info_authors.html .

Revision as of 16:16, 21 July 2006

Introduction

This is the official set of submission guidelines for MIREX 2006. The URL for MIREX 2006 Submission System can be found at the bottom of this page. We are deliberately placing the Submission URL at the bottom of this page to force folks to thoroughly read through this MIREX 2006 instruction set.

Step-By-Step Instructions

  1. Read this wiki page from top to bottom.
  2. Go read Andreas Ehmann's Best Coding Practices for MIREX
  3. Go read the task-specific instructions for each task to which you will be submitting. Links to each task are available off the MIREX 2006 main wiki page.
  4. For each submission be sure you understand the Input/Output format issues as laid down by the task organizers.
  5. For each submission, be absolutely sure you have constructed a README.txt file that:
    1. Begins with submitter name(s) and contact information (email, etc.).
    2. Meets whatever task-specific requirements were laid down by the task organizers.
    3. Provides the team at IMIRSEL with a set of clear and complete instructions on how to run your program.
  6. Create a first-draft extended abstract that outlines the basic methods and techniques being deployed in your submission. See Extended Abstract Details below.


Extended Abstract Details

The extended abstracts provide the outside world with a general understanding of what each submission is trying to accomplish. The extended abstracts need NOT be cutting edge/never-before-published materials. The extended abstracts will be revised by the authors after the data has been collected (to allow for commentary on results data); however, we at IMIRSEL we still need the first-pass drafts at submission time to help us understand what is happening in the submission. Like last year we will post the final versions of the extended abstracts as part of the MIREX 2006 results page (see MIREX 2005 Results; https://www.music-ir.org/evaluation/mirex-results/).


These extended abstracts:

    1. Are two to four pages long (think ISMIR poster/demo papers).
    2. Must be created using the ISMIR 2006 template set: http://ismir2006.ismir.net/info_authors.html .
    3. Must be submitted in PDF format.
    4. Should have the same general look and feel as these examples from last year: