FireDynamics / FireDynamics/propti
Restructure scaling in fitness computation
- Dominant language
- Python
- Stars
- 17
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
The current implementation is not robust. sclae_fitness can be a bool or a string, yet without checking for non-valid values. minmax scaling is using the first and last value, instead of min and max value?
Additionally, a common scaling approach should be investigated.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points; begin by locating sclae_fitness and its callers, then inspect how fitness values are scaled. Check the accepted bool and string values and whether minmax scaling uses the actual minimum and maximum. Done means invalid values are handled, scaling behavior is verified, and any additional common scaling approach is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100