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
Right now it is possible to switch on/off the rejection of variables entirely with the configuration-variable reject_variables.
Proposed feature
I would like to be able to only reject some type of variable. For example reject missing variables, but still show constant variables normally in the report.
Alternatives considered
I'm not sure about a workaround, to me it seems like it depends on the Typeset as they all come back to the unsupported Basetype-
Additional context
No response
The text was updated successfully, but these errors were encountered:
We use the reports to have a first glance at unknown data sets.
A column that consists only of NA-values is indeed not that interesting.
For a constant column on the other hand, it could still be interessting to check if that constant value is plausible.
But eventually they both get grayed out in the report as rejected, which tempts you to not look into them at all.
If it's not a feature worth pursuing for you, could you give me an idea where I have to look into it?
Where does the rejection happen? I already looked in the ./ydata_profiling/model/alerts.py and ./model/pandas/summary_pandas.py where I found out it depends on the description["type"] of a series_description being "Unsupported" or not.
Missing functionality
Right now it is possible to switch on/off the rejection of variables entirely with the configuration-variable reject_variables.
Proposed feature
I would like to be able to only reject some type of variable. For example reject missing variables, but still show constant variables normally in the report.
Alternatives considered
I'm not sure about a workaround, to me it seems like it depends on the Typeset as they all come back to the unsupported Basetype-
Additional context
No response
The text was updated successfully, but these errors were encountered: