More Descriptive Error Messages
elykwilliams opened this issue · comments
Currently the error messages provide usefull debuging info, but do not provide useful feedback to the user about what is going wrong.
For example, if dt is too big, the user is likely to see a MaxRecursionDepth error with information about the state change. Instead of printing out all the state change info, we should printout reasons why this error might have occurred (barring some sort of internal error), and provide an debug() function that will output the current statue change info.