Override a variable if user wants to override one of variables in both FLOPS and GASP geometry are present
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
Note from Ken: Given code_origin_overrides a list of aviary variables names to prioritize when GASP and FLOPS both compute it, what do we need to do if user wants to override one of these? Right now, this scenario is ignored. See note #1176 in override_aviary_vars() of variable_info/functions.py.
Suggested implementation.
No response
Contributor guide
No contributing guide indexed for this repository
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 in variable_info/functions.py at the note in override_aviary_vars(). Trace how code_origin_overrides handles Aviary variables computed by both GASP and FLOPS, then identify how a user-provided override should interact with that selection. Done means the previously ignored scenario has defined behavior and is covered by the relevant existing checks or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100