Replies: 3 comments 1 reply
-
Yes, we should add a sentence to clarify that we can have duplicates and also that our sparse COO format is not sorted by rows or columns. |
Beta Was this translation helpful? Give feedback.
-
I agree. It’s important to allow duplicate entries. We’ll need a preprocessing step in QRMumps.jl; I did not realize it doesn’t accept duplicate entries. It’s a bit odd. |
Beta Was this translation helpful? Give feedback.
-
Maybe these presolve could be implemented in SparseMatricesCOO.jl ? Can you guys create issues for what you have in mind? Remove duplicate entries, sort, etc? For the documentation, I can think of two places:
|
Beta Was this translation helpful? Give feedback.
-
In JSO, we use very often the sparse COO matrix representation (rows, cols, vals). This discussion is to clarify the case of duplicate entries in this representation, i.e. the same pair (row, col) may appear more than once in the representation. The typical package doing this is PDENLPModels.jl.
We realized in a recent issue with @MaxenceGollier
JuliaSmoothOptimizers/PDENLPModels.jl#105 that the presence of duplicate entries is not documented and this may be confusing. For instance, QRMumps.jl assumes that there is no such case.
There is a related discussion in this PR JuliaSmoothOptimizers/SparseMatricesCOO.jl#45 .
So, I believe we should clarify what is the expected behavior in general and in SparseMatricesCOO.
Then, we should also document this behavior at least in the docstring of the NLPModel API.
What do you think?
Cc' @dpo @abelsiqueira @amontoison @geoffroyleconte @paraynaud @d-monnet
Beta Was this translation helpful? Give feedback.
All reactions