TRACER
  • Introduction
  • Manual
    • About the manual
    • Introduction
      • Text Reuse
      • TRACER overview
    • System prerequisites
    • Download and installation
    • Corpus preparation
    • PoS-tagging, lemmatisation & WordNets
    • Configuration
      • Step 1. Preprocessing
      • Step 2. Featuring/Training
      • Step 3. Selection
      • Step 4. Linking
      • Step 5. Scoring
    • Execution of TRACER
    • Postprocessing
    • Results & computed files
    • Keeping a detection logbook
    • Limitations
    • References
  • Beta
    • Visualising results in a tabular format
    • BabelNet API
    • Text preprocessing automation
  • Support
    • Troubleshooting
      • Unable to parse date
      • Unable to access jarfile
      • Empty score and link files
      • Java lang no class definition found
      • Out of memory
      • Out of bounds exception
      • Windows: length of folder name
      • Windows: PowerShell
    • FAQ
    • Publications
    • Resources
    • Command line: MAC vs. Windows
Powered by GitBook
On this page
  1. Support
  2. Troubleshooting

Windows: length of folder name

PreviousOut of bounds exceptionNextWindows: PowerShell

Last updated 7 years ago

CtrlK

When running TRACER on a Windows machine, the length of the folder names generated by TRACER within TRACER_DATA after a detection task might break the text reuse visualization. This means that the index.html file in the TRAViz postprocessing folder, although correctly computed, will display a blank or an error page in the browser. To fix the issue, rename all folders nested in TRACER_DATA to something shorter (e.g. 1, 2, 3, 4, 5, 6). Once all folders are renamed, the index.html file can be reopened and the text reuse visualization will load in the browser.