jrPhD / jrPhD/OpenLoopBalanceControl
Make it easier to write the objective and gradient (avoid having to manually count indices)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
I added this to opty to allow problem access in the objective and gradient: https://github.com/csu-hmc/opty/pull/497
I am working on these two new methods that should let you extract values from the free optimization vector and fill the gradient all by symbol name: https://github.com/csu-hmc/opty/pull/499
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 by reviewing the two linked opty pull requests (#497 and #499) and the repository's Python optimization entry points. Confirm whether the requested objective and gradient workflow belongs in this repository or in opty; done means symbol-name access works without manually counting indices.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100