[gconstruct] Multi-column features should save indpendent transformation for each column
Open
- Dominant language
- Python
- Stars
- 452
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Currently GConstruct saves a single transformation in the output gcon config even when the input has multiple columns.
We should be saving one transformation per column and apply them individually (e.g. min-max needs per-column min and max value to be re-applied, as GSProcessing does)
Contributor guide
Research direction
Start by locating gconstruct's handling of transformations and the output gcon configuration, then compare the per-column min-max behavior described for GSProcessing. Done means each input column has its own saved transformation parameters and those parameters are applied independently when reused.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100