potassco / potassco/constraint-handler
FCH transforms optimization criteria
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 20
Description
It seems that FCH always outputs a symbol in the optimization criterion of optimize_value/3 even if it should be a string or a number based on optimize_maximizeSum.
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 locating the implementation of optimize_value/3 and the handling of optimize_maximizeSum. Trace how the optimization criterion is converted and inspect the existing tests for this path. Done means the output preserves the expected string or number type instead of always producing a symbol.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100