JuliaSmoothOptimizers / JuliaSmoothOptimizers/BasicLU.jl

API design: fused function for `solve_for_update` and `update`

Open
#23 7 comments 0 reactions 0 assignees View on GitHub
Dominant language
Julia
Stars
10
Forks
5
PR merge metrics
No merged PRs in 30d

Description

It seems that in solve_for_update, `getsol = true` is always necessary to obtain the pivot value to pass to the `update` call.

In that case, are there scenarios where `getsol = true` happens? It could be good to have a top-level updating function that takes the index and column to replace. The fact that `solve_for_update` takes either in separate methods is confusing

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.