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

multiple objective functions for configuration files #115

Closed
mheilman opened this issue May 13, 2014 · 6 comments
Closed

multiple objective functions for configuration files #115

mheilman opened this issue May 13, 2014 · 6 comments

Comments

@mheilman
Copy link
Contributor

It would be nice to allow configuration files that specify "objective" as a list (rather than just string values). Right now, I believe that it is the case that if people want to run the same experiment with a different objective, they have to make two copies of the config file.

@dan-blanchard
Copy link
Contributor

Am I imagining that someone wrote a script to generate objectives after the fact?

@mheilman
Copy link
Contributor Author

Right, there's this: https://github.com/EducationalTestingService/skll/blob/develop/skll/utilities/compute_eval_from_predictions.py

Chong Min (does he have a GitHub acct?) asked me about this, and I was thinking that he wanted to specify the objective so it could be used for tuning rather than just for evaluation, but perhaps that script would suffice. I'll follow up with him, but I'll leave this open because I think it might be useful to be able to specify multiple tuning options at once, though it seems a bit of an obscure use case.

@dan-blanchard dan-blanchard added this to the 1.0 milestone Jun 5, 2014
@dan-blanchard
Copy link
Contributor

@mheilman Do we really want this for 1.0 or can I leave the milestone unspecified for this one?

@mheilman
Copy link
Contributor Author

I don't think we need this for 1.0. It'd be nice to have, but it's not super important and won't really affect the API.

@dan-blanchard dan-blanchard removed this from the 1.0 milestone Oct 20, 2014
@dan-blanchard
Copy link
Contributor

That's what I thought too. One step closer to 1.0 then. 🍻

@dan-blanchard dan-blanchard added this to the 1.1 milestone Nov 11, 2014
@desilinguist desilinguist modified the milestones: 1.1, 1.2 Jul 18, 2015
@desilinguist desilinguist assigned ghost Feb 8, 2016
@desilinguist
Copy link
Member

Addressed by #291.

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

3 participants