-
Notifications
You must be signed in to change notification settings - Fork 49
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
Is there a way to access individual model errors? #54
Comments
hey, @mmarsman1 and i have been discussing this, and i think we're going to transition to calling so perhaps it would be simpler if |
Well, lmBF in turn calls one of many functions, depending on the kind of model involved. I think you'll have the same issue one level deeper. I'll have a think about this. |
yup, so i gather you catch and handle errors in these underlying functions so that if one model fails, all the other models in the analysis continue to run. wouldn't this be best if error handling happened at the level of this way you achieve the same functionality, but allow people who call of course, my reading of how this all works might be neive. |
I'll see what I can do. |
cheers |
Hi,
When we run multiple models, some of them can fail. An error is produces at the console, but we would like to have access to this information as well. Take the following code for example:
It produces some NaN BFs, but we would like to provide explanations to the user why these models failed. Is there a way to access this? if not, could these errors be added to the individual BF objects?
with thanks
The text was updated successfully, but these errors were encountered: