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

save results #99

Closed
zseder opened this issue Jun 13, 2014 · 3 comments
Closed

save results #99

zseder opened this issue Jun 13, 2014 · 3 comments

Comments

@zseder
Copy link
Collaborator

zseder commented Jun 13, 2014

We should create some abstract methods into OfflineParser and/or OnlineParser that supports parser running and result saving with pickle to be easily loaded what there is possibly no change in order to be faster
There is a solution for this in dbpedia parsers, parse_and_save(), read_results(), and parse(). Maybe these are okay, but a base class should implement this.

@kornai @pajkossy @juditacs @makrai @zseder

@juditacs
Copy link
Collaborator

Have we agreed on a data structure for all parser outputs? I mean the dictionaries should have a unified name such as language_data and the keys of the dictionaries should match if they have the same type of value(s). If we standardize the parsers, it will be easy to implement such methods in the base classes.

@zseder
Copy link
Collaborator Author

zseder commented Jun 16, 2014

They are standardized dictionaries right now. All the parsers are changed during integration to yield key-value pairs that are in sync with db.

@zseder
Copy link
Collaborator Author

zseder commented Jun 17, 2014

solved in #100

@zseder zseder closed this as completed Jun 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants