Text REtrieval Conference (TREC)
System Description

Organization Name: Dublin City University Run ID: DCU97QSDR-B2
Section 1.0 System Summary and Timing
Section 1.1 System Information
Hardware Model Used for TREC Experiment: UltraSparc
System Use: SHARED
Total Amount of Hard Disk Storage: 20 Gb
Total Amount of RAM: 96 MB
Clock Rate of CPU: ? MHz
Section 1.2 System Comparisons
Amount of developmental "Software Engineering": SOME
List of features that are not present in the system, but would have been beneficial to have:
List of features that are present in the system, and impacted its performance, but are not detailed within this form:
Section 2.0 Construction of Indices, Knowledge Bases, and Other Data Structures
Length of the stopword list: words
Type of Stemming: NONE
Controlled Vocabulary: NO
Term weighting: YES
  • Additional Comments on term weighting: tf * IDF
Phrase discovery: NO
  • Kind of phrase: non stopword pair/triple
  • Method used: OTHER
Type of Spelling Correction: NONE
Manually-Indexed Terms: NO
Proper Noun Identification: NO
Syntactic Parsing: NO
Tokenizer: NO
Word Sense Disambiguation: NO
Other technique: NO
Additional comments: Used document texts as input to a phemic dictionary lookup and indexed texts by tri-phones, triples of phones. Documents divided into windows of 120 triphones with 40 triphone overlap. Used BBaseline texts. A similar process was used for indexing topics
Section 3.0 Statistics on Data Structures Built from TREC Text
Section 3.1 First Data Structure
Structure Type: NONE
Type of other data structure used:
Brief description of method using other data structure:
Total storage used: Gb
Total computer time to build: hours
Automatic process: YES
Manual hours required: hours
Type of manual labor: NONE
Term positions used: NO
Only single terms used: NO
Concepts (vs. single terms) represented: NO
  • Number of concepts represented:
Type of representation:
Auxilary files used: NO
  • Type of auxilary files used:
Additional comments:
Section 3.2 Second Data Structure
Structure Type: NONE
Type of other data structure used:
Brief description of method using other data structure:
Total storage used: Gb
Total computer time to build: hours
Automatic process:
Manual hours required: hours
Type of manual labor: NONE
Term positions used:
Only single terms used:
Concepts (vs. single terms) represented:
  • Number of concepts represented:
Type of representation:
Auxilary files used:
  • Type of auxilary files used:
Additional comments:
Section 3.3 Third Data Structure
Structure Type: NONE
Type of other data structure used:
Brief description of method using other data structure:
Total storage used: Gb
Total computer time to build: hours
Automatic process:
Manual hours required: hours
Type of manual labor: NONE
Term positions used:
Only single terms used:
Concepts (vs. single terms) represented:
  • Number of concepts represented:
Type of representation:
Auxilary files used:
  • Type of auxilary files used:
Additional comments:
Section 4.0 Data Built from Sources Other than the Input Text
Internally-built Auxiliary File

File type: OTHER
Domain type: DOMAIN INDEPENDENT
Total Storage: .1 Gb
Number of Concepts Represented: na concepts
Type of representation: NONE
Automatic or Manual:
  • Total Time to Build: hours
  • Total Time to Modify (if already built): hours
Type of Manual Labor used: NONE
Additional comments: Manual
Externally-built Auxiliary File

File is:
Total Storage: Gb
Number of Concepts Represented: concepts
Type of representation:
Additional comments:
Section 5.0 Computer Searching
Average computer time to search (per query): CPU seconds
Times broken down by component(s):
Section 5.1 Searching Methods
Vector space model:
Probabilistic model:
Cluster searching:
N-gram matching:
Boolean matching:
Fuzzy logic:
Free text scanning:
Neural networks:
Conceptual graphic matching:
Other:
Additional comments:
Section 5.2 Factors in Ranking
Term frequency:
Inverse document frequency:
Other term weights:
Semantic closeness:
Position in document:
Syntactic clues:
Proximity of terms:
Information theoretic weights:
Document length:
Percentage of query terms which match:
N-gram frequency:
Word specificity:
Word sense frequency:
Cluster distance:
Other:
Additional comments:
Send questions to trec@nist.gov

Disclaimer: Contents of this online document are not necessarily the official views of, nor endorsed by the U.S. Government, the Department of Commerce, or NIST.