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

Unable to parse date

PreviousTroubleshootingNextUnable to access jarfile

Last updated 7 years ago

CtrlK

This error is caused by the presence of a sequence of characters or absence of text in the second column of the corpus file. The term date is misleading and does not, in this case, indicate that the problem is with dating information (which can be added in the third column of the corpus file). The problem here is that TRACER does not provide information about the specific issue with the text, so the user has to check the corpus file in a text editor and correct anything that might seem incorrect or problematic. In order to fix this error, the user has to correct, save and re-run TRACER. If the error persists, then more corpus cleaning is needed.