User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
io500:submission:start [2018/12/02 17:47] kunkelio500:submission:start [2021/06/08 09:06] (current) – [Submission instructions] kunkel
Line 1: Line 1:
 ====== Submission ====== ====== Submission ======
  
-//This page contains the information about the submission procedure.//+{{ :io500:submission:sticker.png?200|}}
  
-{{ :io500:submission:sticker.png?200 |}}+ 
 +//This page contains the information about the submission procedure.//
  
 ===== Deadline ===== ===== Deadline =====
  
-The IO-500 list is released during ISC and SC. See our [[io500:submission:cfs|call for submissions]].+The IO500 list is released during ISC and SC. See our [[io500:submission:cfs|call for submissions]].
 Submissions to the upcoming list can be made all year.  Submissions to the upcoming list can be made all year. 
-However, **to be included in the next release**, we must receive the submission the last Sunday before of the respective conference.+However, **to be included in the next release**, we must receive the submission until the deadline listed in our [[io500:submission:cfs|call for submissions]].
  
 ===== Submission instructions ===== ===== Submission instructions =====
  
-There are two options to submit to the IO-500, we prefer the online form:+There are two options to submit to the IO500, we prefer the online form:
  
 1) Use our [[https://www.vi4io.org/io500-submission/|online form]]. You have to receive a one-time token (please check your SPAM folder if you did not receive the initial response 5 minutes later). 1) Use our [[https://www.vi4io.org/io500-submission/|online form]]. You have to receive a one-time token (please check your SPAM folder if you did not receive the initial response 5 minutes later).
  
-2) If you experience any problems with the online form; send an [[mailto:submit@io500.org|email]] with attachments:+2) If you experience any problems with the online form; send an [[submit@io500.org|email]] with attachments:
   * The (potentially) adapted io500.sh   * The (potentially) adapted io500.sh
   * The output directory of the benchmark (variable io500_result_dir in io500.sh)   * The output directory of the benchmark (variable io500_result_dir in io500.sh)
Line 34: Line 35:
  
 === Submitter name === === Submitter name ===
-Submissions will be visible immediately to the IO500 Committee which currently is comprised of John Bent, Julian Kunkel, and Jay Lofstead.  If there is sensitivity about early visibility to your results being seen by any of the committee (e.g., John works for DDN), please feel free to email results privately to a subset of the committee (i.e. do not use the official submission tools if you have privacy concerns).+Submissions will be visible immediately to the IO500 Committee which currently is comprised of John Bent, Andreas Dilger, Julian Kunkel, Jay Lofstead, and George Markomanolis.  If there is sensitivity about early visibility to your results being seen by any of the committee members, please feel free to email results privately to a subset of the committee (i.e. do not use the official submission tools if you have privacy concerns).
  
 Starting with the SC'18 list, releases include the name of the submitter (or team) to give them the credit they deserve to execute the benchmark; this can be opted out. Starting with the SC'18 list, releases include the name of the submitter (or team) to give them the credit they deserve to execute the benchmark; this can be opted out.
Line 52: Line 53:
  
 Fetching, compiling, and running the IO500 Benchmarks is surprisingly straightforward.  Fetching, compiling, and running the IO500 Benchmarks is surprisingly straightforward. 
-Although tuning can be challenging.  Instructions for the former can be found in our [[https://github.com/VI4IO/io-500-dev|github repo]].  Help with the latter can be found in our various [[https://www.vi4io.org/std/io500/start#communication_contribution|communication channels]].+Although tuning can be challenging.  Instructions for the former can be found in our [[https://github.com/IO500/io500|github repo]].  Help with the latter can be found in our various [[https://www.vi4io.org/std/io500/start#communication_contribution|communication channels]].