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

Make eval.py debuggable #25

Open
sampsyo opened this issue Jul 17, 2014 · 1 comment
Open

Make eval.py debuggable #25

sampsyo opened this issue Jul 17, 2014 · 1 comment

Comments

@sampsyo
Copy link
Member

sampsyo commented Jul 17, 2014

At the moment, it's really hard to develop/debug your eval.py. There's no way to run it outside of the full experiment workflow.

To make this better, I think we should get rid of the load() function. More often than not, I tend to use the file-sequestration mechanism anyway; we can just let the programmer specify the file to sequester in the Makefile. Then the score() function will always be passed two filenames. No need to worry about file size.

This will let us build a command that quickly invokes score() on two arbitrary files, or on the stored precise file and a specified relaxed file, for debugging eval.py.

@sampsyo
Copy link
Member Author

sampsyo commented Feb 10, 2015

For now you can make eval.py invokable by adding something like this at the bottom of the file:

if __name__ == '__main__':
    import sys
    score(sys.argv[1], sys.argv[2])

Then invoke it with python eval.py file1 file2.

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

1 participant