Messed up settings of select columns
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.7k
- Forks
- 1.1k
- Avg merge
- 12d 2h
- Merged PRs (30d)
- 1
Description
What's wrong?
I use orange with large datasets (~40000 rows, 300features 9 metas/~60MB size), mostly without addons. For the last verisons 3.38 including it happens frequently that all settings for select columns are gone and messed up. select colums is combined also with select rows for filtering.
The colnames are grouped by source of parametes. Process1_temp, Process2_temp
I use the select fields to group in different analysis path (5-6 parallel at the same time).
When problem occurs setup is completly wrong, parameters that are configured for the path are gone and others are inside.
I have to renew this on regular base.
In the background everything is set to automatic mode. The analysis behind is also completely messed because of wrong selections.
VAR_A1 +
VAR_A2 | --- select columns "All VAR_A" --> Analysis
VAR_A3 +
VAR_B1 +
VAR_B1+
VAR_C1+
VAR_C2 |--- select colums "All VAR_B" --> Analysis
VAR_C3+
complete VAR_A set is changed vs. VAR_C set,VAR_B1, selected for both path is completly gone.
There's no error messages, after change back everything works fine again for a certain time. I named the visuals to be sure I selected the right ones, and there's no fault on configuration. Variables VARA, B, ... are the same, occacsionally new ones are added for new approaches, normally always at the end of the columns.
How can we reproduce the problem?
Take a large dataset, configure columns and rows to filter and just open and close the model several times.
What's your environment?
- Operating system:
- Orange version:
- How you installed Orange:
Windows 11, portable version, problem occured already under WIN 10 installed and portable version.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the problem with a large dataset using the Select Columns and Select Rows widgets, then repeatedly open and close the model as described. Compare the configured selections after each cycle; done means the column and row settings remain associated with the correct analysis paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100