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

Deepdive data not found for a column #668

Open
MahmoudYounes opened this issue May 6, 2018 · 1 comment
Open

Deepdive data not found for a column #668

MahmoudYounes opened this issue May 6, 2018 · 1 comment

Comments

@MahmoudYounes
Copy link

I have been struggling with deepdive for about a week now, can't get the spouse example to work. I am using ubuntu 16.04 LTS, deepdive v0.8.0-79-g28a58de (Linux x86_64)
first of all I find 2 different tutorials for the same objective (running the spouse relation extraction example). I followed the one on the web site up to the point of spouse_features and then all I keep getting is data not found for column p2_id and all processes are not found to be killed. googling this issue revealed that deepdive is not robust to some characters like \t, for example, if a column has only \t character in it this is fail the system.
so here are my questions, how can I know which column and which data entries creating this error?

also, is deepdive still under development? or is it abandoned?

@MahmoudYounes
Copy link
Author

MahmoudYounes commented May 8, 2018

for those who will struggle much like I did. I will explain how to debug this problem. this problem can be caused by multiple sources of errors. you are going to have to find from the log generated in the console which process caused the failure and what is the status code returned by this process. google the status code to know exactly what is the issue, then head to this script and use a couple of echos or prints (depends whether you are in bash or python script) to find out which line causing this error, then figure out your way around it.
note though: try to redirect the outputs of your scripts to a file instead of stdout or stderr because your debug statements might not be captured. this issue is solved

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

1 participant