Skip to content

Issues: vandenheuvel/relp

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

9 Open 8 Closed
9 Open 8 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Obtaining Farkas certificate for infeasible programs.
#46 opened Apr 29, 2022 by filippodebortoli
1
Column pricing with finite precision area:pivoting Area: Choosing the next column to pivot on enhancement Concerns algorithmic functionality rather than implementation details
#31 opened Aug 3, 2021 by vandenheuvel
Parsing the LP file format area:io Area: Reading and writing enhancement Concerns algorithmic functionality rather than implementation details good first issue
#30 opened Aug 3, 2021 by vandenheuvel
A faster implementation of Markowitz' pivot rule in LU factorization area:inverse-maintenance Area: Inverse maintenance enhancement Concerns algorithmic functionality rather than implementation details good first issue
#15 opened Jan 10, 2021 by vandenheuvel
Consider making InverseMaintainer generic over MatrixProvider's associated types architecture
#14 opened Jan 9, 2021 by vandenheuvel
Experiment with partially dense matrices enhancement Concerns algorithmic functionality rather than implementation details
#11 opened Dec 3, 2020 by vandenheuvel
1
Investigate which allocations could be avoided performance Implementation details rather than algorithmic functionality
#9 opened Apr 21, 2019 by vandenheuvel
Use NonZero* types when possible correctness Stability, safety, reliability performance Implementation details rather than algorithmic functionality
#5 opened Apr 5, 2019 by vandenheuvel
Add a component for information extraction and consistency checks correctness Stability, safety, reliability enhancement Concerns algorithmic functionality rather than implementation details
#3 opened Feb 25, 2018 by vandenheuvel
ProTip! Add no:assignee to see everything that’s not assigned.