MedKhem
MedKhem
Hi! thank you for pointing this out. But it shouldn't represent an issue for the training :)
could you please upload the data of both cases on GitHub repo so I can have a look?
Please checkout the latest version and let me know if I can close this issue
ok. so this means the wrongly escaped line breaks is fixed ;) can you send me the corresponding pdf?
yeah. The fix was for issue #24 . Sorry for the confusion. Regarding this "issue", it's not actually an issue. In fact, for the annotation, the training files are not...
This shouldn't represent a noise for the training. Have you annotated the same files in two modes (pre-annotated and manually annotated) and you noticed that there is a difference in...
@gabays same question: do you have the same data annotated in the two modes, so I could use it to reproduce the problem?
@PonteIneptique @gabays the way how grobid is designed, the line breaks are not used as characters in the training. Only the text is used for the training and the line...
It depends on where you add them :) For the **lexical entry** level, if you add a new line between elements of lexical entry (e.g. \, \,..) that's fine. But...
no, I do use it :) but as I told you, this is done in a previous stage. We can not make a general conclusion about the performance of a...