Differences between revisions 1 and 17 (spanning 16 versions)

Results for Exercise Sheet 5 (Approximate Word Matching)

Please read the instructions below, before adding something to the table!

Add your row to the table below, following the examples already there. Column 2 = construction time for your k-gram index in seconds (with exactly one digit after the dot). Column 3 = average query time in milliseconds (rounded to the next integer). Column 4 = average time (over all queries) for one edit distance computation in microseconds (with exactly one digit after the dot). Column 5 = average number of matches per query (rounded to the next integer). Column 6 = machine specification as usual (processor frequency with exactly one digit after the dot, amount of RAM as an integer, no secondary details about processor). Column 7 = programming language (Java or C++).

Name	Constr. time	Query time	ED time	Matches / query	Processor / RAM	Language
Florian B	0.7s	6ms	1.2µs	28	Intel X5560 @ 2.8GHz / 36GB	Java
Simon P	1.8s	2666ms	??µs	1	Intel i3 @ 1.3GHz / 4GB	Java
Anton S	0.5s	16ms	130µs	28	VM: i5 3570K @ 3.4GHz / 5GB	C++

-  ⇤ ← Revision 1 as of 2012-11-21 07:37:45 → 
  Size: 981
  Editor: Hannah Bast
  Comment:
+   ← Revision 17 as of 2012-11-23 21:35:31 → ⇥
  Size: 1217
  Editor: HSI-KBW-046-005-180-074
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 5:
-Add your row to the table below, following the examples already there. Column 2 = construction time for your k-gram index in seconds (rounded to the next integer). Column 3 = average query time in milliseconds (rounded to the next integer). Column 4 = average time (over all queries) for one edit distance computation in microsecond (rounded to the next integer). Column 5 = machine specification as usual (processor frequency with exactly one digit after the dot, amount of RAM as an integer, no secondary details about processor). Column 6 = programming language (Java or C++).
+Add your row to the table below, following the examples already there. Column 2 = construction time for your k-gram index in seconds (with exactly one digit after the dot). Column 3 = average query time in milliseconds (rounded to the next integer). Column 4 = average time (over all queries) for one edit distance computation in microseconds (with exactly one digit after the dot). Column 5 = average number of matches per query (rounded to the next integer). Column 6 = machine specification as usual (processor frequency with exactly one digit after the dot, amount of RAM as an integer, no secondary details about processor). Column 7 = programming language (Java or C++).
 Line 7:
-||<tablewidth="1066px" tableheight="1290px">'''Name''' ||'''Constr. time''' ||'''query time''' ||'''ED time''' ||'''Processor / RAM''' ||'''Language''' ||
||Florian B ||???s ||???ms ||??µs ||Intel X5560 @ 2.8GHz / 36GB ||Java ||
+||'''Name''' ||'''Constr. time''' ||'''Query time''' ||'''ED time''' ||'''Matches / query''' ||'''Processor / RAM''' ||'''Language''' ||
||Florian B ||0.7s ||6ms ||1.2µs ||28 ||Intel X5560 @ 2.8GHz / 36GB ||Java ||
||Simon P ||1.8s ||2666ms ||??µs ||1 ||Intel i3 @ 1.3GHz / 4GB ||Java ||
||Anton S ||0.5s ||16ms ||130µs ||28 ||VM: i5 3570K @ 3.4GHz / 5GB ||C++ ||