# Visualising results in a tabular format

The `.score` files produced by TRACER can be transformed into a more human-readable format with a script that prints the corresponding text segment next to the reuse ID, as well as the number of overlapping features and the percentage of similarity. In the terminal, navigate to the TRACER main folder and type:

```
java -cp tracer.jar eu.etrap.tracer.postprocessing.DefaultOutputterMain /.../filename.txt /.../filename.score
```

Where:

* `/.../filename.txt` is the path to the main text file;
* `/.../filename.score` is the score file.

The generated file, accessible from `/data/corpora/myfolder/`, has `.expanded` as its suffix (i.e., `filename.score.expanded`) and contains four columns separated by tabs:

`RUID 1, RUID 2, FEATUREOVERLAP, SIMTHRESHOLD, TEXT 1, TEXT 2`

This `.txt` output can be duplicated and imported into a `.csv` file for the gold standard analysis


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://tracer.gitbook.io/manual/beta/results-as-csv.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.