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

Suggestions for documentation improvements #2348

Open
13 tasks done
odow opened this issue Oct 3, 2020 · 65 comments
Open
13 tasks done

Suggestions for documentation improvements #2348

odow opened this issue Oct 3, 2020 · 65 comments
Labels
good first issue This issue is recommended for new users, it does not require a thorough understanding of the package Status: Help Wanted Help is welcome on this issue Type: Documentation
Milestone

Comments

@odow
Copy link
Member

odow commented Oct 3, 2020

Hi there!

This issue is a catch-all for documentation improvement suggestions. I'll keep it updated with things to work on, rather than having lots of separate issues.

  • If you have suggestions for things to add to the documentation, leave a comment below.
  • If you're looking to contribute to JuMP, picking something off this list is a great place to start!

General editing

The easiest place to start is just to read through any portion of the docs and give it a good edit. Spelling, grammar, or edits for clarity are always good.

The easiest way to get started is to pick a Markdown page, e.g.,:
https://github.com/jump-dev/JuMP.jl/blob/master/docs/src/index.md
and then click the "Edit this file" pencil icon:
image
Make your changes, and then scroll to the bottom of the page for instructions on how to submit a pull request.

If you're not sure about a change, make it, open a pull request, and then we can discuss it.

Prior art

There are two existing sources of documentation that I would like us to work towards:

Resolved items

Resolved items

Improve current tutorials

A lot of the tutorials are quite basic and consist of just functions. We should revise the existing tutorials to show a wider range of interesting JuMP and Julia syntax and features.

I think it'd also help if each tutorial used a standardized template. Perhaps something like

# Title

This tutorial was contributed by XXX. It is based on the article/book/example of CITE.

## Goal

The goal of this tutorial is to demonstrate ...

## Setup

This tutorial requires the following packages
```Julia
using JuMP
import Foo
```

In addition, you need to data files [bar.txt] and [baz.json]. These files are contained in the JuMP repository 
```
const _DATA_DIR = joinpath(@__DIR__, "data")
```

## Now start the tutorial
  • linear/knapsack
  • linear/multicommodity-flow
  • linear/workforce-schedulig
  • linear/steel-t3
  • nonlinear/qcp
  • nonlinear/rosenbrock
  • nonlinear/mle
  • nonlinear/clnlbeam
  • conic/kmeans
  • conic/correlation
  • conic/sdp-max-cut
  • conic/min-distortion
  • conic/robust-uncertainty

Add new tutorials

Structuring larger models

I wrote a nice answer here:
https://discourse.julialang.org/t/integrating-mathoptinterface-into-an-industry-scale-project-e-g-constraint-management/71943/2?u=odow

Improved MIP modeling tricks

People consistently ask how to reformulate max and abs. These should be added. The Mosek modeling cookbook is the gold-standard for this: https://docs.mosek.com/modeling-cookbook/mio.html

Parallelism

I get this question quite frequently. A section should be added to the docs explaining the different options.

Links with content

How to debug a JuMP model

We need a getting started on debugging.

  1. The Julia debugger doesn't work well with JuMP.
  2. Update your packages to the latest version. JuMP will only support the LTS an the latest point release.
  3. Try a different solver
  4. Simplify the problem
  5. Comment out constraints until the infeasibility resolves itself
  6. Write tests.

@BenLauwens has a great chapter on debugging: https://benlauwens.github.io/ThinkJulia.jl/latest/book.html#chap21. We should link to it, and re-phrase some of the suggestions in a JuMP context.

Parametric problems

The same user as #2662 asked for ways to solve a collection of problems over a set of parameters. We don't have a good way of doing this in JuMP (we have @NLparameter, but not @parameter), but it could be scripted using the modification API (or even just rebuilding the problem).

We should write a tutorial with the different approaches. Here's their suggestion:

![image](https://user-images.githubusercontent.com/8177701/129110774-cc2688d9-ac27-40e2-b6b0-390e1d7c2e0a.png)

I like the idea of visualizing the heat map.

@odow odow added good first issue This issue is recommended for new users, it does not require a thorough understanding of the package Status: Help Wanted Help is welcome on this issue labels Oct 18, 2021
@odow odow changed the title Add documentation on parallel solves of a JuMP model Suggestions for documentation improvements Oct 18, 2021
@odow odow added this to the 1.x milestone Oct 25, 2021
@odow

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow
Copy link
Member Author

odow commented Jan 11, 2023

@odow

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@jd-foster

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@blegat

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@joaquimg

This comment was marked as resolved.

@blegat

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow
Copy link
Member Author

odow commented Sep 5, 2024

Use or mention PiecewiseAffineApprox.jl in the piecewise linear tutorial: https://jump.dev/JuMP.jl/stable/tutorials/linear/piecewise_linear/

@odow

This comment was marked as resolved.

@jd-foster

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow

This comment was marked as resolved.

@odow
Copy link
Member Author

odow commented Oct 15, 2024

Add a section on anti-patterns

@Akshit222

This comment was marked as off-topic.

@odow

This comment was marked as resolved.

@jd-foster
Copy link
Collaborator

More visual content in the docs would be welcome, I think.
This is a good example for flows in graphs: https://doc.sagemath.org/html/en/thematic_tutorials/linear_programming.html#flows

@jd-foster
Copy link
Collaborator

Another interesting idea from Sage docs: a compilation page "presenting commands roughly in the order a student would learn the corresponding mathematics" (but for LP not group theory, of course)
https://doc.sagemath.org/html/en/thematic_tutorials/group_theory.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue This issue is recommended for new users, it does not require a thorough understanding of the package Status: Help Wanted Help is welcome on this issue Type: Documentation
Development

No branches or pull requests

7 participants