Useless files created when running BertQA.predict()
See original GitHub issueWhen we run the predict()
method of BertQA
, two files are also created in the repository where we run the code:
nbest_predictions.json
: An empty json filepredictions.json
: a json file with predictions for the paragraphs in the squad-like dictionary fed as input topredict()
I suggest to take out the creation of these files as they are useless. Or maybe create a boolean parameter to keep the option to save predictions.json
, but keep it as False
by default.
Issue Analytics
- State:
- Created 4 years ago
- Comments:13
Top Results From Across the Web
Detecting Protagonists and Title Figures in Plays - QuaDramA
You can create it anywhere ( $YOUR_PATH/data ) and then set up R to run commands in the parent directory with setwd($YOUR_PATH) ....
Read more >Prediction of Disaster using Bert Model
First, we choose the pre-trained model: in the BERT GitHub repository there are several choices available, we will use uncased_L-12_H-768_A-12 .
Read more >Press
Security researchers have designed a new way to detect brand impersonation using Siamese Neural Networks, which can learn and make predictions based on ......
Read more >Berla, Nancy, Ed. TITLE A New Generation of Evidence - ERIC
ABSTRACT. This report covers 66 studies, reviews, reports, analyses, and books. Of these 39 are new; 27 have been carried over from previous...
Read more >GAVO DaCHS Tutorial - VO related docs
Indices are usually generated after a full import. If you add or change indices later, run dachs imp -I, which will re-make all...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I agree.
Yes, I think it is a good solution for this issue