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

Features and resources correspondence #35

Open
varvara-l opened this issue Aug 17, 2015 · 0 comments
Open

Features and resources correspondence #35

varvara-l opened this issue Aug 17, 2015 · 0 comments

Comments

@varvara-l
Copy link
Collaborator

There are two sub-problems:

  • all the text representations are generated regardless of set of features I need (e.g. I might not need POS tags but the input is POS-tagged anyway).
  • there is no information about which resources does a feature require.

I suggest:

  • writing a description for each feature stating which resources it needs
  • not extracting the information which is not needed for the set of features extracted (btw thus we can avoid the featureConfig variable. It now has 'bb', 'gb' and 'all' modes and extracts the information needed for all black-box features or all glass-box features or both). I don't know how exactly this is implemented in QuEst, but it shouldn't be difficult to change.
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