Skip to content
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

Maybe improve installation.md by showing package's "popularity" #3589

Closed
wants to merge 1 commit into from

Conversation

LebedevRI
Copy link
Contributor

For me at least, picking the "right" solver is still a but daunting.
It would be nice to be actually able to filter by features (i mean,
other than Ctrl+F), but asides from that, perhaps showing
the "popularity" of each particular Julia package might make choosing easier?

This is how it looks: https://github.com/LebedevRI/JuMP.jl/blob/installation.md/docs/src/installation.md#supported-solvers

If this looks too ugly, or is not wanted, please just close the PR :)

For me at least, picking the "right" solver is still a but daunting.
It would be nice to be actually able to filter by features
(i mean, other than Ctrl+F), but asides from that,
perhaps showing the "popularity" of each particular Julia package
might make choosing easier?
Copy link

codecov bot commented Nov 27, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (96b4147) 98.37% compared to head (24f6715) 98.37%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3589   +/-   ##
=======================================
  Coverage   98.37%   98.37%           
=======================================
  Files          38       38           
  Lines        5673     5673           
=======================================
  Hits         5581     5581           
  Misses         92       92           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@odow
Copy link
Member

odow commented Nov 28, 2023

I think we need to be quite careful here. I agree that JuMP could make it easier to suggest solvers for a particular problem class, but we don't really want to pick winners.

One thing we do have is the README for each solver: https://jump.dev/JuMP.jl/stable/packages/solvers/

If we wanted to make the table a little easier to read, we could consider dropping the solver column in favor of just the Julia package and include the organization. So jump-dev/HiGHS.jl. But I don't know what we'd do with multiple solvers in the same package, like AmplNLWriter.

@LebedevRI LebedevRI closed this Nov 28, 2023
@odow
Copy link
Member

odow commented Nov 28, 2023

Perhaps to clarify though: I'm very open to suggestions for changes. I don't particularly like the table or think that it is very helpful...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants