Switch to unified view

a b/paf-prediction-challenge-database-1.0.0/challenge/index.shtml
1
<!--#set var="TITLE" value="Obtaining CinC Challenge 2001 Scores"-->
2
<!--#include virtual="/head.shtml"-->
3
4
5
<h2>About the events</h2>
6
7
<p>
8
The PAF Prediction Challenge Database consists of 50 pairs of half-hour ECG
9
recordings. Each pair of recordings is obtained from a single 24-hour ECG.
10
Subjects in group A experienced PAF; for these subjects, one recording
11
ends just before the onset of PAF, and the other recording is distant in
12
time from any PAF (there is no PAF within 45 minutes before or after the
13
excerpt). Subjects in group N do not have PAF; in these, the times of the
14
recordings have been chosen at random.
15
16
<p>
17
The number of subjects in group N is <em>n</em>
18
(where 20 &lt; <em>n</em> &lt 30).  The number of subjects in group A is
19
thus 50-<em>n</em>, a number also between 20 and 30.
20
21
<p>
22
<b>Event 1 (Screening) is intended to determine if subjects in group A can
23
be distinguished from those in group N</b>. (In other words, can individuals at
24
risk of PAF be identified within a larger population, based on their ECGs?)
25
Since each subject is represented by a pair of consecutively numbered records
26
in the database, entrants in event 1 of the challenge should provide one
27
classification (`A' or `N') for the 50 odd-numbered records only
28
(<tt>t01</tt>, <tt>t03</tt>, <tt>t05</tt>, ... <tt>t99</tt>).  The number of
29
correct classifications (0 to 50) is the event 1 score.
30
31
<p>
32
<b>Event 2 (Prediction) is intended to determine if subjects in
33
group A have distinctive and detectable changes in their ECGs
34
immediately before PAF</b>.  (In other words, is the imminent onset of
35
PAF predictable in an individual known to be at risk of PAF?)  A
36
successful method for doing so should be able to determine which
37
record of each pair of group A records immediately precedes PAF.  If
38
the identities of the group A records were known, it would be
39
sufficient to classify these records only; since the goal of event 1
40
is to identify group A, however, we have not provided this
41
information!  Entrants in event 2 of the challenge must therefore
42
classify exactly one of each pair of records in the test set as `A'
43
(defined as ``<em>immediately preceding PAF, if the patient belongs to
44
group A</em>''), and the other as `N' (defined as ``<em>not
45
immediately preceding PAF</em>'').  One point is awarded for each
46
correctly classified record pair, so that the event 2 scores range
47
from <em>n</em> to 50 (the lower bound is <em>n</em> because the group
48
N subjects are always considered correctly classified).
49
50
<h2>Preparing your entry</h2>
51
52
<p>
53
Your entry needs to be prepared in a special text format, which depends on
54
the event you are entering:
55
56
<ul>
57
<li> For event 1 (Screening), download this <a
58
href="template-test-1">template</a>,
59
and replace the `?' characters with your classifications (`A' or `N')
60
for each of the 50 record pairs in the test set.
61
62
<li> For event 2 (Prediction), download this <a
63
href="template-test-2">template</a>,
64
and replace the `?' characters with your classifications (`A' or `N')
65
for each of the 100 records in the test set.
66
</ul>
67
68
<h2>Submitting your entry for scoring</h2>
69
70
<p>
71
Please double-check your entry before submitting it to be sure it is in
72
<strong>plain text</strong> format, exactly like the template files.
73
<em>HTML-formatted entries will confuse the automated scorer and will not be
74
scored.</em>
75
76
<p>
77
To submit your entry successfully, you will need:
78
79
<ul> 
80
<li> A web browser that supports HTTP uploads, such as Netscape 2.0 or
81
 later, or MS Internet Explorer 4.0 or later.
82
83
<li> A valid e-mail address that is known to us.  Please
84
 <a href="/register.shtml">sign in</a> before submitting your entry.
85
 (If you signed in on a previous visit, you do not need to sign in again.)
86
 All entries are logged by date, time, and the e-mail address of the
87
 entrant.
88
89
 <p>
90
 <b>Important:</b>  Your score will be sent by e-mail to the address you
91
 specify.  Please be sure that your e-mail address is entered correctly,
92
 or you won't be able to view your score.
93
94
<li> A password.  If you don't yet have a password, or if you
95
 have forgotten your password, go to the entry form (see below), fill
96
 in only your e-mail address, click on the "Get password" button, and a
97
 password will be sent to your e-mail address immediately.
98
</ul>
99
100
<p>
101
After filling in your e-mail address and password on the 
102
<a href="http://www.physionet.org/cgi-bin/cinc-2001-score">entry form</a>.
103
enter the name of the file that contains your correctly-formatted entry
104
(you may use the <b>Browse</b> button to find it), indicate which
105
event you wish to enter, and click on <b>Upload entry</b>.
106
107
<p>
108
If you wish to enter both events, you may do so, but you will need to
109
submit separate entries, one in each format, in this case.
110
111
<h2>Notes</h2>
112
113
<p>
114
Please be careful not to submit more than one copy of the same results, since
115
each submission will be counted against your quota of submissions.  If this
116
happens inadvertently, please
117
<a href="mailto:webmaster@physionet.org subject=duplicate entry">send a
118
note</a> quoting the date and time of the duplicate submission;  your
119
submission counter will be adjusted manually if the error can be confirmed.
120
121
<p>
122
If you are tempted to try submitting many entries in order to learn about the
123
correct classifications, why not play <a
124
href="http://www.lizardpoint.com/fun/mastermind/mastmind.html"
125
target="other">Mastermind</a> instead?  We will reject obvious attempts to
126
circumvent the spirit of the challenge in this way, including entries that do
127
not have the correct number of classifications (50 for event 1, 100 for event
128
2), entries in event 1 with fewer than 21 or more than 29 `N' classifications,
129
entries in event 2 that do not have exactly one `A' classification for each of
130
the 50 record pairs, and large numbers of entries from a single entrant.
131
Delivery of your score may be delayed if you submit more than one entry per
132
event per day.
133
134
<p>
135
UNIX versions of Netscape, and possibly other browsers, will allow the
136
user to specify a directory name in the <b>File to upload</b> field of the
137
entry form, but the browser will not transmit anything in this case and will
138
hang until the user interrupts it by clicking on <b>Stop</b>.  This behavior
139
is a bug in the browser and cannot be detected or avoided by the PhysioNet web
140
server.  Other browsers will detect and disallow attempts to upload
141
directories.
142
143
<a name="faq"><h2>Frequently asked questions</h2></a>
144
145
<p>
146
If your question is not answered below, please consult the
147
<a href="/faq.shtml">PhysioNet FAQ</a>.
148
149
<p>
150
<b>Group B subjects are not explicitly defined in the text. I assume these
151
are Group N subjects?</b>
152
153
<p>
154
This is correct.  Group B was renamed Group N.  There should no longer be any
155
references to Group B.  Sorry for the confusion!
156
157
<p>
158
<b>We have to put exactly one A under one of the subjects of each even-odd
159
pair in event 2.  Does this mean that exactly 50 As and 50 Ns are expected in
160
a submission for event 2 scoring?</b>
161
162
<p>
163
This is also correct.
164
165
<p>
166
<b>I presume this scoring scheme is produced in order to allow submission for
167
only one of the events, and/or to eliminate the possibility of contradictory
168
submissions for event 1 and event 2, from the same author?</b>
169
170
<p>
171
You are welcome to submit results for both events, but they must be separate
172
submissions.  Because of the nature of the events, it would be a poor strategy
173
to submit the same classifications in both cases, even if the autoscorer
174
permitted this.  In event 1, the goal is to minimize the number of
175
misclassified subjects in both groups, so it would be a mistake to mark one
176
record in each pair as `A' (unless you really believe that all 50 subjects
177
belong to group A; as stated above, however, there are between 20 and 30
178
subjects in group A).
179
180
<p>
181
In event 2, the goal is to minimize the number of misclassified records in
182
group A only.  In this event, it would be a mistake to omit classifying one
183
record in any pair as `A', because if that pair turned out to belong to group
184
A, you would forfeit the opportunity to score a point for that pair.
185
186
<p>
187
The submission formats for the two events were deliberately designed to be
188
different.  This makes it easy for the autoscorer to recognize a result
189
submitted to the wrong event in error, so that such a case doesn't get counted
190
against your quota of submissions.
191
192
<p>
193
<b>Still, one can have a high score on one event and a poor score on the
194
other. How do you treat this?</b>
195
196
<p>
197
The two events are really addressing rather different questions, using the same
198
data set.  (This, in a nutshell, is one of the principal <em>raisons
199
d'Ítre</em> for PhysioNet: to make it possible for data to be used to address
200
more than one question!)  We will award US$500 to the winner of event 1, and
201
US$500 to the winner of event 2.  If you win both events, you will receive
202
US$1000.
203
204
<p>
205
<b>Who is eligible to win an award?</b>
206
207
<p>
208
To be eligible for an award, you must enter the competition
209
officially (by submitting at least one set of results for scoring, and an
210
abstract describing your work to Computers in Cardiology 2001, no later than
211
the abstract deadline of 1 May 2001).  You may submit revised results at
212
any time until noon GMT on 21 September 2001.  At that time, the winners
213
will be determined based on the highest scores received by official entrants.
214
The date and time of the submission will be used as a tiebreaker if necessary.
215
216
<p>
217
Submissions from members and affiliates of our research groups at MIT, Boston
218
University, Harvard Medical School, Beth Israel Deaconess Medical Center, and
219
McGill University are not eligible for awards, although all are welcome to
220
participate.
221
222
<p>
223
If you have missed the deadline for submitting an abstract to Computers in
224
Cardiology 2001, we still encourage you to participate unofficially.  If you
225
receive a high score, your achievement will be recognized on this web site.
226
If you are able to attend Computers in Cardiology, you will have an opportunity
227
to discuss your work informally with other participants during a workshop
228
session.
229
230
<p>
231
<b>Would it be possible to submit my classification result and ask for
232
scoring during the weekend?  How long will it take for scoring?</b>
233
234
<p>
235
The scoring is performed automatically -- just follow the instructions
236
above for submitting your results.  Your score is sent to you by return email
237
immediately.
238
239
<p>
240
If your results are not properly formatted, you will receive an email reply
241
that will indicate this; if this happens, please review the instructions
242
carefully and try again.  Your friendly challenge organizer reads his
243
<a href="mailto:webmaster@physionet.org?subject=CinC Challenge 2001 Help!">
244
email</a> frequently (on the weekends, too), especially as the critical
245
deadlines approach, and promises to answer your questions quickly if you get
246
stuck!
247
248
<p>
249
<b>If I would like to submit more than one result for an event, should I
250
use the same file name for each submission of the text file (the default
251
names are template-test-1.txt for event 1 and template-test-2.txt for event
252
2)?</b>
253
254
<p>
255
This doesn't matter (your submission is archived using a file name
256
constructed from the date, time, and your email address).
257
258
<p>
259
<b>About the result template for event 1 (PAF risk assessment), there are
260
only odd-numbered records in the template.  What should I do if the
261
classification results for the two records in a pair are different?
262
Should I just write down the results for the odd-numbered records, or can I
263
choose the more reliable one from each pair of records?</b>
264
265
<p>
266
Definitely, you should choose whatever classification you consider to be more
267
reliable, provided that you are using objective criteria for making the choice.
268
Each pair of records comes from one subject, so for purposes of event 1 the
269
correct classification is by definition the same for both records in the pair:
270
either the subject has PAF (`A') or not (`N').  Please keep in mind that the
271
classifications must be determined by an algorithm, not manually, so if your
272
algorithm produces a confidence level, for example, and you choose the
273
classification with the higher confidence level each time, this is acceptable
274
(your decision is algorithmically determined); but it would not be acceptable
275
for you to decide on subjective grounds which classification to use in each
276
case.
277
278
<p>
279
<b>According to the instructions for abstract submission, I should give the
280
result of my algorithm.  Does that mean the scoring result?  So I have to
281
get the scores first before I can submit the abstract, right?</b>
282
283
<p>
284
This is correct: your abstract should include your score.  You should consider
285
this score to represent preliminary results; your abstract will be judged on
286
the basis of the ideas you discuss and not on the score itself (although a good
287
score might help a marginal abstract, a poor score will not rule out a good
288
abstract).  You may submit revised results for scoring before or after the
289
abstract deadline, at any time until noon GMT on 21 September 2001.  Your best
290
results determine your standing in the competition.  In your finished
291
manuscript (which is not due until 25 September 2001) you should include your
292
best results and describe what changes, if any, you made in order to improve
293
your initial results.
294
295
<hr>
296
297
<!--#include virtual="/footer.shtml" -->
298
</body>
299
</html>