Metavariables are not excluded in feature selection methods

[lareooreal]

A longstanding issue is that metavariables are not excluded from methods. For example, in "find informative projections" for scatter plots, they appear as suggestions. Also, in feature suggestions, the metas are included. If there are many, the automatic feature selection breaks down. This is a nuisance, as metas often contain the solution to a classification problem. "Find informative mosaics" has the same issue, as does the violin plot where ordering by relevance also includes metas. Tree prediction does ignore them, though.

I am currently using version 338 on a Mac, and this error is present in the PC version as well.

This issue has existed in every version of Orange that I can recall.

Best larerooreal

[markotoplak]

Now visualization scoring (VizRank) uses all features that a user can choose manually.

But I do agree: in some cases you'll there can be lots of combinations that we are surely not interested in, and having some optional filtering would be nice.

I remember the development team discussing this long ago. I am not quite sure, but I think we used to have the opposite problem: metas were ignored even when we wanted to have them considered.

[lareooreal]

Selecting metadata for visualization is useful, but having them permuted in the model suggestions is not good! Metadata should remain as metadata, serving solely for interpretation purposes. This includes decorating plots with colors, labels, and annotations. Relevant predictors should be included in the X-block. It might be worth considering placing variables either in the X-block or in the metadata bucket. This approach would allow any variable to be used for modeling or proposing features, or for decorative purposes. Am Do., 30. Jan. 2025 um 14:57 Uhr schrieb Marko Toplak < ***@***.***>:

…

Now visualization scoring (VizRank) uses all features that a user can choose manually. But I do agree: in some cases you'll there can be lots of combinations that we are surely not interested in, and having some optional filtering would be nice. I remember the development team discussing this long ago. I am not quite sure, but I think we used to have the opposite problem: metas were ignored even when we wanted to have them considered. — Reply to this email directly, view it on GitHub <#7009 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM5BQGHFIINBU6H3DWTFXLL2NIVUDAVCNFSM6AAAAABWFH4KGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRUGU4DQNBUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>