-
Notifications
You must be signed in to change notification settings - Fork 20
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
Bad No-Metric Error #60
Comments
So I think I should just change this (line 36, cymetric/execution.py):
to say something else? I'm not sure what. "cannot be found"? |
there is probably somewhere higher up that tries to do something like On Wed, May 6, 2015 at 4:49 PM, opotowsky [email protected] wrote:
Matthew Gidden, Ph.D. |
So in evaluator.py there is:
Should I do the try/except clause around line 45? |
The short answer is: you can try it and find out using the same example in On Wed, May 6, 2015 at 5:30 PM, opotowsky [email protected] wrote:
Matthew Gidden, Ph.D. |
Gotcha! Thanks. I'll try it out :-) |
Tried a number of ways with no luck, moving to 1.5 |
This is non intuitive
Perhaps some logic could be added to catch a bad metric and print something more graceful.
The text was updated successfully, but these errors were encountered: