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

Paths when running training #57

Closed
bbieniek opened this issue Jun 1, 2021 · 3 comments
Closed

Paths when running training #57

bbieniek opened this issue Jun 1, 2021 · 3 comments

Comments

@bbieniek
Copy link
Contributor

bbieniek commented Jun 1, 2021

Hi,

While running training via run_bilstmcrf.py I ran it the following way:
Installed deidentify via pip
Checked out the code from github to have run_bilstmcrf.py

When running the run_bilstmcrf.py script, this resulted in issues with the paths for the training set as the scripts use base path in most cases.

Is this the correct way of running the training?

@jantrienes
Copy link
Collaborator

Hi @bbieniek,

thanks for reaching out. The recommended way to train a model with the run_bilstmcrf.py script is to 1) clone the repo, 2) create the virtual environment (see here), and 3) train the model according to these steps. No pip install is needed in this case, because you are working from the sources itself.

When running the run_bilstmcrf.py script, this resulted in issues with the paths for the training set as the scripts use base path in most cases.

All scripts assume that the training data resides in data/corpus/. Could you perhaps share the specific error you received? That would make it easier to analyze the problem. Thank you.

Best,
Jan

@jantrienes
Copy link
Collaborator

I'm closing this for now. Please let me know if you have additional questions.

@bbieniek
Copy link
Contributor Author

bbieniek commented Jul 2, 2021

Thanks Jan for your response. That helped!

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