Closed mmoramarco closed 1 year ago
This behaviour is not unexpected, because in the documentation we say precisely that required formats are data.frame and matrix. Nevertheless i will add casting to the data.frame from tibble in the next version. This transformation won't have any negative impact on the performance of the package.
I attempted to test the forester package on the concrete dataset from the modeldata package (I wanted to mirror some of the tutorials/models from the tidymodels book).
I believe the issue is the tibble format itself when passed into the following chunk of pre_rm_static_cols
This function, when acted on a tibble returns a tibble with one column resulting in a length one (thus that column is marked for removal).
If the tibble is coerced to a data frame first. The subset returns a vector which then has a length of 278 is that column is not marked for deletion.
I'm not sure if there is a larger effect of coercing a tibble into a traditional data.frame before processing but that seems to resolve the issue.