-
Notifications
You must be signed in to change notification settings - Fork 94
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
Better error messages when target column dtype is not supported #1095
Comments
Hi @paxcema I can help with this. Kindly let me know if you are not working on this issue currently. |
Hey @Sumanth077 — I don't think there's anyone working on this at the moment, so your help would definitely be appreciated here. Let's discuss first, though. Do you have a rough idea on how to tackle this? I think we may need to store a map of mixers and their respective supported target data types, to then check whether the final JsonAI is capable of tackling the target |
Yes, I think you could start by adding the supported target data types for these as an attribute, maybe as an attribute in Then, when building either the code or the predictor itself out of a JsonAI object, we can check whether the target data type in the This way, we will raise an error at "model compilation" time so to speak, which is a valuable time saving. Does this sound good? |
Sure @paxcema that sounds good. Will look into that and let you know in case of any further clarification. |
Hi @paxcema I am commenting here since this conversation will give you a clear idea on my query. As you suggested I have made the changes to the base mixer ✅ And would be great to know how to approach in raising an Informative Error. You have mentioned we should raise an error when building either the code or the predictor itself out of a JsonAI object. But I guess the above error "Please specify a custom accuracy function for output type short_text." is raised when creating the Json AI object itself from Problem Definition from the "generate_json_ai" function So would be great to know
Thankyou. |
I think the error should be raised somewhere within the JsonAI creation process. I recommend creating a new method and call it from |
Motivated by an example where a
short_text
target column returns as error:The text was updated successfully, but these errors were encountered: