microsoft / microsoft/OptiGuide
How can we deal with the case when the number of suppliers is larger in the coffee example
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 713
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
I have a question regarding OptiGuide. Due to token size limitations, it appears that OptiGuide struggles to handle large optimization problems. For instance, in the coffee problem, when the number of suppliers is extensive, OptiGuide may fail to perform effectively. Are there any workarounds or plans in place to enhance OptiGuide's capabilities for such scenarios?"
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
The issue names the coffee example but no files, tests, or entry points. Start by reproducing the example with a large supplier count and inspect where token-size limitations cause failure. Done would require a documented workaround or an agreed enhancement for larger optimization problems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100