new optional input (corpus weights) #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Specify optional argument --corpus-weights=filename.tsv to input the weights
The new optional input file should be in TSV format and better to have 2 columns. But it's ok for it to have more or fewer columns, if fewer, then the corpus weight will not be specify and set to 1.0, if more, then >2 columns will not be read.
It's also not necessary for each PubMed ID that occur in the "documents.tsv" to appear in this corpus weights file (not appear PubMed ID's corpus weight will be set to 1.0).
Fix the standard copy constructor of Document Class