User Tools

Site Tools


Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Previous revision
io500:submission:start [2018/06/28 10:02]
io500:submission:start [2018/10/24 08:43] (current)
kunkel
Line 1: Line 1:
 +====== Submission ======
 +
 +//This page contains the information about the submission procedure.//​
 +
 +===== Deadline =====
 +
 +The IO-500 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. 
 +However, **to be included in the next release**, we must receive the submission the last Sunday before of the respective conference.
 +
 +===== Submission instructions =====
 +
 +There are two options to submit to the IO-500, 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).
 +
 +2) If you experience any problems with the online form; send an [[mailto:​submit@io500.org|email]] with attachments:​
 +  * The (potentially) adapted io500.sh
 +  * The output directory of the benchmark (variable io500_result_dir in io500.sh)
 +  * If possible, please mention which system is covered of the [[:​hpsl:​start|CDCL]] or provide system information such that we can add the system to the CDCL!
 +
 +We will reply to you, to confirm reception and any question that may arise.
 +
 +===== Handling of the submitted data =====
 +
 +Until the release of the list, the submission committee will handle all submitted data confidentially.
 +That means that we will not disclose any submitted data to individuals/​companies,​ or institutions.
 +
 +==== Privacy ====
 +
 +We will publish all data submitted, so by submitting the information you **give us the right to publish the uploaded data**. ​
 +
 +=== 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).
 +
 +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.
 +
 +=== Annonymity and embargo ===
 +
 +With the online form, the submitter is able to individually opt-out or embargo (delay) the release of certain information:​
 +1) The name of the submitter/​team (anonymous submission)
 +2) Specific information that would indicate the system; e.g., the file system, the name of the site, supercomputer ...
 +
 +After an embargo period the specific information is revealed and updated automatically in the subsequent list following the end of the embargo period.
 +The period is either 3 years, or after the machine is decommissioned (the embargo period is asked in the online form).
 +
 +
 +
 +===== Preparation =====
 +
 +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]].
 +