Closed GoogleCodeExporter closed 9 years ago
Typical errors in formatting are as follows:
The truth state of every case must be defined once and only once.
ERROR: Truth states not defined for all the cases.
ERROR: Truth states multiply defined.
The row containing "BEGIN DATA:" must be typed exactly as given.
ERROR: "BEGIN DATA:" not all upper-case.
ERROR: "BEGIN DATA:" not terminated with a colon.
Commas with no spaces must be used to separate the four fields of data
describing each ROC rating.
ERROR: Spaces, tabs, or semicolons separate the data in the list of ROC ratings. Only commas should be used.
Original comment by Brandon.Gallas
on 31 Jan 2014 at 9:42
Original comment by Brandon.Gallas
on 31 Jan 2014 at 10:08
Original comment by Brandon.Gallas
on 1 Feb 2014 at 1:26
[deleted comment]
Original comment by mike.mik...@gmail.com
on 6 Feb 2014 at 3:22
Original comment by Brandon.Gallas
on 10 Feb 2014 at 3:15
I have come across a new error. When reading the header information, there are
four important rows that might be encountered that may or may not be present.
They are identified as
N0:
N1:
NR:
NM:
If something is wrong with the formatting of these rows, there is no error. The
file input just fails silently.
Original comment by Brandon.Gallas
on 2 Mar 2014 at 9:17
Made a lot of progress by adding data checks with pop-up button windows for
error reporting. You can realize many errors by using "Input Raw Data" method
and browsing to the files in "imrmc/000related/FilesTest". The error reporting
is crude and should be improved. For one thing, it should stop the current
processes and reset iMRMC (the equivalent of hitting the reset button in
GUIInterface).
The data checks and error reporting that I wrote can be found in
mrmc.InputFile.verifySizesAndGetIDs
mrmc.InputFile.processScoresAndTruth
Original comment by Brandon.Gallas
on 3 Mar 2014 at 8:19
Issue 8 has been merged into this issue.
Original comment by Brandon.Gallas
on 3 Mar 2014 at 8:20
I believe that this issue is fixed.
Original comment by Brandon.Gallas
on 5 Mar 2014 at 9:40
Original issue reported on code.google.com by
Brandon.Gallas
on 31 Jan 2014 at 9:40Attachments: