You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 thescore()
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.The text was updated successfully, but these errors were encountered: