-
-
Notifications
You must be signed in to change notification settings - Fork 398
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.
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
Tables.jl support for results #3096
Comments
Related https://discourse.julialang.org/t/efficient-serialization-of-jump-results/87896 cc @jd-foster I haven't really looked at the Tables.jl stuff, but what would the output be? Columns with the keys and then one value column? That could be quite nice, and would work for both Dense and Sparse |
Yes, exactly. Tables support for Dense is already implemented in SparseVariables, and I think Sparse is in the works (@trulsf ?) For the example in the readme (after solving):
|
This could actually be quite nice. Happy to review a PR if you want to make one? |
Sure, will get back to you with a PR. No promises on timeline, though. |
We are considering moving the Tables.jl support for results from SparseVariables.jl to another package. (sintefore/SparseVariables.jl#20). One issue then is whether support for the default containers from JuMP should be in a separate package from the SparseVariables type(s) or not.
One alternative would be to add
Tables.jl
support forDenseAxisArrays
andSparseAxisArrays
to JuMP, as Tables is designed to be a light dependency (and keep the Tables support for our own types in our package). What do you think?Some other things to consider (that might go together with this or belong in separate issues) are:
DenseAxisArrays
andSparseAxisArrays
would also store the subindex names/index_vars, in our current implementation these have to be added explicitly when generating e.g. aDataFrame
with the variable values from the solver (kind of a follow-up to Pass names (index_vars) to container extensions. #3088). With names stored with the container, one could generate result tables with good default column names automatically.The text was updated successfully, but these errors were encountered: