Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make stdin and stdout available for prediction #49

Open
massongit opened this issue Nov 28, 2017 · 2 comments
Open

Make stdin and stdout available for prediction #49

massongit opened this issue Nov 28, 2017 · 2 comments

Comments

@massongit
Copy link
Contributor

massongit commented Nov 28, 2017

When we predict named entity tags using named entity tagger such as CRF ++, KyTea and KNP, stdin and stdout are used for inputting target data and outputting prediction results.
Therefore, it seems to be good to make stdin and stdout available for inputting target data and outputting prediction results when we predict those.

@aonotas
Copy link
Owner

aonotas commented Dec 2, 2017

You mean we should use logging for prediction?

@massongit
Copy link
Contributor Author

massongit commented Dec 3, 2017

The current prediction command is as follows:

$ deep-crf predict input_raw_file.txt --delimiter=' ' --model_filename ./save_model_dir/bilstm-cnn-crf_adam_epoch3.model --save_dir save_model_dir --save_name bilstm-cnn-crf_adam  --predicted_output predicted.txt

I think it would be better to be able to also use the following command:

$ deep-crf predict --delimiter=' ' --model_filename ./save_model_dir/bilstm-cnn-crf_adam_epoch3.model --save_dir save_model_dir --save_name bilstm-cnn-crf_adam < input_raw_file.txt > predicted.txt

FYI: Prediction command of KyTea:

kytea -model trained_model.model < input_raw_file.txt > predicted.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants