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
According to the paper, the smell is described as follows:
Problem
If the columns are not selected explicitly, it is not easy for developers to know what to expect in the downstream data schema. If the datatype is not set explicitly, it may silently continue the next step even though the input is unexpected, which may cause errors later. The same applies to other data importing scenarios.
Solution
It is recommended to set the columns and DataType explicitly in data processing.
Hello!
I found an AI-Specific Code smell in your project.
The smell is called: Columns and DataType Not Explicitly Set
You can find more information about it in this paper: https://dl.acm.org/doi/abs/10.1145/3522664.3528620.
According to the paper, the smell is described as follows:
Example:
You can find the code related to this smell in this link:
alibi/alibi/utils/data.py
Lines 51 to 71 in e458ab3
I also found instances of this smell in other files, such as:
File: https://github.com/SeldonIO/alibi/blob/master/alibi/datasets/default.py#L249-L259 Line: 254
File: https://github.com/SeldonIO/alibi/blob/master/alibi/explainers/ale.py#L519-L529 Line: 524
File: https://github.com/SeldonIO/alibi/blob/master/alibi/explainers/backends/cfrl_tabular.py#L869-L879 Line: 874
.
I hope this information is helpful!
The text was updated successfully, but these errors were encountered: